O365con14 - develop, build, package and deploy apps for office 2013 with visual studio
0 likes557 views
This document discusses developing, building, packaging and deploying apps for Office 2013 using Visual Studio 2013. It provides an overview of apps for Office, including task pane, content and mail apps. It then covers developing apps using Office Developer Tools in Visual Studio, and publishing apps to the Office Store, SharePoint app catalog or network share. Examples of potential app scenarios are also briefly described.
O365con14 - develop, build, package and deploy apps for office 2013 with visual studio
- 1. Develop, Build, Package and Deploy Apps for Office 2013 with Visual Studio 2013 Bram de Jager SharePoint Architect | Microsoft Certified Solution Master: SharePoint
- 2. • Intro to Apps for Office • New in Office 2013 Service Pack 1 • Develop, Build apps • Package and Deploy apps • Wrap-up Agenda
- 3. INTRO TO APPS FOR OFFICE
- 4. History • Visual Studio Tools for Office (VSTO) • VSTO 2003 downloadable for Visual Studio 2003 • VSTO 2005 (SE) downloadable for Visual Studio 2005 • VSTO 3.0 build into Visual Studio 2008 • VSTO 4.0 build into Visual Studio 2010 • Office Developer Tools • Office Developer Tools for Visual Studio 2012 • Office Developer Tools for Visual Studio 2013
- 5. Apps for Office and SharePoint
- 6. Task pane apps • Side-by-side • Shown next to the Office document • Supported by Word, Excel, PowerPoint, and Project • Contextual information • Insert content into the document • Gets content to perform an action • Can be used for • Retrieving information from web service based on the selection of the user
- 7. Content apps • Appears in body • Shown in line of the document • Integrate • Integrate rich, web-based data, visualizations, embedded media, as well as other external content • Can be used for • Display Excel data plotted on top of geographical maps
- 8. Mail apps • Shown in Outlook item • Requires Outlook 2013 & Exchange 2013 • Seamless integration on desktop, browser and devices • Scenarios • Based on contextual trigger in item body • Runs in messages and/or appointments • Can be used for • Shows Bing Maps centered on the address found in the body of the email
- 9. Supported applications Office application Task Pane Content Mail Access app for SharePoint Yes* Excel Yes Yes Excel Online Yes Yes Word Yes Outlook Yes Outlook Web App Yes OWA for Devices Yes* PowerPoint Yes* Yes* PowerPoint Online Yes* Yes* Project Yes * = requires Office 2013 Service Pack 1
- 10. NEW IN OFFICE 2013 SERVICE PACK 1
- 11. What's new for Apps for Office in Office SP1 • Highlights • Support for PowerPoint 2013 & PowerPoint Online • Changes in licensing model (no sign-in required) • New API's: Navigation API, Data Formatting API, File Properties API • Mail apps in compose email and appointments • Office UI updates • Requirements • Office 2013 Service Pack 1 • Update to Office Developer Tools for Visual Studio (March 2014 update)
- 13. Anatomy of an app for Office HTML5, CSS, JavaScript (in all its glory!) 2 Web applications hosted by any HTTP delivery mechanism 3 Document-based manifest driven applications. 1
- 14. Developer tool sets and APIs • “Napa” Office 365 Development Tools • Browser based developer tool, http://dev.office.com • Start in Napa, continue in Visual Studio • Office Developer Tools for Visual Studio • Visual Studio 2012 extension • Visual Studio 2013 RTM • Visual Studio 2013 – March 2014 Update • Support for Office 2013 SP1 • Office 365 API Tools for Visual Studio Preview
- 15. Apps for Office rich client runtime
- 16. Apps for Office web clients
- 17. “ “ DEMO Build a Wikipedia Task Pane app in Word
- 18. PACKAGE AND DEPLOY APPS
- 19. Publish apps for Office • Office Store • Public marketplace that Microsoft will host and regulate on Office.com • Apps for Office catalog on SharePoint • For task pane and content apps • Centralized corporate catalog managed by IT • Exchange catalog • Private catalog for mail apps • Network shared folder app catalog • Deploy task pane and content apps to a central network shared folder
- 20. App availability by location App type Office Store Corporate catalog Exchange Server Shared folder app catalog Task Pane app x x x Content app x x x Mail app x x Same Office-solution catalog experience that the Office Store provides. App Catalog located in SharePoint. Apps are only shown in Office clients. Availability based on access to file share.
- 21. What goes where? Visual Studio 2013 MS Build WebDeploy package XML Manifest Office Client File ShareCorporate Catalog IIS Webserver Azure Website Office Store
- 22. “ “ DEMO Publish the Wikipedia app to Azure and Corporate Catalog
- 23. Configure Office client for App Catalog • Office client configuration • Open Word 2013 • Open Options » Trust Center » Trust Center Settings • Select Trusted App Catalogs (on left) • Add the Corporate Catalog URL (check “Show in menu” box) • Registry entry • HKEY_CURRENT_USERSoftwareMicrosoftOffice15.0WEFTrustedCatalogs
- 24. WRAP-UP
- 25. Scenarios • Start (review/approval) workflow process from within the Office clients • Allowing employees to browse, select and insert (legal) text snippets into documents, which are managed in a central location • Pull meeting location from meeting invite and highlight the meeting room plotted onto the building floor plan • Recognize the tracking number for package delivery and retrieve real-time delivery status • And many more…
- 26. Write once, run everywhere
- 27. Key takeaways • Apps for Office are the means for enabling contextual experiences • Office 2013 SP1 brings improvements to Apps for Office • Apps for Office boost productivity by integrating services into Office • Leverage existing investments when building Apps for Office
- 28. bram.de.jager@macaw.nl | bramdejager.wordpress.com | @bramdejager Bram de Jager