Building Add-ins for Office 365 requires many new skills and knowledge. For those new to SharePoint and all SharePoint veterans, building add-ins and apps for Office 365 introduces a huge paradigm shift over the full-trust development model. Full-trust development is on its way out whether we like it or not. In this session, we will learn how to create real world add-ins and apps deployable on Office 365 and On-premise SharePoint 2013. Learn to build SharePoint-Hosted add-ins/apps and Provider-Hosted add-ins/apps that will leverage various Azure services to create robust solutions, including Azure Web Sites, Azure Web Jobs and more. We will demonstrate using AngularJS and Web Services to create useful and functional add-ins. The future is today. Don’t pass up this opportunity to learn the skills and knowledge you need to build SharePoint Add-ins and App solutions for Office 365. Attendee Takeaways: 1. Understand the difference between full-trust solutions, sandbox solutions and add-ins/app solutions. 2. Create real world add-ins and apps deployable on Office 365 and On-premise SharePoint using AngularJS. 3. Build SharePoint-Hosted add-ins/apps and Provider-Hosted add-ins/apps. Presented at Houston TechFest 2016

1. www.expertpointsolutions.com
Real World Add-in Development for Office365 & SharePoint 2016
Brian Culver ● Houston Techfest ● September 23, 2016

2. About Brian Culver
 SharePoint Solutions Architect for Expert Point Solutions in
Houston, Texas.
 Microsoft Certified Master (MCM) in SharePoint
 Microsoft Certified Professional Developer (MCPD).
 Brian has worked in the Information Technology industry for
since 1998 and he has been working with SharePoint since
2005. His deep expertise includes Azure, Office365,
SharePoint, ASP.Net, SQL Server and Project Server. He
has been involved in many large SharePoint
implementations including Internet and Intranet sites, Partner
Portals, Enterprise Content Management and Governance,
and much custom application integration and development.
 Author, Speaker and Blogger
Email : brian.culver(at)expertpointsolutions.com
Twitter : @spbrianculver
LinkedIn : https://www.linkedin.com/in/bculver
Blog : http://blog.expertpointsolutions.com

3. Session Agenda
 Reviewing the Landscape
 Full Trust vs Add-ins/Apps
 SharePoint Development Today
 Create a Hello World SharePoint-Hosted Add-in
 Adding AngularJS
 Create a Hello World Provider-Hosted Add-in
 Azure Web Sites
 Deployment Lifecycle
 Other considerations

4. Reviewing the Landscape
 Things are changing quickly … very quickly

5. Reviewing the Landscape
 Things are changing quickly … very quickly

6. Reviewing the Landscape
 Things are changing quickly … very quickly
 Full Trust Server Side development is practically gone … don’t do it

7. Reviewing the Landscape
 Things are changing quickly … very quickly
 Full Trust Server Side development is practically gone … don’t do it

8. Reviewing the Landscape
 Things are changing quickly … very quickly
 Full Trust Server Side development is practically gone … don’t do it
 Client Side development is in

9. Reviewing the Landscape
 Things are changing quickly … very quickly
 Full Trust Server Side development is practically gone … don’t do it
 Client Side development is in
 It’s a different kind of world … its a hybrid world

10. Reviewing the Landscape
 Things are changing quickly … very quickly
 Full Trust Server Side development is practically gone … don’t do it
 Client Side development is in
 It’s a different kind of world … its a hybrid world

11. Reviewing the Landscape
 Full Trust Solutions
 Only available on premise
 ~80% of third party products
 ~80% of Enterprise custom solutions
Image Source: https://blogs.office.com/2016/05/04/the-sharepoint-framework-an-open-and-connected-platform/
Used with permission from Microsoft.

12. Reviewing the Landscape
 Full Trust Solutions
 Only available on premise
 ~80% of third party products
 ~80% of Enterprise custom solutions
 Sandbox Solutions
 Code-based sandbox solutions were deprecated back in 2014
 Code-based sandbox solutions not supported in Office365 as of August 31st, 2016
 Code-based sandbox solutions are also deprecated in SharePoint 2013 and in SharePoint 2016
 Read this: https://msdn.microsoft.com/en-us/pnp_articles/sandbox-solution-transformation-guidance

13. Reviewing the Landscape
 Full Trust Solutions
 Only available on premise
 ~80% of third party products
 ~80% of Enterprise custom solutions
 Sandbox Solutions
 Code-based sandbox solutions were deprecated back in 2014
 Code-based sandbox solutions not supported in Office365 as of August 31st, 2016
 Code-based sandbox solutions are also deprecated in SharePoint 2013 and in SharePoint 2016
 Read this: https://msdn.microsoft.com/en-us/pnp_articles/sandbox-solution-transformation-guidance
 Apps and Add-ins
 SharePoint-Hosted
 Provider-Hosted
 SharePoint / Office 365 Dev Patterns & Practices (PnP) http://aka.ms/OfficeDevPnP
 SharePoint Framework (SPFx)
 ETA: 2017
 SharePoint Framework Developer Preview Release out
Image Source: https://blogs.office.com/2016/05/04/the-sharepoint-framework-an-open-and-connected-platform/
Used with permission from Microsoft.

14. SharePoint Development Today
Image Source: https://blogs.office.com/2016/05/04/the-sharepoint-framework-an-open-and-connected-platform/
Used with permission from Microsoft.

15. SharePoint Development Today

16. SharePoint Development Today
Why?
 Isolated and Safer
 Using a different domain name for apps helps prevent cross-site scripting between apps and SharePoint sites.
 Each apps has its own unique subdomain which isolates it from SharePoint and other apps.
 Multi-tenant
 Works with subscription service which allows it to run on separate tenants.
 Multiple development possibilities (even non-MS stack)
 Open Source, jQuery, TypeScrypt, AngularJS, BootStrap, etc.
 Easier to deploy
 Easier to maintain and upgrade (Best lifecycle and versioning to date)
 Manageable (Office Store and Corporate Catalog)
 Cloud ready!
 Works in Office 365, SharePoint 2013 and SharePoint 2016.
 Integrates with just about any Cloud service and technology.

17. SharePoint Development Today
Develop an add-in whenever you can
 The most important guidance we can give you is to develop a SharePoint Add-in instead of a farm solution or no-code
(declarative) sandboxed solutions whenever you can. SharePoint Add-ins have the following advantages over classic
solutions:
 Provide users with the easiest discovery, purchase, and installation process.
 Give administrators the safest SharePoint extensions.
 Provide you with the simplest marketing and sales system based on a Microsoft online add-in store.
 Maximize your flexibility in developing future upgrades.
 Maximize your ability to take advantage of your existing non-SharePoint programming skills.
 Integrate cloud-based resources in smoother and more flexible ways.
 Enable your extension to have permissions that are distinct from the permissions of the user who is running the add-in.
 Enable you to use cross-platform standards, including HTML, REST, OData, JavaScript, and OAuth.
 Enable you to take advantage of the SharePoint cross-domain JavaScript library to access SharePoint data.
Alternatively, you can use a Microsoft-provided secure token service that is OAuth-compatible or use digital certificates to
get authorization to SharePoint data.
 Source: https://msdn.microsoft.com/en-us/library/office/jj163114.aspx

18. SharePoint Development Today
 Apps and Add-ins
 SharePoint-Hosted
 Provider-Hosted
 SharePoint / Office 365 Dev Patterns & Practices (PnP) http://aka.ms/OfficeDevPnP
 SharePoint Framework (SPFx)
 ETA: 2017
 SharePoint Framework Developer Preview Release out

19. SharePoint-Hosted Solution
Office365 and SharePoint 2016
Demo

20. Provider-Hosted Solution
Azure Web Site with Office 365
Demo

21. Closing Comments
 Develop an add-in whenever you can.
 Always strive to leverage the latest frameworks.
 Maximize your ability to take advantage of your existing non-
SharePoint programming skills.
 Be flexible and integrate cloud-based resources in smoother and more
flexible ways.
 Use cross-platform standards, including HTML, REST, OData,
JavaScript, and OAuth.
 Embrace Change … its already happened, and change will continue.
 Pay close attention to the Office Dev Patterns and Practices group.
 Oh yeah … don’t forget PowerShell. You won’t get far without it.

22. Questions
??
?
?

23. Constructive Feedback Is Appreciated
Great information,
but would like to
have learned more
about [Insert Topic]Brian – Your
presentation
was …
Good
Demos!
Thanks!

24. Thank you!
Brian Culver, MCM
Twitter:
@spbrianculver
E-mail:
brian.culver(at)expertpointsolutions.com
Blog:
http://blog.expertpointsolutions.com/
Slides:
http://www.slideshare.net/bculver

25. Resources
 Office 365 Roadmap
 http://fasttrack.microsoft.com/roadmap
 SharePoint / Office 365 Dev Patterns & Practices (PnP)
 http://dev.office.com/patterns-and-practices
 The SharePoint Framework—an open and connected platform
 https://blogs.office.com/2016/05/04/the-sharepoint-framework-an-open-and-connected-platform/
 Overview of the SharePoint Framework
 http://dev.office.com/sharepoint/docs/spfx/sharepoint-framework-overview
 SharePoint Framework Developer Preview Release
 https://dev.office.com/blogs/sharepoint-framework-developer-preview-release
 5 differences between SharePoint Framework debug and release builds
 https://www.spcaf.com/blog/5-differences-sharepoint-framework-debug-release-builds/
 Sandbox solution transformation guidance
 https://msdn.microsoft.com/en-us/pnp_articles/sandbox-solution-transformation-guidance