1. Enabling Developers with Development Features Presented by: Ricardo Wilkins SharePoint Solutions Architect

2. Discussion Points  Today’s SharePoint vs Old Stuff  Apps & the App Store  Tools & Deployment Options  Coding Walkthru

3. Evolutio n

4.  App model  Dev Tools  Deployment Options What’s New  Bottom Line :  Client-side is the future  No more excuses

5. Features | Solutions | Apps Features Used to deploy artifacts List templates, workflows, web parts, etc Solutions Used to deploy code & files Usually includes Feature(s) Package of files (*.wsp) Apps New in SP2013 Used to deploy solutions & other things that make up an App Package of files (*.app)

6. Farm | Sandbox | SP Apps Farm Full trust solutions Full access API Classic model from 2007 On-premise only Sandbox Declarative elements Partially trusted code service still included for limited server side support Resource monitored SPO friendly SP Apps New Apps model Deployed from corporate catalog or office market place Manage permission and licenses specifically Preferred option

7. 7 No custom code on the SharePoint server Easier to upgrade to future versions of SharePoint Works in hosted environments w/o limitations Reduces the ramp-up time for those building apps Don’t need to know/be as familiar with SharePoint “-isms” Leverage hosting platform options in new apps App Model Benefits

8. 8 Why Apps?  End Users: consumerization thru app catalogs  IT Pro: stable SP environments  Devs: reuse existing skill sets

9. Why Apps?  Easy discovery, purchase and installation process for Users  Safest way for admins to extend SharePoint  Simple marketing and sales system for app revenue  Maximize flexibility in developing future upgrades  Maximize your ability to leverage non-SharePoint skills  Smoother integration with cloud-based resources  Permissions distinct from the user  Cross-platform standards (REST, OData, OAuth, etc)  Cross-domain access via Javascript and proper security mechanisms  Work as well online as on-premise

10. 10 Tools

11. Visual Studio

12. Client-side Object Model Client-side OM greatly expanded Search Taxonomy Feeds Publishing Sharing Workflow IRM Analytics E-Discovery Business Connectivity Services Mobile

13. Napa

14. Deployment Options  SharePoint-hosted  Cloud-hosted  Provider-hosted  Azure Auto-hosted

15. Apps – Possible scenarios

16. 16 Apps – Possible scenarios 16

17. 17 Apps – Possible scenarios 17

18. 18 Apps – Possible scenarios 18

19. 19 App Store | App Catalog | App Market

20. 20 App Store | App Catalog | App Market

21. Analysis  Architects important  Additional configuration (security)  Code Scope (App Web)  Data Access Performance (Farm vs Apps; network & cloud latency)  Full screen apps vs chrome  Isolation  Apps and Search Crawl (not by default)  Access external web services & databases (unlike Sandbox solutions)  Non-.NET participation  No upgrade concerns – really?  Process monitoring (no longer needed?)  IT Pro headaches a thing of the past?

22. Demo (by screenshot)

23. http://msdn.microsoft.com/en-us/library/office/apps/fp179924.aspx

53. Demo – Build with ‘Napa’

68. Seller Dashboard (http://dev.office.com)http://dev.office.com Office and SharePoint Store In-product App Discovery Direct Sales Negotiated deals/ IT projects App Catalog TRIAL/ PURCHASE TRIAL/ LEAD OFFICE/ SHAREPOINT Developer IT admin End users Choice, Control and Flexibility APP VALIDATION

69. Questions? Enabling Developers with SharePoint Development Features Presented by: Ricardo Wilkins rwilkins@bennettadelson.com www.SharePointCowBell.com @ricardo303 @spcowbell