Monday, January 9, 2017

SharePoint Developer Options



Disclaimer: All opinions are my own. I am not affiliated with any company mentioned in this post.
There are a number of ways to develop applications in SharePoint these days. To find out more please visit https://dev.office.com/
  1. Script Editor - Great for manipulating a single page.
  2. Host pages in a SharePoint Document Library - All of your pages can be uploaded to a Document Library and organized using Folders. All of your code must be client based only. You cannot load code that runs on the SharePoint server. You can use plain JavaScript, a JavaScript Framework like Angular, Angular2, Knockout etc... Various Javascript libraries such as JQuery, ReactJS etc... Custom Stylesheets, BootStrap and many more. But all must run on the client, no SharePoint Server side code is allowed anymore.
  3. SharePoint Add-In (SharePoint Hosted or Provider Hosted) - Given what I am seeing in blog posts I follow, SharePoint Hosted Add-Ins are supported at this time but are quickly falling out of favor. Provider Hosted Add-Ins are preferred, this is where all of your code resides on your own server and you make either CSOM or REST Calls into SharePoint to surface your data. You will need to have permission or someone with permissions to register your app with the Sharepoint catalog.
  4. SharePoint Framework - This is still in Developer Preview Release at the time of this post, but it is expected to be made Generally Available sometime in 2017 for SharePoint Online and SharePoint 2016. The SharePoint Framework allows you to create SharePoint page Web Parts using modern technologies like I mentioned in item 2 above. You can create these web parts using a Mac or Windows dev machine. More information is available at https://dev.office.com/sharepoint/d... to get started. You will need to have permission or someone with permissions to register your web part with the Sharepoint catalog.
  5. Microsoft PowerApps - Designed primarily for Power Users in an Organization as a replacement for InfoPath. PowerApps is so much more though, your data store is not limited to just SharePoint, you can surface data from a variety of Social Networks (Facebook, Twitter, Slack, etc...) from Azure Sql Server, On-Premise SQL Server, Vimeo, YouTube, WordPress, the Common Data Service which is part of each PowerApps environment etc... and many many more pre built Connectors. If a connector is not available for your datasource you can create your own. PowerApps apps can be web, phone, or tablet based. This is a no code solution, to manipulate the web part you use Excel type formulas to add dynamic functionality to your apps. At the time of this post PowerApps apps are limited to your organization, there is no path to sell your apps in one of the app stores. You can find more information at https://powerapps.microsoft.com/en-...
A great resource to keep on hand is the Microsoft Patterns and Practices website linked from https://dev.office.com/ , here you can find a wealth of information, code samples and much more.
One thing to note if you do not already know, as of SharePoint 2016, Sandbox solutions have been deprecated. Your technology of choice may be limited due to your companies policies but none the less, it is exciting to know that we have many options.

Microsoft PowerApps and Flow Learning Resources

An ongoing list of Microsoft PowerApps and Flow Resources I'll update as I come across helpful resources. Main Sites: https://p...