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.
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
- Updates to the PnP Partner Pack
- Updated to use the latest Nuget package for SharePoint Online