· The apps for SharePoint provide a new method to deliver specific information or functionality to a SharePoint site.
· SharePoint 2013 introduces the "Cloud app model", It enables you to create a apps
· Microsoft will host and control a public SharePoint Store, where developers will be able to publish and sell their custom apps for SharePoint.
· SharePoint apps are self-contained functionality that extend capabilities of SharePoint web application
· Apps are essentially web applications which runs "outside" of SharePoint host web
· It's easy to use, stand-alone app that solves a specific end-user or business need
· We can use any languages for creating the apps such as HTML, PHP, .NET & web development tool etc...
· By using "NAPA" we can create a SharePoint apps
· We can use Client Object Model (CSOM) to talk to SharePoint
Example: we can create the custom branding and themes for SharePoint 2013 and share them with rest of the users with office market place
- .NET for Synchronous
Apps hosting Types
· Thery are cloud based Apps
· Provider-Hosted Apps may have SharePoint components, similar to SharePoint-Hosted Apps, but the main business logic and data storage are manifested in an external infrastructure, such as an external Web server or in the Cloud.
· The app and all resources are hosted in separate server in our organization's environments or developer's environment
· We are the responsible for provisioning and IT organizational or developers can supports the app
Hosted in the cloud (Azure auto-provisioned)
· These are also cloud based apps
· Auto hosted apps all windows azure and windows azure SQL database components are provisioned for you when apps is installed and windows azure websites infrastructure handles the load balancing and other important maintenance task
· Auto hosted app for SharePoint can interact with a SharePoint website but also uses resources and services that are located on a remote site that is hosted by Windows Azure.
Hosted in a SharePoint environment
· SharePoint-Hosted Apps are manifested entirely within SharePoint server and generally have no external dependencies.
· The app and all resources are hosted in our organization's SharePoint farm
· We can reuse the web elements like list, libraries and out of box things
Apps Restrictions compared with Sandboxed Solution
Why Sandboxed solutions?
· Sandboxed solution is introduced in SharePoint 2010
· Sandboxed Solutions are partially trusted, and can only access a subset of the server-side SharePoint API.
· Sandboxed solutions can deploy by site collection owner or Administrator via browser
· Scalability and flexibility are increased because sandboxes run in a separate process (spucworkerprocess) that can be restricted by quotas, and their effect on the farm can be monitored.
· Sandboxed solutions do not affect other sandboxed solutions, well at least not in other site collections is what I mean.
· Sandboxed solutions skip application pool recycles, so debugging is not such a pain.
Sandbox solution vs. Apps
· Apps can cross site collections within the same "tenant", this was a huge limitation of a sandbox solutions.
· Apps for SharePoint have permissions just as users and groups do. This enables an app to have a set of permissions that are different from the permissions of the user who is executing the app.
· Apps can now define their entire user interface. This means we are no longer limited to developing a web part and hosting it inside a web part page just to do some custom code, but sandboxed we have limitations.
· Build apps for SharePoint
· SharePoint 2013 development overview
In this article, we have explored about SharePoint apps and Sanboxed solution vs apps. Stay tuned for more article :)