SharePoint 2013 introduces new App Model for building customizations for the SharePoint platform. Did you know that you could also leverage the App Model for structured and repeatable deployments?
12. Achitecture Overview
Site
SharePoint Site Collection
App Instance App Web
Config List Status List
App App API
Request Queue
Configuration Worker
Apply
configuration
Start app
Submit configuration
request
Update request
status
Process configuration
request
Get Available
Configurations
Submit configuration
request
1
2
3
4
5
6
7
8
Prepare:
- Presenter mode in Visual Studio aanzetten
- Alle projecten opstarten en inloggen
- SPSNL14 site opnieuw aanmaken
- Publishing web aanmaken
- Managed Navigation aanzetten
Future proof : your business will change even if you are not ready for the cloud yet
Apps have an online focus making it easier to move (if you need to)
Ready for the PLA (that focusses heavily on utilizing the app model)
Leveraging the new Application Model for structured and repeatable deployments
Not everything can be done declarativly
Only deployable at site collection level, thus creating sites based on a template is ‘hard’
Limited to resources, will run in http context thus can time out (creating a site based on a template that is). And after using 300 resources you can no longer apply stuff
Everything is code, except artifacts you create in your app web.
Should refrain -> no footprint
no footprint -> upgradability
The App model supports App Only Calls, actions that can be done even though the user doesn’t have that specific permission. Not supported in Sandboxed Solutions and supported with elevation in FTC but then everything can be done.
Limitations:
Managed Navigation
Image Renditions
Portal Site Connection
Some versioning settings
Enable Community Reporting