• SharePoint Developer Announcements - dev.office.com/blogs
• SharePoint Development Guidance - docs.microsoft.com/en-us/sharepoint/dev
  • Right now SharePoint Dev PnP guidance is still in its own location, soon in above site - aka.ms/sppnp-msdn
• SharePoint Development Videos - aka.ms/spdev-videos
• SharePoint Development Samples - github.com/SharePoint
• SharePoint Social Media Channels - @officedev, @officedevpnp, @vesajuvonen, OffceDev Facebook
• SharePoint Developer discussions - aka.ms/sppnp-community
  • Obviously countless other locations
• New feature requests for SharePoint development - UserVoice SharePoint Dev
• Possible issue in SharePoint Dev platform - github.com/SharePoint/sp-dev-docs/issues
  • + Other support channels where suitable

To make things easy, we have provided needed script for SharePoint 2013 and SharePoint 2016 from the SharePoint Patterns and Practices initiative under the PnP-Tools repository in GitHub. You can find direct link to these scripts below. You’ll find different scripts for SP2013 (15) and SP2016 (16) for enabling the CSOM client callable proxy in your farm.

• PowerShell to enable site collection creation with CSOM

Let’s walk through the steps to enable this using these scripts one-by-one.

Enable Server Stub for site collection creation

When you install SharePoint 2016, we do not unfortunately enable this assembly for the CSOM, so we’ll need to explicitly enable the server side support for the tenant assembly, so that when we are using CSOM remotely, SharePoint knows which assembly is responsible for handling the request in server side. If you don’t do this, you’ll get following exception in the CSOM side when you use the APIs.

[sourcecode language='text'  padlinenumbers='true' wraplines='true']
{"Cannot find stub for type with id \"{268004ae-ef6b-4e9b-8425-127220d84719}\". The specified server may not support APIs used in this operation."}
[/sourcecode]

You can enable the server side stub by using the allowtenantapiv16.ps1 script from the GitHub. You will need to do this only once in the farm with the farm administrative permissions, since we are modifying the SharePoint web application settings to enable this. If you have multiple web applications, you will need to be repeating this cross all of those where you want this capability to be enabled.

[sourcecode language='powershell'  wraplines='true']
param
(
[Parameter(Mandatory=$true)][ValidateNotNullOrEmpty()]
    [String]$WebApplicationUrl
)
#
# Enable the remote site collection creation for on-prem in web application level
# If this is not done, unknon object exception is raised by the CSOM code
#
$snapin = Get-PSSnapin | Where-Object {$_.Name -eq 'Microsoft.SharePoint.Powershell'}
if ($snapin -eq $null) 
{
    Write-Host "Loading SharePoint Powershell Snapin"
    Add-PSSnapin "Microsoft.SharePoint.Powershell"
}    
 
$webapp=Get-SPWebApplication $WebApplicationUrl
$newProxyLibrary = New-Object "Microsoft.SharePoint.Administration.SPClientCallableProxyLibrary"
$newProxyLibrary.AssemblyName = "Microsoft.Online.SharePoint.Dedicated.TenantAdmin.ServerStub, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
$newProxyLibrary.SupportAppAuthentication = $true
$webapp.ClientCallableSettings.ProxyLibraries.Add($newProxyLibrary)
$webapp.SelfServiceSiteCreationEnabled=$true
$webapp.Update()
Write-Host "Successfully added TenantAdmin ServerStub to ClientCallableProxyLibrary for web application" $WebApplicationUrl
# Reset the memory of the web application
Write-Host "IISReset..."    
Restart-Service W3SVC,WAS -force
Write-Host "IISReset complete on this server, remember other servers in farm as well." 
[/sourcecode]

Here’s what the script does in practice

1. Load SharePoint PowerShell module
2. Connect to SharePoint web application provided as parameter for the script
3. Add TenantAdmin assembly as known assembly for the client callable proxies – this will include the needed mapping with the CSOM methods and the actual assembly performing the operation in server side
4. Enable self service site collection for the web application, so that we can perform site collection creations remotely

You might be thinking on why didn’t we perform these needed steps by default with the installation, which is a fair question without clear answer. This operation is though fully supported and absolutely something what can be performed in the farm.

Set one of the existing site collections as tenant admin site

This could be slightly confusing step, but it’s required even though you would not use multi-tenant features in on-premises. You can consider this as a “feature” of this API, but it’s actually due the fact that the API used for site collection creation or the tenant admin assembly is directly ported from the SharePoint Online and the code still has some historical leftovers from the past (yes – it shouldn’t, but it does).

So – to make this API work in the on-premises, you’ll need to mark one of your site collections as tenant admin site collection. This could sound much more terrifying that what it actually means. In practice, you’ll need to chose the site collection, which will be used when you call the API to create new site collections and flip one property on that site collection, which does not have any other impact in on-premises. From consistency perspective, I’d create either specific empty site collection for this operation or use the root site collection of web application. Both are absolutely valid options. Here’s the code to perform this in practice from definetenantadminsite.ps1.

[sourcecode language='powershell' ]
param
(
[Parameter(Mandatory=$true)][ValidateNotNullOrEmpty()]
    [String]$siteColUrl
)
#
# Set admin site type property to the site collection using PS for any site collection type.
# This is needed to be set for the site collection which is used as the 
# "Connection point" for the CSOM when site collections are created in on-prem
#
  
$snapin = Get-PSSnapin | Where-Object {$_.Name -eq 'Microsoft.SharePoint.Powershell'}
if ($snapin -eq $null) 
{
    Write-Host "Loading SharePoint Powershell Snapin"
    Add-PSSnapin "Microsoft.SharePoint.Powershell"
}
 
$site = get-spsite -Identity $siteColUrl
$site.AdministrationSiteType = [Microsoft.SharePoint.SPAdministrationSiteType]::TenantAdministration

Write-Host "Site $siteColUrl set to AdministrationSiteType" $site.AdministrationSiteType
[/sourcecode]

After this step, you’ll be then good to and start provisioning site collections in SharePoint 2016 with CSOM. Needed code is exactly the same as shown in the SP2013 version of this blog post, so you can copy that from there. Notice that you’ll need to connect to the site collection URL, which you marked as your “tenant admin” site collection for the operations.

“Sharing is caring!”

Developer Keynote

Conference had a keynote for each of the main conference days with slightly different agenda, which worked out well.

• Tuesday – The Future of SharePoint is Now, Reinventing Content Collaboration with Dan Holme, Mike Ammerlaan and Chris McNulty
• Wednesday – Where Form Meets Function: Understanding Collaboration’s Cultural Fit with Christian Buckley and Benjamin Niaulin
• Thursday – What’s the future of SharePoint customizations? – by me, Erwin van Hunen and Paolo Pialorsi

Thursday’s keynote was really all around the developer story with SharePoint and where we are heading from a customization perspective. We had roughly 1200 attendees in the room and feedback was really great. Erwin and Paolo are both MVPs and also SharePoint PnP Core team members, so they are really well looped on what we do in engineering. This was also really fun thing to do with the three of us and it was nice to see that regardless of classic momentary network issues, everything went as planned. There’s always room for improvement, but let’s do that with the next setup.

We obviously covered the modern tool chain and and touched on numerous other development areas related on the SharePoint Online and on-premises. Key takeaways from the keynote in general were following:

• Future is bright for SharePoint developers
• SharePoint is a development platform
• Stay up to date with SharePoint Patterns and Practices

We also concentrated on the power of community and how everyone from the community can truly influence on the future of SharePoint by sharing their feedback and letting us in the engineering know what works and what doesn’t. Community influence to SharePoint roadmap has never been bigger and we truly want to help you where we can to achieve your business and technical objectives.

We absolutely also acknowledge that the modern SharePoint development model does require quite a lot of learning for existing SharePoint developers. This is something where we will try to also help as much as possible by providing training materials, guidance and samples. What’s though cool about the transition is that after you’ve done the leap for the modern technologies, you can use those learnings with other products as well, since modern SharePoint development is more and more aligning to industry standards by using web stack development tools and remote APIs.

You can find used presentation from the SharePoint PnP docs.com section.

Keynote demo 1 – Modern web parts and development experience

This demo was more around demonstrating the out of the box experience with modern out of the box web parts. Paolo showed how you can modify the modern pages and how to configure web parts using the modernized web part property pane. After the out of the box experience, he showed how developers have exactly the same control and modern development experience when they are implementing their own web parts.

We used following basic to-do web part as the sample implementation, which is available from the SharePoint GitHub repository . This sample was implemented by Chaks (Chakkaradeep Chinnakonda Chandran) while back as a reference sample for different client-side web part aspects.

Key takeaways

• Modern pages will have fluent and significantly improved end user experience to customize them
• Modern web parts are fluent and reactive in the way you configure them
• You can take advantage of all the different advantages and improvements in the modern experience with your customizations – you have access on same APIs and readiness to implement similar experiences as with out of the box web parts

Keynote demo 2 – Modern web stack development with SharePoint

In this second demo, we wanted to show that even though SharePoint Framework is currently only available in SharePoint Online, you can start adapting modern web stack development tooling in on-premises. We have communicated that the SharePoint Framework will be supported in the SharePoint 2016 during calendar year of 2017, but you can actually already today adapt modern development tooling and libraries in on-premises.

We demonstrated modern stack tooling on SharePoint 2016, SharePoint 2013 and SharePoint 2010 environments. This means using modern JavaScript libraries and tooling like React or Gulp in the context of these versions. You can start building your customizations with the modern tooling, which will help your adoption on moving to SharePoint Framework, when your environments will be updated to SharePoint 2016 or if you’ll be moving to SharePoint Online in future.

Notice thought that even though we showed SharePoint 2010 in the demo (nerd factor), it has slightly different story than with 2013 and 2016 version, due the differences in the REST API implementation. 2013 and 2016 are pretty similar from the REST API implementation perspective, but in SP2010 you only had pretty limited remote API with listdata.svc based implementation. This means that any work you’ll do in SP2010, would require significant changes from data layer perspective, before it could be moving to newer versions.

Key takeaways

• SharePoint Framework will be released also to SharePoint 2016 during calendar year of 2017
• SharePoint Framework will NOT be released to SharePoint 2013 or SharePoint 2010 versions
• You can use modern web stack tooling already today in your on-premises deployments
  • Amount of refactoring needed to adapt SharePoint Framework in SharePoint 2016 or SP Online depends on your major SharePoint version
• By adapting modern tooling and JavaScript libraries in on-premises, you’ll make the adaption of SharePoint Framework easier in future for you

Guidance on starting to use modern web development practices with SharePoint on-premises is work in progress. We are targeting to provide generic guidance for SharePoint 2013 and SharePoint 2016 on this model, so that you can more easily adapt the modern tooling. We won’t be targeting SharePoint 2010 with this, due the remote API differences and limitations.

You can see initial status and what was shown in the keynote from following repository: https://github.com/VesaJuvonen/react-app. This is just initial work started with help of Chakkaradeep (Chaks) Chinnakonda Chandran (this is forked from Chaks initial work) and Waldek Mastykarz. Just to repeat the message one more time – this does not mean that SPFx would be landing to SP2013 or SP2010, but you can take advantage of modern web stack tool chain in those platforms as well, which will then make adoption of new platforms easier for you, when you are upgrading to newer versions.

Here’s the modern web stack UI hosted in the SharePoint 2010 platform. This was done with content editor web part (CEWP), which was pointing to a txt file in the site collection with needed script references to JavaScript files hosted from local node.js service as a development experience.

Keynote demo 3 – Provisioning modern team sites with a bot using voice

Few weeks back we already got a nice Microsoft Bot Framework submission around the SharePoint Framework client-side web part samples from Gary Pretty. This really got the PnP team thinking around the different opportunities and possibilities with the bots. Objective of the demo was around demonstrating the integration opportunities cross different services in the Office 365 and how you can automate operations using the Microsoft Bot Framework.

In the demo, we used our custom bot called PnP SharePoint Manager in the Microsoft Teams from iPhone with voice. So basically we were able to command our bot to perform operations towards SharePoint Online using different devices and input options.

Key takeaways

• There are interesting opportunities for the customizations when you combine the different services available with Office 365
• Microsoft Bot Framework is a great platform for modern experiences and for automating operations cross your cloud deployments
• SharePoint Online has powerful APIs, which we can use remotely from different services

Notice. If you are interested on this bot framework demo more detailed, you can find a recording of almost identical setup from the PnP Core Special Interest Group recording from 16th of November. You can also jump directly to the demo b using following link: Remote provisioning with Microsoft Bot Framework using Microsoft Teams or SharePoint Framework client-side web part.

SharePoint Framework Workshop

We started the ESPC with the pre-day conference around developing SharePoint Framework client-side web parts. This was a fun day together with Mike Ammerlaan (Microsoft) and Eric Overfield (PixelMil). We had roughly 90 attendees in the room and we walkthrough the modern SharePoint development experience together with the audience. Agenda consistent from topics like following.

• Introduction SharePoint Framework
  • Overview
  • Tooling
  • Building client-side web parts
  • Office UI Fabric React
  • Lifecycle and deployment options
  • etc
• SharePoint and Microsoft Graph
• Webhooks in SharePoint

Hackathon

This year ESPC organized second annual SharePoint Hackathon as part of the conference. This session was hosted by Mike Ammerlaan and was also personally present to help with any questions around topics, which attendees were investigating or hacking. On the picture right , you can see how I concentrated on supporting the attendees in practice .

This was by far the best organized hackathon which have ever attended. ESPC organizers had ensured that we had cool swag for the attendees and we had our own waiter from hotel taking care of any requests around drinks or food. We had roughly 25 participants and all were highly committed on building something cool. Hackathon started on Tuesday evening around 6 PM with shared dinner and attendees or their teams where expected to submit their results as a video by Thursday morning 10 AM.

Submissions were really high quality and had different kind of technologies demonstrated in the context of SharePoint. Implementations varied from on-premises to SharePoint Online, using also mobile devices. Choosing a winner from these kind of submissions were really hard, but we could not give a Xbox unfortunately for all of them.

Winner team members were Andi Krüger and StephanKitzler-Walli. Guys demonstrated how to host and build SharePoint Framework style implementations in the on-premises using both farm solutions and add-in model as the underlying technique. Demonstration was really impressive and there was clearly a lot of time spent on making things happen.

Additional activities and notes

I also had one classic session to delivery by myself during the conference. This was around my not to use Feature Framework in SharePoint deployments for deploying assets or configurations to SharePoint sites. Key pointers of that session are following and you can also find slides for that below.

• Feature Framework is not flexible enough for managing your customizations – especially in maintenance cases where you’ll need to always fall back on code
• Start moving to remote API based approaches where suitable – with for example PnP Provisioning Engine
• There are multiple open source and commercial solutions available for replacing feature framework as the deployment tool for the assets and configurations

Would also like to thank the ESPC organizers on extremely well managed conference and also on the great speaker gifts. Each speaker got their very own personalized Lego figure. Here’s me, Erwin van Hunen and Markus Hintner hanging in the bar.

“Sharing is caring!”

SharePoint / Office 365 Dev Patterns and Practices (PnP) November 2016 release is out with new contributions from community for the community. This post contains all the details related on what was included with the release and what else has been happening in the PnP world during the past month.

What is SharePoint / Office Dev Patterns & Practices (PnP)?

PnP is community driven open source initiative where Microsoft and external community members are sharing their learning's around implementation practices for SharePoint and Office 365. Active development and contributions happen our GitHub projects under 'dev' branch and each month there will be a master merge (monthly release) with more comprehensive testing and communications.

PnP is owned and coordinated by SharePoint engineering, but this is work done by the community for the community. 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 PnP Core team and we are looking to extend the Core team with more community members.

Notice that since this is open source community program, there’s no SLAs for the support what we provide from program. You can use SharePoint Developer group in the Microsoft Tech Community for providing input and to ask any questions around the existing materials. If you are interested on getting more closely involved, please check the following guidance from our GitHub wiki or a referenced PnP Webcast.

• How to get started and contribute to Office 365 Dev PnP program? - Wiki
• Office Dev PnP Webcast – How to get started with Office Dev PnP? - Webcast
• Office Dev PnP Webcast – How to contribute to Office Dev PnP initiative? - Webcast

Some key statistics around PnP program from October 2016

• GitHub repository forks at different repositories 
  • PnP main repository - 1872
  • PnP Sites Core - 291
  • PnP PowerShell - 225
  • PnP JS Core - 82
• Unique visitors during past 2 weeks cross PnP repositories - 12515
• Unique visitors during past 2 weeks in SharePoint organization repositories - 2889
• Merged pull requests cross PnP repositories (cumulative) - 2571
• Closed issues and enhancements ideas cross PnP repositories (cumulative) - 1059
• PnP Core component NuGet package downloads - 54222
• Unique visitors in PnP MSDN pages during October 2016 - 18603
• Unique tenants using PnP CSOM Core component during October 2016 - 2592
• Http requests towards SharePoint Online from PnP CSOM Core Component during October 2016 - 817000000

Main resources around PnP program

• PnP under dev.office.com – http://aka.ms/SPPnP- One location for all the resources and news around PnP
• PnP GitHub - http://aka.ms/SPPnP-GitHub - main repository
• PnP MSDN pages - http://aka.ms/SPPnP-MSDN
• PnP Community Discussions - http://aka.ms/SPPnP-Community
• PnP Videos at YouTube - http://aka.ms/SPPnP-Videos
• PnP training package (videos in Channel 9) - http://aka.ms/OfficeDevPnPTraining
• Presentations at docs.com - http://aka.ms/SPPnP-Docs

November 2016 monthly community call

Agenda for the Tuesday 8th of November community call at 8 AM PDT / 5 PM CET:

• Summary on the November 2016 release and other program updates - Vesa Juvonen ~20 min
• Using Microsoft Bot Framework with SharePoint Framework (SPFx) - Vesa Juvonen - 10-15 min
• Modern team site provisionign and new PnP Microsoft Graph PowerShell Cmdlets - Bert Jansen - 10-15 min
• Latest on the PnP JS Core library and why it's a great tool for add-ins and SP Fx customizations - Patrick Rodgers - 10-15 min

Community call will get recorded and release to PnP YouTube channel typically within 24 hours after the recording is ended. If you have any questions, comments or feedback, please participate in our discussions in the new Microsoft Tech Community under SharePoint developer group.

PnP Sites Core, PnP PowerShell and provisioning engine Special Interest Group (SIG)

PnP Office Hours has be rebranded as Special Interest Group (SIG) for PnP Sites Core, PnP PowerShell and provisioning engine. This way attendees know what the calls are concentrating more efficiently and can decide which areas they want to be more closely involved. SIG calls are bi-weekly calls where we talk about PnP sites core and related topics. These calls have also free Q&A section, if you have any questions around SharePoint development in on-premises or in cloud. Need to get recommendation to your design or having hard time with some APIs? - Drop by, ask a question and we'll help you.

You can download invite for the bi-weekly meeting from following location.

• https://aka.ms/sppnp-core-sig-call

All SIG meetings are being recorded and are available for view from PnP YouTube Channel. Here's the latest recordings from the SIG or old office hour meetings kept after previous monthly communications.

• 2nd of November - Microsoft Graph Cmdlets, Programatic provisioning of modern team sites, GitHub changes for PnP
• 19th of October - Modern team sites, PnP gallery cmdlets, NuGet package updates for CSOM 
• 5th of October - PnP Template Gallery demo, upcoming NuGet packages for on-premises, Ignite preview

Notice. Next SIG for PnP Component / PowerShell will be on Wednesday 16th of November - If you have questions around these topics, please join this call and use the opportunity to ask questions from SP engineering and PnP Core team.

SharePoint Framework (SPFX) and JavaScript Special Interest Group (SIG)

SharePoint Framework and JavaScript Special Interest Group (SIG) has bi-weekly meetings to cover latest changes in the SharePoint Framework side, from engineering perspective and to cover also latest development related on the PnP JS Core library. These calls are designed to have 50%/50% of content and demos and there has been already great community demos on the new SharePoint Framework Client-side web parts. If you're interested on showing your code, just let us know.

• Invite to bi-weekly call - https://aka.ms/sppnp-js-sig-call
• Gitter (Around the PnP JS Core) - https://gitter.im/OfficeDev/PnP-JS-Core

All SPFx and JS SIG meetings are recorded, so that you can check the demos and discussions, if you cant' make the actual call. You can find the latest recordings from the PnP YouTube Channel. Here's the latest recordings.

• 27th of October - Latest on SharePoint Framework, bot framework with SP Fx, React Todo Webpart
• 13th of October - Latest on SharePoint Framework, elevated priviledges with SP Fx, latest on PnP JS Core

Notice. Next SIG for SharePoint Framework and JavaScript development will be on Thursday 10th of November - If you have questions around these topics, please join this call and use the opportunity to ask questions from SP engineering and PnP Core team.

PnP Weekly Webcasts

We started new PnP Weekly Webcast series on October 2015 and have continued releasing new videos since that. All new webcasts are released in PnP YouTube Channel. Old webcasts and other demo videos are also found from the PnP Channel 9 section. Here's the new web casts released after the last monthly release.

• 7th of November - Reuse your existing JavaScript libraries with SharePoint Framework
• 31st of October - Building a sample search web part with SharePoint Framework using React
• 24th of October - PnP CSOM Core component and PowerShell test automation
• 17th of October - Azure AD implicit flow with SPFx client-side web part (developer preview)
• 10th of October - Introduction to PnP Templates Gallery

PnP repositories in GitHub

There are quite a few different GitHub repositories under the PnP brand since we wanted to ensure that you can easily find and reuse what's relevant for you. We do also combine multiple solutions to one repository, so that you can more easily sync and get latest changes of our released guidance and samples. In general we do recommend you to use the PnP sample search tool at dev.office.com for locating relevant material for you. This should be easier and faster than trying to locate relevant material from GitHub.

Here's the current repository structure, including short description for each of them.

• PnP - Main repository for SP add-in, Microsoft Graph etc. samples
• PnP-Guidance - Guidance, presentations and articles which are partly sync'd to MSDN
• PnP-Sites-Core - Office Dev PnP Core component
• PnP-JS-Core - Office Dev PnP Core component for JavaScript
• PnP-PowerShell - Office Dev PnP PowerShell Cmdlets
• PnP-Tools - New repository for tools and scripts targeted more for IT Pro's and for on-premises for SP2013 and SP2016
• PnP-Office-Addins - Office Add-in samples and models (starting)
• PnP-Partner-Pack - Packaged guidance with detailed instructions on setting things up in Office 365 and in Azure.
• PnP-Transformation - Material specifically for the transformation process. Currently includes samples around InfoPath replacement and transformation tooling from farm solutions to add-in model.
• PnP-OfficeAddins - Samples for the Office Add-ins development
• PnP-Provisioning-Templates - Source for templates available from PnP Template Gallery at http://templates-gallery.sharepointpnp.com
• PnP-Provisioning-Schema - PnP Provisioning engine schema repository

On top of the specific PnP repositories, PnP initiative also controls the new repositories under the SharePoint organization. PnP is owned nowadays by SharePoint engineering and we will be using PnP as the channel and forum to faciliate community work.

• SP-Dev-Docs - Source for new SharePoint dev center documentation exposed from http://dev.office.com/sharepoint
• SP-Dev-Fx-WebParts - Client-side web part samples from community and engineering
• SP-Dev-Samples - Samples for add-ins, webhooks and other APIs

What's supportability story around PnP material?

Following statements apply cross all of the PnP samples and solutions, including samples, core component(s) and solutions, like PnP Partner Pack.

• PnP guidance and samples are created by Microsoft & by the Community
• PnP guidance and samples are maintained by Microsoft & community
• PnP uses supported and recommended techniques
• PnP implementations are reviewed and approved by Microsoft engineering
• PnP is open source initiative by the community – people who work on the initiate for the benefit of others, have their normal day job as well
• PnP is NOT a product and therefore it’s not supported through Premier Support or other official support channels
• PnP is supported in similar ways as other open source projects done by Microsoft with support from the community by the community
• There are numerous partners that utilize PnP within their solutions for customers. Support for this is provided by the Partner. When PnP material is used in deployments, we recommend to be clear with your customer / deployment owner on the support model

Latest changes

SharePoint Framework samples

These are samples which are available from the SharePoint client-side web part sample repository at https://github.com/SharePoint/sp-dev-fx-webparts.

• New sample angular-migration showing how to migrate existing Angular applications to SharePoint Framework
• New sample angular-multipage showing how to manage UI state with Angular client-side web part with multiple views
• New sample angular-search showing how to implement client-side web part with Angular, whcih uses search APIs for getting information from sites
• New sample angular2-prototype showing how to build client-side web parts with Angular2
• New sample js-display-list showing simplistic client-side web part to render list items from existing lists in SharePoint
• New sample knockout-dependent-properties showing how to build custom components with Knockout and how to create dependent properties with property pane
• New sample react-aad-webapi which shows how to call custom web api secured with Azure AD from client-side web part
• New sample react-bot-framework which is a conceptual demo on how to use Microsoft bot framework in the context of client-side web part
• New sample react-custompropertypanecontrols which is showing how to build custom property pane control when you have complex property pane UX to show for end users
• New sample react-real-time which is showing how to build real time news feed using Microsoft Flow, Azure and socket.io
• New sample react-sp-elevatedprivileges which is showing how to perform elevated privileges operations to SharePoint from WebAPI which is called from client-side web part
• New sample react-todo-basic illustrating multiple different client-side web part patterns in React. Includes place holder control usage, advance scenarios for property pane and many other concepts for client-side web parts

PnP CSOM Core and Provisioning Engine

PnP CSOM Core component is a wrapper on top of native CSOM and REST, which simplifies complex scenarios with remote APIs, one of the example is the PnP Provisioning Engine for remote templates. The first version of the PnP remote provisioning engine was released with the May 2015 release. For the November 2016 release we have continued to add new supported capabilities and made significant improvements from stability perspective for both SharePoint Online and SharePoint on-premises (2013 and 2016). This list contains the main updates that have been added in the November 2016 release:

• General overall quality and performance improvements for on-premises and online
• Support for creating modern team sites with Microsoft Graph
• Minimal support for applying customizations to modern team sites using PnP Provisioning Engine
• Unit/integration test improvements
• Updated base templates for the SPO, 2013 and 2016 - used in delta handling

See also https://testautomation.sharepointpnp.com for day-to-day results and executed tests.

PnP JavaScript Core library v1.0.6

PnP JavaScript Core Library will move to version 1.0.6. This is JavaScript library which will increase productivity of developers when you are developing JavaScript based customizations on top of SharePoint. Library has been released as a npm package and you can find the source code from GitHub. PnP JS Core library is being developed and coordinated by the PnP Special Interest Group for SPFx and JavaScript, which has weekly meetings around this development effort and general topics on upcoming SharePoint Framework. PnP JS Core library is developed using typical open source web stack tooling, so that it's fully aligned on the development models with SP Framework. 

This is similar effort as what PnP initiative previously has done with the PnP CSOM Core Component together with community. 

v1.0.6 is coming out early November with following capabilities.

• Improved support for reading and writing files
• Improved logging of failed HTTP requests
• Support for the search suggest API
• Improved batch scoping for web and site instances

• Fixed an issue when using node authentication with client secrets with certain special characters.
• Fixed an issue where results were undefined when using paging with items and odata=verbose.
• Fixed an issue where the expiration date wasn't being passed along in the caching wrapper's getOrPut method.
• Fixed an issue where Refiners were not working as expected with search.
• Fixed a bug that prevented the promise returned from batch.execute to resolve when a batch had internal dependencies (adding or updating a list item). Also restructured how the results are aggregated into a promise chain and returned to ensure batch.execute's promise resolved AFTER all of the batch promises.’

PnP PowerShell

PnP PowerShell providers more than hundred additional PowerShell cmdlets, which can be used to manipulate content in SharePoint Online and in on-premises (SP2013, SP2016). These cmdlet's are additive for SharePoint Online management shell, which concentrate more on the administrative tasks with SharePoint Online. 

Here's the latest changes in the PnP PowerShell

• Cmdlet prefix change from SPO to PnP
• Notice that your existing scripts also still work due alias entries for both, but we do recommend updating gradually your scripts to use PnP prefix with PnP PowerShell
• Marked Get-SPOSite as deprecated. Use Get-PnPSite instead.
• New Cmdlets for Graph:
  • Connect-PnPMicrosoftGraph
  • New-PnPUnifiedGroup
  • Get-PnPUnifiedGroup
  • Remove-PnPUnifiedGroup
• Fixed Set-SPOTheme to support Non-Classic sites/Modern sites
• Overall quality improvements and bug fixes
• Updated documentation for Cmdlets

PnP sample library

Here's updates cross the PnP code sample library by the community on the code and documentation, which is great way to contribute as well.

• Updated script SharePoint.Hybrid.CloudSSA.Configuration designed for configuring a SharePoint Server farm with a hybrid Cloud Search Service Application
• Updated sample Provisioning.PnPDeployer.Console which is a console application that makes it easy to deploy artifacts to SharePoint On-Premises or Online. Based on the PnP Provisioning Engine, it wraps the engine's main functionalities and provides a new layer responsible for handling tokens, authentication, sequences and logging.
• pdated Solution Business.O365StarterIntranet Intranet projects shouldn’t have to reinvent the wheel every time for basic features (like navigation or multilingualism). This solution aims to provide the fundamental building blocks of a common intranet solution with SharePoint Online/Office 365 through a lightweight client side solution using the latest web stack development tools and frameworks.
• Updated sample SharePoint.RESTAPI.SPApp to include additional accordion sample with knockout based UI
• Updates to the PnP Partner Pack
  • Fine tuning and polishing based on community input

PnP Guidance articles

The PnP Guidance repository contains guidance articles which are published at MSDN. Starting from end of May 2016 this process was changed to be fully automated and there's automatic contributors list in the MSDN side showing who have been providing updates to these documents. We are looking forward on your contributions around real life learnings in different areas. Read more details around this open publishing model from following blog post

• Contributing to Office Dev PnP and SharePoint PnP documentation just got easier

We did not release any new guidance articles during October, but updated some of the articles based on the community input.

See MSDN articles from the PnP MSDN section at http://aka.ms/OfficeDevPnPMSDN

PnP Guidance videos

You can find all PnP videos from our YouTube Channel at http://aka.ms/sppnp-vidoes. This location contains already significant amount of detailed training material, demo videos and community call recordings. Since last release communications, we did not release any individual videos on top of the Special Interest Group recordings and PnP Webcasts.

Since YouTube channel is relatively new, some of the PnP videos are also in the PnP Channel 9 video blog.

Key contributors for the November 2016 release

Here’s the list of active contributors (in alphabetical order) during past month in PnP repositories. PnP is really about building tooling together with the community for the community, so your contributions are highly valued cross the Office 365 customers, partners and obviously also at Microsoft.

Thank you for your assistance and contributions from the behalf of the community. You are making a difference!

• Adrian Diaz Cervera (Encamina) - AdrianDiaz81
• Andrew Koltyakov (Arvo Systems) - @AndrewKoltyakov
• Alex Terentiev - AJIXuMuK
• arheom GitHub alias
• Arjan Cornelissen (Sogeti) - @arjancornelis
• Chuck Cassel - casselc
• David Hartman (Slalom) - davidhartman
• Edouard Shaar
• Erwin van Hunen (Rencore) - @erwinvanhunen
• Elio Struyf - @eliostruyf
• Franck Cornu (CGI) - @FranckCornu
• Gary Pretty (Mando) - @GaryPretty
• Gavin Barron - @gavinbarron
• Ivan Vagunin (Knowit AB) - @ivagunin
• Jean-Sebastien PADOAN - THE-SENSEI
• Jens Otto Hatlevold (Bouvet AS) - jensotto
• John Liu (SharePoint Gurus) - @johnnliu
• KEMiCZA GitHub alias 
• Luis Mañez (ClearPeople) - @luismanez
• Martin Segelfeldt (Knowit AB) - Segelfeldt
• Naamat Al-Aswad (Grace Software Consulting) - nalaswad
• Paolo Pialorsi (PiaSys.com) - @PaoloPia
• paulwillen GitHub alias
• Pieter Veenstra (Triad) - @PieterVeenstra
• Radi Atanassov (OneBit Software) - @RadiAtanassov
• reshmee011 GitHub alias
• Santha Kumar T - @ktskumar
• Simon-Pierre Plante (SPP Technologies) - spplante
• Todd Baginski (Canviz) - @toddbaginski
• Waldek Mastykarz (Rencore) - @waldekm
• Vardhaman Deshpande - @vrdmn
• Wictor Wilen (Avanade) - @wictor
• Yousry Mohamed – ylashin

Companies: Here's the companies, which provided support for PnP initiative for this month by allowing their employees working for the benefit of others in the PnP initiative. There were also people who contributed from other companies during last month, but we did not get their logos and approval to show them on time for this communications. If you still want your logo for this month's release, please let us know and share the logo with us. Thx.

Microsoft people: Here’s the list of Microsoft people who have been closely involved on the PnP work during last month.

• Antons Mislevics (Microsoft) - antonsmislevics
• Bert Jansen (Microsoft) - @O365Bert
• Brian Michely (Microsoft) - @brianmichely
• Chakkaradeep (Chaks) Chinnakonda Chandran (Microsoft) - @chakkaradeep
• Charles Mullins (Microsoft) - charlmu
• Dan Budimir (Microsoft) - MSDN blog
• Daniel Gaeta (Microsoft)
• Frank Marasco (Microsoft) - @frank_marasco
• Kiki Shuxteau (Microsoft)
• Laura Graham (Microsoft) - Lauragra
• Olivier Carpentier (Microsoft) - @OlivierC
• Patrick Rodgers (Microsoft) - @mediocrebowler
• Vesa Juvonen (Microsoft) - @vesajuvonen

Latest traffic statistics

Here's traffic statistics from the PnP, PnP PowerShell, PnP Sites Core (.NET) and JavaScript Core component repositories.

Traffic at PnP repository

Traffic from PnP Sites Core repository

Traffic from PnP PowerShell repository

Traffic from PnP JavaScript Core Component repository

See About Repository Graphs for more details on above statistics.

Next steps

• November 2016 monthly community call is on 8th of November at 8 AM PDT / 5 PM CET for latest release details with demos - Download invite with detailed schedule for your time zone from http://aka.ms/sppnp-call.

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 7th of November 2016]]> https://docs.microsoft.com/archive/blogs/vesku/ignite-2016-latest-on-sharepoint-office-365-patterns-and-practices-initiative Thu, 06 Oct 2016 15:47:34 GMT https://blogs.msdn.microsoft.com/vesku/?p=1515 Had a great trip to drop by at Atlanta for Ignite 2016 last week and now that the videos are out, wanted to also share the slides at least for the main PnP session. I personally had 3 sessions this time and “luckily” they all happened on the same day, which is always fun. Main session personally was the session around the SharePoint / Office 365 Dev Patterns and Practices initiative and how we will work in the future around the upcoming SharePoint capabilities.

Here’s the PnP session details and below are the available resources

• Title - Learn about PnP and the new SharePoint Framework
• Description - Office 365 Dev and SharePoint Patterns & Practices (PnP) helps customers move forward whether building solutions for today or tomorrow. Get latest update on the provided samples, reusable components and practices. See also what the PnP team is doing to support the new Microsoft SharePoint Framework and how you can participate to this community driven initiative.

Recording of the session is available from YouTube.

Slides used in this session are available for your from the SharePoint / Office 365 PnP docs.com site.

PnP initiative also had it’s own booth in the expo area where we did had 6 of the PnP Core team members ready to answer any questions on the SharePoint development. This was really nice setup and had numerous great discussions on the past, current and future models for SharePoint. Thx for dropping by and let’s continue discussion in the SharePoint Developer group under Microsoft Technical Network.

In this picture from left to write: Vesa Juvonen, Patrick Rodgers, Frank Marasco, Erwin van Hunen, Paolo Pialorsi and Radi Atanassov.

Sharing is caring!

Office 365 and SharePoint Patterns and Practices (PnP) September 2016 release is out with new contributions from community for the community. This post contains all the details related on what was included with the release and what else has been happening in the PnP world during the past month.

What is SharePoint / Office Dev Patterns & Practices (PnP)?

PnP is community driven open source initiative where Microsoft and external community members are sharing their learning's around implementation practices for SharePoint and Office 365. Active development and contributions happen our GitHub projects under 'dev' branch and each month there will be a master merge (monthly release) with more comprehensive testing and communications.

This is work done by the community for the community without any actual full time team members. 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 PnP Core team and we are looking to extend the Core team with more community members.

Notice that since this is open source community program, there’s no SLAs for the support what we provide from program. You can use SharePoint Developer group in the Microsoft Tech Community for providing input and to ask any questions around the existing materials. If you are interested on getting more closely involved, please check the following guidance from our GitHub wiki or a referenced PnP Webcast.

• How to get started and contribute to Office 365 Dev PnP program? - Wiki
• Office Dev PnP Webcast – How to get started with Office Dev PnP? - Webcast
• Office Dev PnP Webcast – How to contribute to Office Dev PnP initiative? - Webcast

Some key statistics around PnP program from September 2016 release

• GitHub repository forks at different repositories 
  • PnP main repository - 1759
  • PnP Sites Core - 262
  • PnP PowerShell - 193
  • PnP JS Core - 66
• Yammer group members - 4695
• Unique visitors during past 2 weeks cross PnP repositories - 11326
• Unique visitors during past 2 weeks in SharePoint organization repositories - 3857
• Merged pull requests cross PnP repositories (cumulative) - 2295
• Closed issues and enhancements ideas cross PnP repositories (cumulative) - 815
• PnP Core component NuGet package downloads - 45845
• Unique visitors in PnP MSDN pages during August 2016 - 29438

Main resources around PnP program

• PnP under dev.office.com – http://aka.ms/SPPnP- One location for all the resources and news around PnP
• PnP GitHub - http://aka.ms/SPPnP-GitHub - main repository
• PnP MSDN pages - http://aka.ms/SPPnP-MSDN
• PnP Community Discussions - http://aka.ms/SPPnP-Community
• PnP Videos at YouTube - http://aka.ms/SPPnP-Videos
• PnP training package (videos in Channel 9) - http://aka.ms/OfficeDevPnPTraining
• Presentations at docs.com - http://aka.ms/SPPnP-Docs

September 2016 monthly community call

Agenda for the Tuesday 13th of September community call at 8 AM PDT / 5 PM CET:

• Summary on the September 2016 release and other program updates - Vesa Juvonen ~20-25 min
• What's new in PnP Partner Pack v2.0 - Paolo Pialorsi (Piasys.com) ~10-15 min
• Demo on new PnP Starter Intranet for SharePoint Online solution - Franck Cornu (CGI) ~10-15 min
• Demo on new SharePoint.React.SupportTicket sample - Brian Michely (Microsoft) ~10-15 min

If you have any questions, comments or feedback, please participate in our discussions in the new Microsoft Tech Community under SharePoint developer group. Notice that since Yammer Office 365 network will be shut down on 15th of September, would recommend moving the questions and discussions to new Microsoft Tech Community, so that we can continue the lively discussion around the PnP initiative as well.

PnP Office Hours

PnP Office Hours are bi-weekly calls where we talk about different topics around SharePoint engineering side and what's under development with PnP core team. These calls have also free Q&A section, if you have any questions around SharePoint development in on-premises or in cloud. Need to get recommendation to your design or having hard time with some APIs? - Drop by and we'll help you.

You can download invite for the bi-weekly meeting from following location.

• http://aka.ms/SPPnP-OfficeHours

All PnP Office Hours are being recorded and are available for view from PnP YouTube Channel. Here's the latest office hour recordings.

• 10th of August - Office Hours
• 24th of August - Office Hours
• 7th of September - Office Hours

Notice. Next Office Hours will be on Wednesday 21st of September.

SharePoint Framework (SPFX) and JavaScript Special Interest Group (SIG)

harePoint Framework and JavaScript Special Interest Group (SIG) has weekly meetings to cover latest changes in the SharePoint Framework side, from engineering perspective and to cover also latest development related on the PnP JS Core library. These calls are designed to have 50%/50% of content and demos and there has been already great community demos on the new SharePoint Framework Client-side web parts. If you're interested on showing your code, just let us know.

• Invite to weekly call - http://aka.ms/sppnp-js-sig-call
• Gitter (Around the PnP JS Core) - https://gitter.im/OfficeDev/PnP-JS-Core

All SPFx and JS SIG meetings are recorded, so that you can check the demos and discussions, if you cant' make the actual call. You can find the latest recordings from the PnP YouTube Channel. Here's the latest office hour recordings.

• 11th of August - PnP SPFx and JS SIG
• 18th of August - PnP SPFx and JS SIG
• 26th of August - PnP SPFx and JS SIG
• 1st of September - PnP SPFx and JS SIG
• 8th of September - PnP SPFx and JS SIG
  

PnP Weekly Webcasts

We started new PnP Weekly Webcast series on October 2015 and have continued releasing new videos since that. All new webcasts are released in PnP YouTube Channel. Old webcasts and other demo videos are also found from the PnP Channel 9 section. Here's the new web casts released after the last monthly release.

• 8th of August - Integrating Angular 1.x to SharePoint Framework Client Side web part
• 15th of August - PnP PowerShell - Getting started with latest updates
• 22nd of August - Building simple SharePoint Framework Client Web Part
• 29th of August - Building Angular SharePoint Framework Client Web Part
• 5th of September - Getting started with SharePoint Webhooks
• 12th of September - Referencing external JavaScript libraries from your client-side web part

PnP repositories in GitHub

There are quite a few different GitHub repositories under the PnP brand since we wanted to ensure that you can easily find and reuse what's relevant for you. We do also combine multiple solutions to one repository, so that you can more easily sync and get latest changes of our released guidance and samples. In general we do recommend you to use the PnP sample search tool at dev.office.com for locating relevant material for you. This should be easier and faster than trying to locate relevant material from GitHub.

Here's the current repository structure, including short description for each of them.

• PnP - Main repository for SP add-in, Microsoft Graph etc. samples
• PnP-Guidance - Guidance, presentations and articles which are partly sync'd to MSDN
• PnP-Sites-Core - Office Dev PnP Core component
• PnP-JS-Core - Office Dev PnP Core component for JavaScript
• PnP-PowerShell - Office Dev PnP PowerShell Cmdlets
• PnP-Tools - New repository for tools and scripts targeted more for IT Pro's and for on-premises for SP2013 and SP2016
• PnP-Office-Addins - Office Add-in samples and models (starting)
• PnP-Partner-Pack - Packaged guidance with detailed instructions on setting things up in Office 365 and in Azure.
• PnP-Transformation - Material specifically for the transformation process. Currently includes samples around InfoPath replacement and transformation tooling from farm solutions to add-in model.
• PnP-OfficeAddins - Samples for the Office Add-ins development
• PnP-Provisioning-Schema - PnP Provisioning engine schema repository

On top of the specific PnP repositories, PnP initiative also controls the new repositories under the SharePoint organization. PnP is owned nowadays by SharePoint engineering and we will be using PnP as the channel and forum to faciliate community work.

• SP-Dev-Docs - Source for new SharePoint dev center documentation exposed from http://dev.office.com/sharepoint
• SP-Dev-Fx-WebParts - Client-side web part samples from community and engineering
• SP-Dev-Samples - Samples for add-ins, webhooks and other APIs

What's supportability story around PnP material?

Following statements apply cross all of the PnP samples and solutions, including samples, core component(s) and solutions, like PnP Partner Pack.

• PnP guidance and samples are created by Microsoft & by the Community
• PnP guidance and samples are maintained by Microsoft & community
• PnP uses supported and recommended techniques
• PnP implementations are reviewed and approved by Microsoft engineering
• PnP is open source initiative by the community – people who work on the initiate for the benefit of others, have their normal day job as well
• PnP is NOT a product and therefore it’s not supported through Premier Support or other official support channels
• PnP is supported in similar ways as other open source projects done by Microsoft with support from the community by the community
• There are numerous partners that utilize PnP within their solutions for customers. Support for this is provided by the Partner. When PnP material is used in deployments, we recommend to be clear with your customer / deployment owner on the support model

Latest changes

Provisioning Engine

The first version of the PnP remote provisioning engine was released with the May 2015 release. For the September 2016 release we have continued to add new supported capabilities and made significant improvements from stability perspective for both SharePoint Online and SharePoint on-premises (2013 and 2016). This list contains the main updates that have been added in the September 2016 release:

• General overall quality and performance improvements for on-premises and online
• Added support for IsVisible attribute for NavigationNode elements
• Significant unit/integration test improvements
• Updated base templates for the SPO, 2013 and 2016 - used in delta handling

See also https://testautomation.sharepointpnp.com/ for day-to-day results and executed tests.

PnP Partner Pack 2.0

We are happy to release PnP Partner Pack v2.0 with significant new capabilities for partners and customers to use in their SharePoint Online deployment. PnP Partner Pack is a starter kit for building typical SharePoint customizations using add-in model techniques. It's Azure AD based deployment, which provides centralized control on site templates and branding management, among the other things. Here's the key capabilities in the PnP Partner Pack v2.0:

• Architectural changes
  • Support for self-consistent Open XML .PNP template files, instead of .XML template files. Backward compatibility with already created .XML templates.
  • Support for external template providers, and out of the box provider for the new SharePoint PnP Templates Gallery.
  • Authorization layer to filter functionalities based on current user’s context.
• New Governance tools like:
  • Capability to apply company-wide branding (logo, color palette, fonts, background image, JS embedding, etc.) for sites and sites collections created, as well as for already created ones.
  • Capability to refresh/update templates for sites created with the PnP Partner Pack v. 2.0 in order to support solutions lifecycle management.
  • Asynchronous batch creation of site collections, based on an input XML file.
• Implementation and UI changes:
  • Updated to the latest release of PnP Core component and support for latest functionalities.
  • Fully re-branded using Office UI Fabric styles.
  • New set of MVC rendering templates supporting Office UI Fabric common components.
  • New People Picker control based on Office UI Fabric and Microsoft Graph.

PnP JavaScript Core library v1.0

PnP JavaScript Core Library has moved to version 1.0.4. This is JavaScript library which will increase productivity of developers when you are developing JavaScript based customizations on top of SharePoint. Library has been released as a npm package and you can find the source code from GitHub. PnP JS Core library is being developed and coordinated by the PnP Special Interest Group for SPFx and JavaScript, which has weekly meetings around this development effort and general topics on upcoming SharePoint Framework. PnP JS Core library is developed using typical open source web stack tooling, so that it's fully aligned on the development models with SP Framework. 

This is similar effort as what PnP initiative previously has done with the PnP CSOM Core Component together with community. 

You can read more details around the v1.0.4 capabilities from following release blog post at MSDN or from GitHub wiki pages:

• SharePoint Patterns and Practices SharePoint JavaScript Library 1.0.4
• PnP JS Core Library - GitHub Wiki pages
  

PnP library

Here's updates cross the PnP code sample library by the community on the code and documentation, which is great way to contribute as well.

• PnP Core: Lots of re-factoring done to improve code quality and completeness:
  • provisioning engine updates (see above)
  • Added support to set icon for weblogin form
  • Updates for timerjob framework related on app-only handling with SPO and on-premises versions
  • General bug fixing, performance and quality improvements
  • Updated to use latest CSOM version for SharePoint Online
  • Automated documentation updated to md file
  • Removal of deprecated methods (methods are 2 releases in the code after deprecation)
  • Build and test automation improvements with unit test changes
  • All PnP Core Nuget packages (Online, SP2013 and SP2016) updated with new version
• PnP JavaScript Core: Version 1.0.4 released:
  • Official v1.0.4 version released as npm package - check more details from following blog post
• New sample react-officegraph which illustrates how to Office Graph with SharePoint Framework (SPFx) client-side web parts
• New sample angular-ngofficeuifabric-todo which illustrates how to build SharePoint Framework (SPFx) client-side web part using Angular and ngOfficeUIFabric
• New sample WebHooks.List which is a reference implemention on making use of SharePoint webhooks in your applications
• New sample SharePoint.React.SupportTicket which illustrates how you can quickly build and package React forms with validation and send form data to a SharePoint list via the REST API
• New sample Provisioning.PnPDeployer.Console is a console application that makes it easy to deploy artifacts to SharePoint OnPremise/Online. Based on the PnP Provisioning Engine, it wraps the engine's main functionnalities and provides a new layer responsible for handling tokens, authentication, sequences and logging.
• New Solution Business.O365StarterIntranet Intranet projects shouldn’t have to reinvent the wheel every time for basic features (like navigation or multilingualism). This solution aims to provide the fundamental building blocks of a common intranet solution with SharePoint Online/Office 365 through a lightweight client side solution using the latest web stack development tools and frameworks.
• New Solution SharePoint.SandBoxTool which is a command line utility you can scan, download, analyze and if possible fix the sandbox solutions in your SharePoint environment. This tool uses multi-threading to improve performance, uses app-only permissions to be able to access all sites and can deal with throttling in case that would happen.
• Updated solution AspNetCore.Authentication An ASP.NET Core implementation of the TokenHelper and SharePointContext classes for use in SharePoint Apps. This library (and sample) demonstrates how to get ASP.NET Core provider-hosted apps authenticated through SharePoint. Updated to align with ASP.NET Core RTM version.
• Updated solution Provisioning.VSTools to support VS2015, including numerous improvements
• Updated PnP-PowerShell Commands with new CommandLets and with few fixes
  • Overall quality improvements and bug fixes
  • Added ClientTag based usage tracking for metrics
  • Updated Set-SPOTheme to support theme reset
  • Updated Set-DefaultColumnValues to support column defaults also for choice fields
  • Updated Apply-ProvisionignTemplate to support in-memory templates
  • Updated Add-SPOField to support associating site column to a list in sub site
  • Updated Add-SPOFile with better file handling logic with different file statuses
  • Updated Add-NavigationNode to fix issue with relative URLs
  • Added support for latest CSOM
  • Updates on the test cases
  • Updated help details for CmdLets
  • Updated documentation for CmdLets
• Updates to the PnP Partner Pack
  • As mentioned in specific chapter

PnP Guidance articles

The PnP Guidance repository contains guidance articles which are published at MSDN. Starting from end of May 2016 this process was changed to be fully automated and there's automatic contributors list in the MSDN side showing who have been providing updates to these documents. We are looking forward on your contributions around real life learnings in different areas. Read more details around this open publishing model from following blog post

• Contributing to Office Dev PnP and SharePoint PnP documentation just got easier

Here's new guidance articles since the last release communications

• Sandbox solution transformation guidance - Web Parts
• Sandbox solution transformation guidance - Event Receivers
• Sandbox solution transformation guidance - Feature Receivers
• Sandbox solution transformation guidance - InfoPath Forms with Code

See MSDN articles from the PnP MSDN section at http://aka.ms/OfficeDevPnPMSDN

PnP Guidance videos

You can find all PnP videos from our YouTube Channel at http://aka.ms/sppnp-vidoes. This location contains already significant amount of detailed training material, demo videos and community call recordings. Since last release communications, we have released one additional guidance video:

• SharePoint Sandbox Solution Scanner

Since YouTube channel is relatively new, some of the PnP videos are also in the PnP Channel 9 video blog.

Key contributors for the September 2016 release

Here’s the list of active contributors (in alphabetical order) during past month in PnP repositories. PnP is really about building tooling together with the community for the community, so your contributions are highly valued cross the Office 365 customers, partners and obviously also at Microsoft.

Thank you for your assistance and contributions from the behalf of the community. You are making a difference!

• Bill Ayers (Flow Simulation Ltd.) - @SPDoctor
• Dan Beaulieu - dbeaulieu
• Erwin van Hunen (Rencore) - @erwinvanhunen
• Elio Struyf - @eliostruyf
• Franck Cornu (CGI) - @FranckCornu
• John Liu (SharePoint Gurus) - @johnnliu
• Luis Mañez (ClearPeople) - @luismanez
• Mauricio nunes - mauricionr
• Michael Schau (WorkPoint A/S) - @SchauDK
• Michael Toole (Perficient, Inc.) - miket9884
• Paolo Pialorsi (PiaSys.com) - @PaoloPia
• Pieter Veenstra (Triad) - @PieterVeenstra
• Radi Atanassov (OneBit Software) - @RadiAtanassov
• Shantha Kumar T - sksnips
• Simon-Pierre Plante (SPP Technologies) - spplante
• Stephan Steiger (IOZ AG) - @robi26
• Thomas Berman (DQC Sverige) - thomasberman
• Todd Baginski (Canviz) - @toddbaginski
• Waldek Mastykarz (Rencore) - @waldekm
• Wictor Wilen (Avanade) - @wictor

Companies: Here's the companies, which provided support for PnP initiative for this month by allowing their employees working for the benefit of others in the PnP initiative. There were also people who contributed from other companies during last month, but we did not get their logos and approval to show them on time for this communications. If you still want your logo for this month's release, please let us know and share the logo with us. Thx.

Microsoft people: Here’s the list of Microsoft people who have been closely involved on the PnP work during last month.

• Antons Mislevics (Microsoft) - antonsmislevics
• Bert Jansen (Microsoft) - @O365Bert
• Brian Michely (Microsoft) - @brianmichely
• Chakkaradeep (Chaks) Chinnakonda Chandran (Microsoft) - @chakkaradeep
• Dan Budimir (Microsoft) - MSDN blog
• Frank Marasco (Microsoft) - @frank_marasco
• Kiki Shuxteau (Microsoft)
• Koen Zomers (Microsoft) - @koenzomers
• Laura Graham (Microsoft) - Lauragra
• Mike Morrison (Microsoft) - mike-morrison
• Olivier Carpentier (Microosft) - @OlivierC
• Patrick Rodgers (Microsoft) - @mediocrebowler
• Vesa Juvonen (Microsoft) - @vesajuvonen

Latest traffic statistics

Here's traffic statistics from the PnP, PnP PowerShell, PnP Sites Core (.NET) and JavaScript Core component repositories.

Traffic at PnP repository

Traffic from PnP Sites Core repository

Traffic from PnP PowerShell repository

Traffic from PnP JavaScript Core Component repository

See About Repository Graphs for more details on above statistics.

Next steps

• September 2016 monthly community call is on 13th of September at 8 AM PDT / 5 PM CET for latest release details with demos - Download invite with detailed schedule for your time zone from http://aka.ms/sppnp-call.

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 12th of September 2016

Office 365 and SharePoint Patterns and Practices (PnP) June 2016 release is out with new contributions from community for the community. This post contains all the details related on what was included with the release and what else has been happening in the PnP world during the past month.

What is Office 365 and SharePoint Patterns and Practices (PnP)?

PnP is community driven open source initiative where Microsoft and external community members are sharing their learning's around implementation practices for Office 365 in general and also 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.

This is work done by the community for the community without any actual full time team members. 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 PnP Core team and we are looking to extend the Core team with more community members.

Notice that since this is open source community program, there’s no SLAs for the support what we provide from program. There is however highly active PnP Yammer group, where you can get fast support on any questions around the existing materials. If you are interested on getting more closely involved, please check the following guidance from our GitHub wiki or a referenced PnP Web Cast.

• How to get started and contribute to Office 365 Dev PnP program? - Wiki
• Office Dev PnP Web Cast – How to get started with Office Dev PnP? - Web Cast
• Office Dev PnP Web Cast – How to contribute to Office Dev PnP initiative? - Web Cast

Some key statistics around PnP program from June 2016 release

• GitHub repository forks at different repositories 
  • PnP main repository - 1565
  • PnP Sites Core - 218
  • PnP PowerShell - 165
• Yammer group members - 4470
• Unique visitors during past 2 weeks cross PnP repositories - 11163
• Merged pull requests cross PnP repositories - 2313
• Closed issues and enhancements ideas cross PnP repositories - 636
• PnP Core component NuGet package downloads - 35026
• Unique visitors in PnP MSDN pages during May 2016 - 21963

Main resources around PnP program

• PnP under dev.office.com – http://aka.ms/OfficeDevPnP - One location for all the resources and news around PnP
• PnP GitHub - http://aka.ms/OfficeDevPnPGitHub - main repository
• PnP MSDN pages - http://aka.ms/OfficeDevPnPMSDN
• PnP Yammer group - http://aka.ms/OfficeDevPnPYammer
• PnP Videos at Channel 9 - http://aka.ms/OfficeDevPnPVideos
• PnP training package (videos in Channel 9) - http://aka.ms/OfficeDevPnPTraining
• Presentations at docs.com - http://docs.com/OfficeDevPnP
• PnP Guidance Repository – http://aka.ms/OfficeDevPnPGuidance

June 2016 monthly community call

Agenda for the Tuesday 14th of June community call at 8 AM PDT / 5 PM CET:

• Summary on the June release, community survey results and other updates in program - Vesa Juvonen ~20-25 min
• Demo on ASP.net Core SP Token handling - Radi Atanassov (OneBit Software) ~10-15 min
• Demo on PnP JavaScript Core component v1.0 and Yeoman template integration - Patrick Rodgers ~10-15 min
• Demo on new file handling capabilities in SPO in PnP PowerShell - Mårten af Sandeberg (Knowit AB) ~10-15 min

If you have any questions, comments or feedback, please participate in our discussions in the Office 365 Patterns and Practices Yammer group at http://aka.ms/OfficeDevPnPYammer. We already have more than 4400 members in this group with lively discussions on different SharePoint and Office 365 development related topics. This is the most active developer group in the Office 365 Technical network and we are absolutely proud and thankful of that.

PnP Office Hours and Special Interest Group (SIGs) for JavaScript development

We started bi-weekly PnP Office Hours during February 2016 for addressing questions on how to contribute towards PnP. These are open discussions around what the Core team is doing and where the community members can assist. This time is also open for discussions around design decisions, challenges and possible issues in the PnP deliverables. You can download invite for the bi-weekly invite from following location. Recording of these Office Hours are shared in the PnP Yammer group within 24 hours after the recording was done.

• http://aka.ms/OfficeDevPnPOfficeHours

Due constantly growing interest on the PnP program, we also are piloting Special Interest Groups (PnP SIGs), which are more targeted on specific topic, like SharePoint Client Side (JavaScript) development or other areas. We are currently piloting this model with SIG for Client Side development, which have had great interest. Client Side Development SIG is creating its own JavaScript Core component using normal web stack tooling, which aligns on the recently announced upcoming SharePoint Framework. Weekly calls are around 50%-50% on the JS Core component development and discussions around the upcoming SharePoint Framework.

• Yammer group – http://aka.ms/OfficeDevPnPYammerSPClient
• Invite to weekly call - http://aka.ms/OfficeDevPnPSPClientSIGCall

You can find more around PnP Office Hours and Special Interest Groups (SIGs) from following blog post or check the web cast around the JavaScript SIG for the specific details.

• Introducing Office Dev Patterns and Practices Office Hours and Interest Groups
• Office Dev PnP Web Cast – Introducing PnP JavaScript Special Interest Group
  

PnP Weekly Web Casts

We started new PnP Weekly Web Cast on October 2015 and have continued releasing new video web casts for each week. All web casts will be to the PnP Channel 9 section. Here's the new web casts released after the last monthly release.

• 9th of May - Getting started with the web stack in SharePoint development
• 15th of May - Getting started with SharePoint Framework
• 23rd of May - Introduction to Bulk UPA Custom Profile Properties Update API
• 30th of May - Preparing for SharePoint Framework - What should I learn?
• 6th of June - Introduction to Microsoft Graph .NET SDK

Notice that we'll have a summer break on the web cast publishing and the last web cast before the break will go out on Monday 20th of June 2016. We'll continue with web casts during August 2016.

PnP repositories in GitHub

There are quite a few different GitHub repositories under the PnP brand since we wanted to ensure that you can easily find and reuse what's relevant for you. We do also combine multiple solutions to one repository, so that you can more easily sync and get latest changes of our released guidance and samples. In general we do recommend you to use the PnP sample search tool at dev.office.com for locating relevant material for you. This should be easier and faster than trying to locate relevant material from GitHub.

Here's the current repository structure, including short description for each of them.

• PnP - Main repository for SP add-in, Microsoft Graph etc. samples
• PnP-Guidance - Guidance, presentations and articles which are partly sync'd to MSDN
• PnP-Sites-Core - Office Dev PnP Core component
• PnP-JS-Core - Office Dev PnP Core component for JavaScript
• PnP-PowerShell - Office Dev PnP PowerShell Cmdlets
• PnP-Tools - New repository for tools and scripts targeted more for IT Pro's and for on-premises for SP2013 and SP2016
• PnP-Office-Addins - Office Add-in samples and models (starting)
• PnP-Partner-Pack - Packaged guidance with detailed instructions on setting things up in Office 365 and in Azure.
• PnP-Transformation - Material specifically for the transformation process. Currently includes samples around InfoPath replacement and transformation tooling from farm solutions to add-in model.
• PnP-OfficeAddins - Samples for the Office Add-ins development
• PnP-Provisioning-Schema - PnP Provisioning engine schema repository

Note. We are looking again to do some level of refactoring of the PnP repositories due the upcoming model for the new SharePoint Framework. We'll come back on this slightly later when things are fully locked.

What's supportability story around PnP material?

Following statements apply cross all of the PnP samples and solutions, including samples, core component(s) and solutions, like PnP Partner Pack.

• PnP guidance and samples are created by Microsoft & by the Community
• PnP guidance and samples are maintained by Microsoft & community
• PnP uses supported and recommended techniques
• PnP implementations are reviewed and approved by Microsoft engineering
• PnP is open source initiative by the community – people who work on the initiate for the benefit of others, have their normal day job as well
• PnP is NOT a product and therefore it’s not supported through Premier Support or other official support channels
• PnP is supported in similar ways as other open source projects done by Microsoft with support from the community by the community
• There are numerous partners that utilize PnP within their solutions for customers. Support for this is provided by the Partner. When PnP material is used in deployments, we recommend to be clear with your customer / deployment owner on the support model

Latest changes

Provisioning Engine

The first version of the PnP remote provisioning engine was released with the May 2015 release. For the Juhe 2016 release we have continued to add new supported capabilities and made significant improvements from stability perspective for both Office 365 and on-premises. This list contains the main updates that have been added in the June 2016 release:

• General overall quality and performance improvements for on-premises and online
• New OpenXML based support for provisioning templates - When serializing template with assets, you can generate automatically .pnp file, which contains all the assets related on the template
• Support for lookup fields pointing from sub site to root web
• Support for folders in AzureStorageConnector
• Support for extracting multi-lingual resources values
• Other multi-lingual support improvements
• Updated base templates for the SPO, 2013 and 2016 - used in delta handling

We are planning to release new schema version and some new capabilities as part of the June 2016 release. This new version will contain few missing pieces from the current design, which will be also addressed gradually in the PnP provisioning engine.

PnP JavaScript Core library v1.0

Version 1.0 of the PnP JavaScript Core Library was released during this month. This is JavaScript library which will increase productivity of developers when you are developing JavaScript based customizations on top of SharePoint. Library has been released as a npm package and you can find the source code from GitHub. PnP JS Core library is being developed and coordinated by the PnP Special Interest Group for JavaScript, which has weekly meetings around this development effort and general topics on upcoming SharePoint Framework. PnP JS Core library is developed using typical open source web stack tooling, so that it's fully aligned on the future usage with SP Framework. 

This is similar effort as what PnP initiative previously has done with the PnP CSOM Core Component together with community. 

You can read more details around the v1.0 capabilities from following release blog post at MSDN or from GitHub wiki pages:

• SharePoint Patterns and Practices SharePoint JavaScript Library 1.0.0
• PnP JS Core Library - GitHub Wiki pages
  

PnP library

We have done general cleaning in the repository related on Nuget package updates and also removed some samples, which are no longer relevant. We are planning to continue these cleaning activities during the next months as well to streamline the repository and to combine some samples for reducing the overall number of similar samples.

There's also significant amount of general updates on the existing samples done by the community on the code and documentation, which is great way to contribute as well.

• PnP Core: Lots of re-factoring done to improve code quality and completeness:
  • provisioning engine updates (see above)
  • Eanbled and DisableResponsiveUI extension methods to web object
  • Support for adding navigation nodes at beginning or end
  • Set SearchCenter URLs at site level
  • Extension methods to start a new workflow instance from web or site level
  • Convert a folder to document set
  • General bug fixing, performance and quality improvements
  • Updated to use latest CSOM version for SharePoint Online
  • Automated documentation updated to md file
  • Removal of deprecated methods
  • Build and test automation improvements with unit test changes
  • All PnP Core Nuget packages (cloud and on-premises) updated with new version
• PnP JavaScript Core: Version 1.0 finalized:
  • Official v1.0 version released as npm package
• New sample SharePoint.PnP-JS-Core with set of interactive demos for using the PnP JavaScript Core Library. Implemented as a SharePoint hosted add-in, so that you can easily try them out and see live results
• New sample Core.DownloadMultipleFilesJS that shows how to add download multiple files functionality to SharePoint document libraries by adding "download all files" and "download files as zip" to library ribbon as custom actions.
• New sample BusinessApps.O365ProjectsApp which contains code samples for upcoming book "Programming Office 365" for Microsoft Press. In particular it contains samples for: Office 365 Applications, Remote Timer Job and Graph SDK
• New solution AspNetCore.Authentication An ASP.NET Core implementation of the TokenHelper and SharePointContext classes for use in SharePoint Apps. This library (and sample) demonstrates how to get ASP.NET Core provider-hosted apps authenticated through SharePoint.
• Updated Provisioning.Extensibility sample to use latest extensibility interface
• Updated Core.EmbedJavaScript.HeaderFooter sample with small bug fixes
• Updated Core.ProfilePictureUploader to support multi-lingual my sites as well
• Updated Core.TaxonomyPicker component with small styling fixes and improved handling of the dom structure updates
• Updated Provisioning.UX.App provisioning solution with small updates
• Updated solution Provisioning.VSTools with small adjustments and bug fixes
• Updated PnP-PowerShell Commands with new CommandLets and with few fixes
  • Overall quality improvements and bug fixes
  • Added support for new pnp OpenXML templates
  • -CreateDrive option for Connect-SPOnline CmdLets for file system like access to SPO sites
  • New CmdLet Get-SPOFolderItem for file access in SPO
  • New CmdLets Enable-SPOResponsiveUI and Disable-SPOResponsiveUI for applying PnP Responsive UI package to sites with single Cmdlet call
  • New CmdLet Add-SPODocumentSet to add a new document set
  • New CmdLet Remove-SPOFolder
  • Updated help details for CmdLets
  • New Invoke-SPOWebAction Cmdlet which lets to iterate sites, lists and lsit items and execute provided delegated methods on the target.
  • Updated documentation for CmdLets
• Updates to the PnP Partner Pack
  • Small adjustments around the implementation for upcoming v2.0 release (later)
  • Setup guidance improvements
  • Updated to use the latest Nuget package for SharePoint Online

PnP Guidance articles

he PnP Guidance repository contains guidance articles which are published at MSDN. Starting from end of May this process was changed to be fully automated and there's automatic contributors list in the MSDN side showing who have been providing updates to these documents. We are looking forward on your contributions around real life learnings in different areas. Read more details around this open publishing model from following blog post

• Contributing to Office Dev PnP and SharePoint PnP documentation just got easier

Here's a sample article with Contribute option and list of contributors for it

As part of this change, we also released significant amount of new content in the MSDN. You can find for example farm solution to add-in model transformation recipes in the MSDN now at following location

• SharePoint add-in recipes

See MSDN articles from the PnP MSDN section at http://aka.ms/OfficeDevPnPMSDN

PnP Guidance videos

We did not release any new guidance videos during this month on top of the new web cast videos mentioned already above in this blog post. You can find all PnP videos from our Channel 9 section at http://aka.ms/OfficeDevPnPVideos. This location contains already significant amount of detailed training material, demo videos and community call recordings. We are considering option to move to Youtube with the video channel for more control with play lists, so that you can find more easily what you are looking for.

Key contributors for the June 2016 release

Here’s the list of active contributors (in alphabetical order) during past month in PnP repositories. PnP is really about building tooling together with the community for the community, so your contributions are highly valued cross the Office 365 customers, partners and obviously also at Microsoft.

Thank you for your assistance and contributions from the behalf of the community. You are making a difference!

• Alex Angas - @AlexAngas
• Alexander Shelopukho (VirtoSoftware) - biogenez
• Arto Kaitosaari (Affecto Oy) - @artokai
• Bruno Krieger (IOZ AG) - brunokrieger
• casselc GItHub alias - casselc
• Christian Glessner (Experts Inside GmbH) - cglessner
• Eric Scott Owens (Computer Enterprises Inc.) - eric-scott-owens
• Erwin van Hunen (Rencore) - @erwinvanhunen
• Daniel Laskewitz (Sogeti) - @laskewitz
• Danny Engelman (365CSI.com) - @Danny_Engelman
• Derek Smith - derek-smith
• Dragan Panjkov - @panjkov
• Gautam Sheth (Rapidcircle) - gautamdsheth
• Ivan Vagunin (Knowit Oy) - @ivagunin
• Ivaylo Kunev - pr0peller
• Jens Otto Hatlevold (Bouvet ASA) - jensotto
• Kim Pihlström (Onsight) - @kimpihlstrom
• Lars Fernhomberg - lafe
• Leo Forner - lforner
• Luis Mañez (ClearPeople) - @luismanez
• Marc D Anderson (Sympraxis Consulting LLC) - @sympmarc
• Massimo Prota (Rapid Circle) - @massimoprota
• Mårten af Sandeberg (Knowit AB) - afsandeberg
• Martin Lingstuyl (I4-You Business Solutions) - martinlingstuyl
• Martin Segelfeldt (Knowit AB) - Segelfeldt
• Michael Schau (WorkPoint A/S) - @SchauDK
• Michael Toole (Perficient, Inc.) - miket9884
• Mikael Svenson (Puzzlepart) - @mikaelsvenson
• Nigel Price - @Nigel_Price
• Oaden GitHub alias - Oaden
• Ole Kristian Mørch-Storstein (Puzzlepart) - Blog
• Ole Martin Pettersen (Puzzlepart AS) - @olemartinit
• Paolo Pialorsi (PiaSys.com) - @PaoloPia
• Patrik Björklund (Cognit Consulting AB) - @pbjorklund
• Pieter Veenstra (Bluesource) - @PieterVeenstra
• Radi Atanassov (OneBit Software) - @RadiAtanassov
• Ronald Booden (www.booden.net)
• Russell Gove - russgove
• Stefan Bauer (n8d.at) - @StfBauer
• Stephan Steiger (IOZ AG) - @robi26
• Tobias West (SCC) - tobiaswest83
• Velin Georgiev (OneBit Software) - @VelinGeorgiev
• Waldek Mastykarz (Rencore) - @waldekm
• Will Don - nerdondon
• 2P2-Anthony alias - 2P2-Anthony

Companies: Here's the companies, which provided support for PnP initiative for this month by allowing their employees working for the benefit of others in the PnP initiative. There were also people who contributed from other companies during last month, but we did not get their logos and approval to show them on time for this communications. If you still want your logo for this month's release, please let us know and share the logo with us. Thx.

Microsoft people: Here’s the list of Microsoft people who have been closely involved on the PnP work during last month.

• Alex Randall (Microsoft) - @alex_randall_
• Antons Mislevics (Microsoft) - GitHub
• Bert Jansen (Microsoft) - @O365Bert
• Brian Michely (Microsoft) - @brianmichely
• Dan Budimir (Microsoft) - MSDN blog
• David Rei (Microsoft) - MSDN blog
• Frank Marasco (Microsoft) - @frank_marasco
• Kiki Shuxteau (Microsoft)
• Laura Graham (Microsoft) - Lauragra
• Mike Morrison (Microsoft) - mike-morrison
• Neil Hodgkinson (Microsoft) - GitHub
• Patrick Rodgers (Microsoft) - GitHub
• Roberto Sonnino (Microsoft) - @robertos_br
• Roy Harper (Microsoft) - roharp
• Vesa Juvonen (Microsoft) - @vesajuvonen
  

Latest traffic statistics

Here's traffic statistics from the PnP, PnP PowerShell, PnP Sites Core (.NET) and JavaScript Core component repository.

Traffic at PnP repository

Traffic from PnP Sites Core repository

Traffic from PnP PowerShell repository

Traffic from PnP JavaScript Core Component repository

See About Repository Graphs for more details on above statistics.

Next steps

• June 2016 monthly community call is on 14th of June at 8 AM PST / 5 PM CET for latest release details with demos - Download invite with detailed schedule for your time zone from http://aka.ms/OfficeDevPnPCall.
• We'll have a summer break for the releases and following master merge will happen on 5th of August 2016 and August community call is on 9th of August 2016. Community call invite will be updated late June with updated connection information. During this summer break, we won't be doing master merge (monthly release), but team continues working in GitHub and in Yammer.

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, Office 365, Microsoft - 10th of June 2016]]> https://docs.microsoft.com/archive/blogs/vesku/office-dev-pnp-web-cast-getting-started-with-sharepoint-framework Mon, 16 May 2016 13:56:53 GMT https://blogs.msdn.microsoft.com/vesku/?p=1305 [Cross posting from dev.office.com]

In this PnP Web Cast we concentrated on showing in practice how to get started with upcoming SharePoint Framework. We demonstrated the preview tooling (*) for development and how the development cycle will work with SharePoint Framework. 

Key objective of the web cast is to show you the high level development cycle and to clarify some of the terms and capabilities what has been shared by the community blog posts after SharePoint Framework announcement on 4th of May 2016.

Presentation covers following topics:

• SharePoint Extensibility Principles
• Open source tooling support
• SharePoint Workbench - What is it?
• Client-side Web Part Build Flow

Demo section concentrates on showing following topics:

• Looking on the client-side web part configuration options and end user experience
• Creating your first Client-side Web Part with preview tooling (*)
• Walkthrough of Client-side Web Part Build Flow with preview tooling (*)

* Notice. It's important to notice that we used preview tooling in this video, which is not yet available for the community to consume, when this video was released. When official tooling will be available, there might be also some changes on the exact commands and we are also looking to have Visual Studio tooling support. 

Web cast presenters: Waldek Mastykarz, Vesa Juvonen

Waldek works in Rencore AB and is one of the external members in the Office 365 Dev PnP Core team. 

Presentation used in this web cast is available from http://docs.com/OfficeDevPnP.

Video at Channel 9.

Additional resources

See following resources around the covered topics

• The SharePoint Framework - an open and connected platform
• PnP Web Cast - Getting started on the web stack in SharePoint development
• Multiple MVP blog posts

What is Office 365 Developer Patterns and Practices (PnP) web cast series?

Office 365 Developer Patterns and Practices (PnP) web cast series covers 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 in our GitHub repositories 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, SharePoint, Microsoft - 16th of May 2016]]> https://docs.microsoft.com/archive/blogs/vesku/office-365-developer-patterns-and-practices-may-2016-release Wed, 11 May 2016 12:53:15 GMT https://blogs.msdn.microsoft.com/vesku/?p=1295 [Cross posting from dev.office.com]

Office 365 Developer Patterns and Practices (PnP) May 2016 release is out with new contributions from community for the community. This post contains all the details related on what was included with the release and what else has been happening in the PnP world during the past month.

What is Office 365 Developer Patterns and Practices (PnP)?

PnP is community driven open source initiative where Microsoft and external community members are sharing their learning's around implementation practices for Office 365 in general and also 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.

This is work done by the community for the community without any actual full time team members. 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 PnP Core team and we are looking to extend the Core team with more community members.

Notice that since this is open source community program, there’s no SLAs for the support what we provide from program. There is however highly active PnP Yammer group, where you can get fast support on any questions around the existing materials. If you are interested on getting more closely involved, please check the following guidance from our GitHub wiki or a referenced PnP Web Cast.

• How to get started and contribute to Office 365 Dev PnP program? - Wiki
• Office Dev PnP Web Cast – How to get started with Office Dev PnP? - Web Cast
• Office Dev PnP Web Cast – How to contribute to Office Dev PnP initiative? - Web Cast

Some key statistics around PnP program from May 2016 release

• GitHub repository forks at different repositories 
  • PnP main repository - 1498
  • PnP Sites Core - 196
  • PnP PowerShell - 152
• Yammer group members - 4329
• Unique visitors during past 2 weeks cross PnP repositories - 9872
• Merged pull requests cross PnP repositories - 1867
• Closed issues and enhancements ideas cross PnP repositories - 570
• PnP Core component NuGet package downloads - 31184
• Unique visitors in PnP MSDN pages during April 2016 - 25217

Main resources around PnP program

• PnP under dev.office.com – https://aka.ms/OfficeDevPnP - One location for all the resources and news around PnP
• PnP GitHub - https://aka.ms/OfficeDevPnPGitHub - main repository
• PnP MSDN pages - https://aka.ms/OfficeDevPnPMSDN
• PnP Yammer group - https://aka.ms/OfficeDevPnPYammer
• PnP Videos at Channel 9 - https://aka.ms/OfficeDevPnPVideos
• PnP training package (videos in Channel 9) - https://aka.ms/OfficeDevPnPTraining
• Presentations at docs.com - http://docs.com/OfficeDevPnP
• PnP Guidance Repository – https://aka.ms/OfficeDevPnPGuidance

May 2016 monthly community call

Agenda for the Tuesday 10th of May community call at 8 AM PDT / 5 PM CET:

• Summary on the May release, community survey results and other updates in program - Vesa Juvonen ~20-25 min
• Demo on new PnP JavaScript Core component - Patrick Rodgers ~10-15 min
• Demo on MicrosoftGraph.Cordova.Mobile - Bill Ayers (Flosim) ~10-15 min
• Open discussion around the SharePoint Framework - Q&A ~10-15 min

If you have any questions, comments or feedback, please participate in our discussions in the Office 365 Patterns and Practices Yammer group at https://aka.ms/OfficeDevPnPYammer. We already have more than 4300 members in this group with lively discussions on different SharePoint and Office 365 related topics from on-premises and cloud perspective. This is the most active developer group in the Office 365 Technical network and we are definitely proud and thankful of that.

PnP Office Hours and Special Interest Group (SIGs) for JavaScript development

We started bi-weekly PnP Office Hours during February 2016 for addressing questions on how to contribute towards PnP. These are open discussions around what the Core team is doing and where the community members can assist. This time is also open for discussions around design decisions, challenges and possible issues in the PnP deliverables. You can download invite for the bi-weekly invite from following location. Recording of these Office Hours are shared in the PnP Yammer group within 24 hours after the recording was done.

• https://aka.ms/OfficeDevPnPOfficeHours

Due constantly growing interest on the PnP program, we also are piloting Special Interest Groups (PnP SIGs), which are more targeted on specific topic, like SharePoint Client Side (JavaScript) development or other areas. We are currently piloting this model with SIG for Client Side development, which have had great interest. Client Side Development SIG is creating its own JavaScript Core component using normal web stack tooling, which aligns on the recently announced upcoming SharePoint Framework. Weekly calls are around 50%-50% on the JS Core component development and discussions around the SharePoint Framework.

• Yammer group – https://aka.ms/OfficeDevPnPYammerSPClient
• Invite to weekly call - https://aka.ms/OfficeDevPnPSPClientSIGCall

You can find more around PnP Office Hours and Special Interest Groups (SIGs) from following blog post or check the web cast around the JavaScript SIG for the specific details.

• Introducing Office Dev Patterns and Practices Office Hours and Interest Groups
• Office Dev PnP Web Cast – Introducing PnP JavaScript Special Interest Group

PnP Weekly Web Casts

We started new PnP Weekly Web Cast with video series with new video on each Monday around key topics around the guidance or around hot topics from the community. Videos will be released to the PnP Channel 9 section. Here's list of videos released since last monthly communications.

• 11th of April - Introducing PnP JavaScript Special Interest Group
• 18th of April - SharePoint Client Side Object model versioning for your customizations
• 25th of April - JavaScript and Microsoft Graph (Quick Contact Sample)
• 2nd of May - Managing your app principals in Office 365 - tooling and scripts
• 9th of May - Getting started with the web stack in SharePoint development

PnP repositories in GitHub

There are quite a few different GitHub repositories under the PnP brand since we wanted to ensure that you can easily find and reuse what's relevant for you. We do also combine multiple solutions to one repository, so that you can more easily sync and get latest changes of our released guidance and samples. In general we do recommend you to use the PnP sample search tool at dev.office.com for locating relevant material for you. This should be easier and faster than trying to locate relevant material from GitHub.

Here's the current repository structure, including short description for each of them.

• PnP - Main repository for SP add-in, Microsoft Graph etc. samples
• PnP-Guidance - Guidance, presentations and articles which are partly sync'd to MSDN
• PnP-Sites-Core - Office Dev PnP Core component
• PnP-JS-Core - Office Dev PnP Core component for JavaScript
• PnP-PowerShell - Office Dev PnP PowerShell Cmdlets
• PnP-Tools - New repository for tools and scripts targeted more for IT Pro's and for on-premises for SP2013 and SP2016
• PnP-Office-Addins - Office Add-in samples and models (starting)
• PnP-Partner-Pack - Packaged guidance with detailed instructions on setting things up in Office 365 and in Azure.
• PnP-Transformation - Material specifically for the transformation process. Currently includes samples around InfoPath replacement and transformation tooling from farm solutions to add-in model.
• PnP-OfficeAddins - Samples for the Office Add-ins development
• PnP-Provisioning-Schema - PnP Provisioning engine schema repository

Note. We are looking again to do some level of refactoring of the PnP repositories due the upcoming model for the new SharePoint Framework. We'll come back on this slightly later when things are fully locked.

What's supportability story around PnP material?

Following statements apply cross all of the PnP samples and solutions, including samples, core component(s) and solutions, like PnP Partner Pack.

• PnP guidance and samples are created by Microsoft & by the Community
• PnP guidance and samples are maintained by Microsoft & community
• PnP uses supported and recommended techniques
• PnP implementations are reviewed and approved by Microsoft engineering
• PnP is open source initiative by the community – people who work on the initiate for the benefit of others, have their normal day job as well
• PnP is NOT a product and therefore it’s not supported through Premier Support or other official support channels
• PnP is supported in similar ways as other open source projects done by Microsoft with support from the community by the community
• There are numerous partners that utilize PnP within their solutions for customers. Support for this is provided by the Partner. When PnP material is used in deployments, we recommend to be clear with your customer / deployment owner on the support model

Latest changes

Provisioning Engine

The first version of the PnP remote provisioning engine was released with the May 2015 release. For the May 2016 release we have continued to add new supported capabilities and made significant improvements from stability perspective for both Office 365 and on-premises. This list contains the main updates that have been added in the May release:

• General overall quality and performance improvements
• Updated base templates for the SPO, 2013 and 2016 - used in delta handling

We are planning to release new schema version and some new capabilities as part of the June 2016 release. This new version will contain few missing pieces from the current design, which will be also addressed gradually in the PnP provisioning engine.

PnP Core Component Nuget - renaming

As part of the May 2016 release, we are also releasing native support for SharePoint 2016 with the PnP Core Component. As part of this release, we have also updated the Nuget package naming and would suggest you to take advantage of the updated packages in your solutions.

Here's the new names for the Nuget packages based on your target environment

• SharePoint 2013 - SharePointPnPCore2013
• SharePoint 2016 - SharePointPnPCore2016
• SharePoint Online / Office 365 - SharePointPnPCoreOnline

Notice. We have also updated old Nuget packages with the latest version and keep on doing this also during June 2016 release, but will deprecated them after that. We suggest that you'd use the new Nuget packages in your solution. Please make sure also that you use the right Nuget package based on your target environment. Regardless of multiple target environments, you can still use one code base for all of them, if needed. This model is explained in recent PnP Web Cast called SharePoint Client Side Object model versioning for your customizations.

PnP library

We have done general cleaning in the repository related on Nuget package updates and also removed some samples, which are no longer relevant. We are planning to continue these cleaning activities during the next months as well to streamline the repository and to combine some samples for reducing the overall number of similar samples.

There's also significant amount of general updates on the existing samples done by the community on the code and documentation, which is great way to contribute as well.

• PnP Core: Lots of re-factoring done to improve code quality and completeness:
  • provisioning engine updates (see above)
  • Native SP2016 support included - notice new Nuget packages
  • General bug fixing, performance and quality improvements
  • Automated documentation updated to md file
  • Removal of deprecated methods
  • Build and test automation improvements with unit test changes
  • Three new PnP Core Nuget packages (cloud and on-premises) have been released and old ones have been updated for easier transition.
• New solution Provisioning.VSTools, which demonstrates using the PnP provisioning engine within a Visual Studio extension package to assist with common deployment tasks for SharePoint assets. The VSTools extension package maintains the PnP provisioning engine XML file automatically as files are added or removed from the project instead of the developer having to fill out the file manually which usually results in missing items, misspelled items, etc.
• Updated Core.TaxonomyPicker component with better multi-lingual support.
• Updated Provisioning.UX.App provisioning solution with small updates
• Updated PnP-PowerShell Commands with new CommandLets and with few fixes - Updated latest on 10th of May to use the new Core Nugets
  • Overall quality improvements and bug fixes
  • New Invoke-SPOWebAction Cmdlet which lets to iterate sites, lists and list items and execute provided delegated methods on the target.
  • Updated documentation for CmdLets
• Initial version of PnP-JS-Core JavaScript library which is released also as a NPM package. PnP JS Core library is targeted to increase your productivity around JavaScript driven development in SharePoint.
• Updates to the PnP Partner Pack
  • Updated to use the latest Nuget package for SharePoint Online

PnP Guidance articles

The PnP Guidance repository contains guidance articles which are mostly being published at MSDN. Starting from end of May this process will be fully automated and there's automatic contributors list in the MSDN side showing who have been providing updates to these documents. We will be releasing significant amount of new material by end of May as part of introducing the new synchronization process around PnP MSDN pages.

See MSDN articles from the PnP MSDN section at https://aka.ms/OfficeDevPnPMSDN.

PnP Guidance videos

We did not release any new guidance videos during this month on top of the new web cast videos mentioned already above in this blog post. You can find all PnP videos from our Channel 9 section at https://aka.ms/OfficeDevPnPVideos. This location contains already significant amount of detailed training material, demo videos and community call recordings.

Key contributors for the May 2016 release

Here’s the list of active contributors (in alphabetical order) during past month in PnP repositories. PnP is really about building tooling together with the community for the community, so your contributions are highly valued cross the Office 365 customers, partners and obviously also at Microsoft.

Thank you for your assistance and contributions from the behalf of the community. You are making a difference!

• Arjan Cornelissen (Sogeti) - @arjancornelis
• Arto Kaitosaari (Affecto Oy) - @artokai
• Daniel Laskewitz (Sogeti) - @laskewitz
• Bill Ayers (Flow Simulation Ltd.) - @SPDoctor
• Bryon Chan - bryonchan
• Camille Mercado (Perficient, Inc.)
• Derek Smith - derek-smith
• Erwin van Hunen (Rencore) - @erwinvanhunen
• Ivan Vagunin (KnowIt) - @ivagunin
• Jerry Fetzer (Perficient) - jcfetzer
• Kristian Nagel - thenail
• Lane Goolsby (ThreeWill) - @lanegoolsby
• Lars Fernhomberg - lafe
• Luis Mañez (ClearPeople) - @luismanez
• Marc D Anderson (Sympraxis Consulting LLC) - @sympmarc
• Massimo Prota (Rapid Circle) - @massimoprota
• Matt Carter (BlueSky Sharepoint Consulting) - m-carter1
• Martin Segelfeldt (Knowit AB) - Segelfeldt
• Michael Toole (Perficient, Inc.) - miket9884
• Mårten af Sandeberg (Knowit AB) - afsandeberg
• Ole Martin Pettersen (Puzzlepart AS) - @olemartinit
• Paolo Pialorsi (PiaSys.com) - @PaoloPia
• Patrik Björklund (Cognit Consulting AB) - @pbjorklund
• Pieter Veenstra (Bluesource) - @PieterVeenstra
• Radi Atanassov (OneBit Software) - @RadiAtanassov
• Rajesh Sitaraman (SADA Systems) - @rjesh
• Russell Gove - russgove
• Stefan Bauer (n8d.at) - @StfBauer
• Tatjana Starovoitva (Perficient, Inc.)
• Thomas Berman (Advance) - thomasberman
• Tobias West (SCC) - tobiaswest83
• Waldek Mastykarz (Rencore) - @waldekm
• Warren Roscoe -warrenroscoe
• Will Don - nerdondon

Companies: Here's the companies, which provided support for PnP initiative for this month by allowing their employees working for the benefit of others in the PnP initiative. There were also people who contributed from other companies during last month, but we did not get their logos and approval to show them on time for this communications. If you still want your logo for this month's release, please let us know and share the logo with us. Thx.

Microsoft people: Here’s the list of Microsoft people who have been closely involved on the PnP work during last month.

• Alex Randall (Microsoft) - @alex_randall_
• Antons Mislevics (Microsoft) - GitHub
• Bert Jansen (Microsoft) - @O365Bert
• Brian Michely (Microsoft) - @brianmichely
• Dan Budimir (Microsoft) - MSDN blog
• David Rei (Microsoft) - MSDN blog
• Frank Marasco (Microsoft) - @frank_marasco
• Kiki Shuxteau (Microsoft)
• Laura Graham (Microsoft) - Lauragra
• Neil Hodgkinson (Microsoft) - GitHub
• Patrick Rodgers (Microsoft) - GitHub
• Roy Harper (Microsoft) - roharp
• Vesa Juvonen (Microsoft) - @vesajuvonen

Latest statistics

Here's some statistics from the PnP, PnP PowerShell and PnP Sites Core (core component) repository. Traffic information is dependent on the time of the day it's collected, so final day is quite low right now, due morning schedule.

Contributions at PnP repository

Traffic at PnP repository

Contributions at PnP Sites Core repository

Traffic from PnP Sites Core repository

Contributions at PnP PowerShell repository

Traffic from PnP PowerShell repository

See About Repository Graphs for more details on above statistics.

Next steps

• May 2016 monthly community call is on 10th of May at 8 AM PDT / 5 PM CET for latest release details with demos - Download invite with detailed schedule for your time zone from https://aka.ms/OfficeDevPnPCall.
• Following master merge will happen on 3rd of June 2016 and June community call is on 14th of June 2016

“Sharing is caring”

Vesa Juvonen, Senior Program Manager, Office 365, Microsoft - 9th of May 2016]]>