3. Enterprise Collaboration Strategist Author, Blogger, Speaker

4. Regional Architect Author, Blogger, Speaker Tahoe Digital Dashboard Outlook Today

6. 2003 – What is an Application? SharePoint was not an Application Platform, except Web Parts Investments were in MOSTLY portals and content 2007 – Everything is an Application! Push to embrace SharePoint for LOB applications Custom server side code 2010 – Choose the right Application SharePoint and Developer Tools come together Silverlight, CSOM and other new capabilities Partially trusted code reduces impact and risk to farm 2013 – Redefine Application as App Client side experience via HTML or iFrame Leverage CSOM and REST APIs from Azure and other clients Investments in App discovery and Management via SharePoint store Deployments 2013 2010 2007

9. No custom code on the SharePoint server Reduces the ramp time for building Apps Leverage hosting platform features in new Apps Isolation – Private vs. Public clouds

26. Evergreen and release cycle – Old model SP2013O16O17 O18 Tightly coupled SharePoint customizations Upgrade Specific upgrade project each time new version is introduced Customizations have to be upgraded to get access on new capabilities in product Will cause additional costs during each release cycle of customizations Customization updates cause downtime each time something is changed Complex ALM processes for ensuring quality of the code

27. Evergreen and release cycle – NEW model SP2013 Loosly coupled SharePoint customizations O16O17O18 Development You choose when and how applications are updated... Backwards compatibility for API level to move customizations cross versions Customizations don’t block new capabilities from SharePoint Customizations extend, not change SharePoint Customizations can be updated with minimal impact on SharePoint Customizations will utilize services from SharePoint and other services, but won’t usually change out of the box services.

31. Sponsored by