SharePoint / Office 365 Dev Patterns and Practices (PnP) December 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.
Today’s post was written by Bill Baer, senior product manager for the #SharePoint team. When we launched SharePoint Server 2016, we shared our vision that it would be a foundational release, born in the cloud and built for continuous innovation. Today, we’re pleased to announce our next step on this journey with the availability of Feature Pack 1. Through the November 2016 Public Update for SharePoint Server 2016, we’re delivering several new features based on customer feedback, extending support for hybrid scenarios and developer needs, including:
- Administrative actions logging for common SharePoint administrative actions.
- MinRole enhancements to support small and medium-sized farms.
- A OneDrive for Business modern experience.
- Custom tiles in the SharePoint app launcher.
- SharePoint hybrid auditing unified across site collections on-premises and in #Office 365.
- Hybrid taxonomy unified
In August 2016, we announced that Office 365 Groups would get full-powered SharePoint team sites. When you create a group, #Office 365 gives the group a shared inbox, calendar, OneNote notebook, place for files, Planner for task management—and now a modern team site with pages, lists, libraries and team news, so the group can collaborate, communicate and coordinate. This is now 100 percent rolled out to all #Office 365 First Release customers, as noted by the @SharePoint team. Starting today, people will be able to create #SharePoint team sites connected to Office 365 Groups from the SharePoint home in Office 365—and it’s fast. Admins control how these new capabilities appear for their users. And it is more intuitive to adjust the site as business needs require. Now, no matter where users create an Office 365 group (from Outlook, #Microsoft
At #Microsoft Ignite 2016, in Atlanta, we proudly announced the availability of the new “#PnP #Templates Gallery” portal, which is available at the following URL: https://templates-gallery.sharepointpnp.com. The basic idea around this new portal, is to have a public and shared repository for PnP provisioning templates, which anybody can download and use for free. Moreover, we hope that many community members will like to share their own templates with the community. In the following figure, you can see the home page of the PnP Templates Gallery. The site is responsive and mobile-aware, and allows you to browse the templates, and to search for them based on few search criteria:
We are happy to announce availability of new #SharePoint Client Side Object Model (#CSOM) version targeted for the #Office 365 or more specifically for SharePoint and Project Online. This release again contains few updates on the existing SharePoint CSOM assemblies and some maintenance changes. These monthly changes are not significant, but we want to align on the monthly rythm in future, so that you can know beforehand that there will be new version arriving during end of each month. You can find the latest CSOM package for #SharePoint Online, including the Project Online CSOM assembly, from the NuGet gallery with an id of '#Microsoft.SharePointOnline.CSOM'. We are also working on updating the redistributable package at some point, but you can already right now start using some of these new capabilities in your solutions. We do recommend you to use the Nuget Package to gain
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
- How to reference external libraries in client-side web parts
- Considerations and options when external libraries are being referenced
- How to reference external library to your client-side web part
- Needed configuration for