[Cross posting from dev.office.com blogs]
In this PnP Web Cast we concentrate on the Office 365 Dev PnP Core Component which is designed to increase the productivity of developers when you are developing applications for SharePoint Online or for SharePoint on-premises. It encapsulates numerous complex operations to more streamlined methods and usage, so that developers can more efficiently concentrate on solving business problems. PnP Core component is released as Nuget package and can be used in provider hosted add-ins or from native windows applications, like with console applications. It’s also used by the PnP PowerShell CmdLets, which enables you to take advantage of the Core Component capabilities without the need of using Visual Studio.
There are currently two different versions of the PnP Core Component, one targeted for SharePoint Online and for SharePoint 2013 on-premises. SharePoint 2016 version is coming later 2016. Different versions are released due the differences in supported CSOM operations.
One of the great capabilities in the PnP Core Component is the AuthenticationManager class, which can be used to get SharePoint ClientContext easily regardless of the used authentication models in SharePoint Online or in SharePoint on-premises. Supported authentication models for your application are following.
- SharePoint Online – With credentials
- SharePoint Online – With web loging
- SharePoint Online – App Only
- SharePoint Online – Azure Active Directory – Native Client
- SharePoint Online – Azure Active Directory – App Only
- SharePoint 2013 / 2016 – With credentials
- SharePoint 2013 / 2016 – ADFS mixed authentication
- SharePoint 2013 / 2016 – App only
In the demo section Bert concentrates on showing how to use different authentication methods when you need to gain access to SharePoint Online.
Presentation used in this web cast is available from http://doc.com/OfficeDevPnP.
Video at Channel 9.
See following additional links around the covered topics and for additional documentation around the remote provisioning models.
- PnP Core Component – in Nuget gallery. Notice that there’s different version for SharePoint Online and for SharePoint 2013 on-premises
- PnP Core Component – in GitHub
- Authentication Manager in PnP Core
- ADFS usage with PnP Core in on-premises
- Connecting to SharePoint Online from console application with ADAL and PnP Core Component – blog post at MSDN
- PnP Web Cast – Provisioning Engine – also included in the PnP Core Component
- PnP Web Cast – Remove timer job framework – also included in the PnP Core Component
- PnP PowerShell – Uses PnP Core Component and it’s capabilities
Using Azure AD with AuthenticationManager (from PnP Partner Pack)
- Azure Active Directory Application registration, as Office 365 Add-In
- Create the self-signed certificate
- App Only certificate configuration in the Azure AD Application
What is Office 365 Developer Patterns and Practices (PnP) web cast series?
We have started this Office 365 Developer Patterns and Practices (PnP) web cast series to cover different patterns, practices and topics around development with Office 365 and SharePoint. Majority of the topics are valid for the Office 365 and SharePoint on-premises. Our objective is to release new around 30-45 minute long web cast each Monday with few slides and live demo on the covered topic. All web casts are published at the PnP Channel 9 video blog with additional references on the existing materials.
PnP is community driven open source project where Microsoft and external community members are sharing their learning’s around implementation practices for Office 365 and SharePoint on-premises (add-in model). Active development and contributions happen our GitHub project under dev branch and each month there will be a master merge (monthly release) with more comprehensive testing and communications. Latest activities and future plans are covered in our monthly community calls which are open for anyone from the community. Download invite from https://aka.ms/OfficeDevPnPCall.
This is work done by the community for the community without any actual full time people. It’s been great to find both internal and external people who are willing to assist and share their learning’s for the benefit of others. This way we can build on the common knowledge of us all. Currently program is facilitated by Microsoft, but already at this point we have multiple community members as part of the Core team and we are looking to extend the Core team with more community members.
If you have any questions, comments or feedback around PnP program or this blog post, please use the PnP Yammer group at https://aka.ms/OfficeDevPnPYammer.
“Sharing is caring”
Vesa Juvonen, Senior Program Manager, Office 365, Microsoft – 15th of February 2016