Quantcast
Channel: Blog
Viewing all 429 articles
Browse latest View live

SharePoint PnP Webcast – Introduction to PnP Templates Gallery

$
0
0

In this PnP Webcast we concentrated on covering SharePoint Patterns and Practices (PnP) Templates Gallery, which is an open source remote provisioning template gallery for PnP provisionign templates. PnP Templages Gallery can be used to consume and share PnP provisioning templates with SharePoint on-premises and SharePoint Online. You can use the PnP provisionign templates available from the Gallery site in your deployments using either managed code or by using PnP PowerShell Cmdlets. These templates are using so called remote provisioning pattern, which also means that they are future proven model without feature framework usage, like classic site templates or site definitions. 

You can create PnP provisioning templates simply by designing your SharePoint site using a browser and then export this site as a reusable template using managed code or with PnP PowerShell cmdlets. When template is extracted, it can be then used to apply configurations or customizations on existing SharePoint sites. We released the gallery only with few templates, but are looking forward on the contributions from the community side, so that we can grow the available templates for others to use as well.

Presentation covers following topics:

  • What is PnP Templates Gallery?
  • How to use templages from the gallery?
  • How to submit your templates?

Web cast demo shows following details

  • Walkthrough of the PnP Templates Gallery UI for finding what's relevant for you
  • How to download and use templates from the gallery - step-by-step actions
  • How to use PnP PowerShell CmdLets for template manipulation?
  • How to submit your templates to PnP Templates Gallery?

Webcast presenters: Paolo PialorsiVesa Juvonen

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

Video at YouTube.

Additional resources

See following resources around PnP Provisioning Engine, PnP PowerShell and PnP Templages Gallery. 

What is SharePoint / Office DevPatterns & Practices (PnP) web cast series?

SharePoint / Office Dev Patterns and PracticesSharePoint / Office Dev Patterns & Practices (PnP) webcast 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 minute long web cast each Monday with few slides and a live demo on the covered topic. All web casts are published at the PnP YouTube channel 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 http://aka.ms/SPPnP-Call.

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 Microsoft Tech Community (SharePoint Developer group).

“Sharing is caring”


Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 10th of October 2016


SharePoint / Office Dev Patterns & Practices – October 2016 release

$
0
0

SharePoint / Office 365 Dev Patterns and Practices (PnP) October 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)?

SharePoint / Office Dev Patterns and Practices 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.

Some key statistics around PnP program from October 2016 release

Main resources around PnP program

October 2016 monthly community call

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

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.

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.

Notice. Next SIG for PnP Component / PowerShell will be on Wednesday 19th of October - 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.

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.

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.

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.

 

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 October 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 October 2016 release:

  • General overall quality and performance improvements for on-premises and online
  • Allow to apply and extract groups to subwebs
  • Fixes on RoleAssignments and RoleDefinition Provisioning
  • 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 JavaScript Core library v1.0

PnP JavaScript Core Library has moved to version 1.0.5. 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.5 is coming out early October with following capabilities.

  • Exporting Types from within the library to make it easy to use them directly and better support webpack and similar bundlers
  • Various fixes
  • Various enhancements
  • Removed many selectable properties to shrink the library (saved 11K minimized) - use select to access those properties
  • Documentation updates to clearly describe how to contribute to or use the library
    • Includes updates in readme.md
  • Moved to TypeScript 2.0 and the new @types system to ease installation for both developer and consumer of library

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)
    • Implemented native CSOM webpart export for SPO
    • Improved support for site and site collection around enabling responsive UI capabilities - support to be set at site or site collection level
    • 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 (cloud and on-premises) updated with new version
  • New sample WebHooks.Nodejs as Node.js webhook application for Sharepoint. This application allows you to manage all subscriptions for a specific list or library and shows you the webhook changes when they happen.
  • New sample jquery-cdn illustrating using jQuery and its plugins loaded from CDN for building SharePoint Framework Client-Side Web Parts.
  • New sample jquery-photopile illustrating using JQuery and Photopile.Js with the SharePoint Framework
  • New sample js-powerbi-embedded illustrating SharePoint Framework Client-Side Web Part embedding a PowerBI report using PowerBI Embedded without any server-side code.
  • New sample react-aad-implicitflow illustrating SharePoint Framework web parts built using React illustrating different scenarios using implicit OAuth flow with Azure Active Directory.
  • New sample react-organisationchart illustrating simple Organisation Chart webpart using Office UI Fabric, React, OData batching and ServiceScope plumbing.
  • New sample react-search illustrating Search Web Part with internal and external template support. This sample illustrates how you can use React and Flux within the SharePoint Framework.
  • New sample sharepoint-crud Web Parts illustrating performing SharePoint CRUD operations in React, Angular, JavaScript without any framework and using the SP PnP JS library.
  • New Script SharePoint.Hybrid.CloudSSA.Configuration designed for configuring a SharePoint Server farm with a hybrid Cloud Search Service Application
  • Updated 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 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
    • Load-SPOProvisioningTemplate and Save-SPOProvisioningTemplate for loading PnP template from pnp file for in-memory manipulation in PowerShell
    • Add/Remove-SPOFileTo/FromProvisioningTemplate Cmdlets for adding files to pnp templates
    • Remove-SPOTermGroup for removing term groups from taxonomy store
    • Remove-SPOTaxonomyItem for removing terms from taxonomy store
    • Added support for unit testing of the Cmdlets
    • Updated documentation for CmdLets
  • 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

Here's new guidance articles since the last release communications

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:

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!

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.

 
 ClearPeople
 IOZ
 Digital Illustrated
 piasys
 onebit software
 rencore
 Triad


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

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

Stats on PnP repository

Traffic from PnP Sites Core repository

Stats on PnP Core repository

Traffic from PnP PowerShell repository

Stats on PnP PowerShell repository

Traffic from PnP JavaScript Core Component repository

Stats on PnP JS Core repository

See About Repository Graphs for more details on above statistics.

Next steps

  • September 2016 monthly community call is on 11th of October 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 - 10th of October 2016

SharePoint PnP Webcast – Azure AD implicit flow with SPFx client-side web part (developer preview)

$
0
0

In this PnP Webcast we concentrated on covering current status around connecting Azure AD secured assets from SharePoint Framework (SPFx) client-side web parts. During SPFx developer preview, there are additional considerations around the connectivity, which we are looking to resolve during future dev releases. Use case for the demo is to have a web part, which connects to Microsoft Graph for showing upcoming appointments for the particular user. 

> Notice. Key objective of this webcast is to show how to perform authorization against Azure AD from client-side web parts during developer preview, so that you can concentrate on your business logic. SharePoint engineering is working on providing more seamless experience from connectivity perspective, which will help on accessing AAD secured data in your organization. 

Presentation covers following topics:

  • Azure AD implicit flow considerations with SP Fx
    • Authorization challenges with AAD
    • Not optimal experience during development preview
    • Challenges with IE 10
  • We are working on better story around the integration and looking to have it available by GA of client-side web parts

Web cast demo shows following details

  • Walkthrough of "upcoming appointments" sample
  • Signing in to Azure AD from client-side web part
  • Adal.js library usage in the client-side web part usage
  • AD Authorization and Microsoft Graph integration flow in the sample web part

Webcast presenters: Waldek MastykarzVesa Juvonen

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

Video at YouTube.

Additional resources

See following resources around the SharePoint Framework. 

What is SharePoint / Office DevPatterns & Practices (PnP) web cast series?

SharePoint / Office Dev Patterns and PracticesSharePoint / Office Dev Patterns & Practices (PnP) webcast 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 minute long web cast each Monday with few slides and a live demo on the covered topic. All web casts are published at the PnP YouTube channel 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 http://aka.ms/SPPnP-Call.

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 Microsoft Tech Community (SharePoint Developer group).

“Sharing is caring”


Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 17th of October 2016

SharePoint CSOM versions for on-premises released as NuGet packages

$
0
0

We are happy to announce availability of SharePoint Client Side Object Model (CSOM) assemblies as NuGet packages for SharePoint 2013 and SharePoint 2016. Previously we have shipped CSOM only as seperate installer packages (msi's), but wanted to ensure that you can use exactly the same assemblies also using NuGet packages. You can find these packages from the NuGet gallery with specific id's for SharePoint 2013 and 2016 versions.

These packages contain exactly the same versions of the assemblies as the msi packages to avoid version conflicts. We are also committed to update these NuGet packages in the same time as any updates for the msi packages. This means that it does not really matter which option you want to use in our deployments. Key advantage of having these assemblies as NuGet packages is to have possibility to reference them as NuGet in your Visual Studio solutions without any external dependencies. Versions of the CSOM assemblies are as follows, which also aligns with the previously released msi packages.

  • SharePoint 2013 CSOM - April 2015 CU
  • SharePoint 2016 CSOM - SP2016 RTM version

We would be looking for your feedback and input around these packages, so that they are valuable for you. Right now, NuGet packages only contain .NET 4.5 version of the assemblies for simplicity perspective, but please let us know if this is not optimal for you by using the comments in this blog post or by using Microsoft Tech Community (SharePoint Developer Group). Since CSOM assemblies have dependency on the server side version, we are not looking to update these NuGet packages frequently, rather only when there's a major release and we would need to reset a CSOM baseline for the on-premise deployments.

Screenshots from NuGet gallery with SP2013 and SP2016 packages shown in results

Notice that since each CSOM version is targeted for specific environment and you might run into issues, if you use wrong CSOM version for your target environment. This is because of the server side dependencies of the APIs. CSOM versioning model and dependency to your target environment is clarified in following blog post - Using correct Client Side Object Model (CSOM) version for SharePoint customizations

If you are targeting SharePoint Online as your platform, you should be using specific NuGet package for that with an id of 'Microsoft.SharePointOnline.CSOM'. You can read more details on latest capabilities for the SharePoint Online from the SharePoint Online CSOM September 2016 release notes (latest monthly release).

“Sharing is caring”


Vesa Juvonen, Senior Program Manager, OneDrive-SharePoint Engineering, Microsoft - 19th of October 2016

SharePoint PnP Webcast – PnP Core and PowerShell Test automation

$
0
0

In this PnP Webcast, we concentrated on showing how we perform integration / scenario testing for the PnP Core Component and PnP PowerShell solutions. These both are widely used by customers and partners in their day-to-day work, so we are looking to ensure as high quality functionalities as possible with automated daily tests. PnP automated test results are available for review at http://aka.ms/sppnp-test, which is a site where you can drill into details on each specific test case cross different target environments (SharePoint 2013, 2016 or online). 

> Notice. You can use this webcast also as an inspiration for test automation for your environment. All test assets and used automation is available from PnP repositories for you to reuse. 

Presentation covers following topics:

  • Integration / functional testing of PnP Core and PowerShell
  • How PnP initiative performs testing cross different environments
  • How different validation circles work in SharePoint Online
  • Test engine architecture
  • Planned improvements for the test automation

Web cast demo (17:03) shows following details

  • Demonstration of testautomation.sharepointpnp.com web site for the test results
    • Different types of tests
    • Reporting of different environments and test results
    • Drilling into test report details
  • How to subscribe daily test summary on test results

Webcast presenters: Bert JansenVesa Juvonen

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

Video at YouTube.

Additional resources

See following resources around the covered topics 

What is SharePoint / Office DevPatterns & Practices (PnP) web cast series?

SharePoint / Office Dev Patterns and PracticesSharePoint / Office Dev Patterns & Practices (PnP) webcast 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 minute long web cast each Monday with few slides and a live demo on the covered topic. All web casts are published at the PnP YouTube channel 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 http://aka.ms/SPPnP-Call.

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 Microsoft Tech Community (SharePoint Developer group).

“Sharing is caring”


Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 24th of October 2016

Use commands to make your add-ins available in the Office ribbon

$
0
0

In March 2016, we released add-in commands for Word, Excel, and PowerPoint for Office desktop and Office Online. Add-in commands were made available in Outlook in November 2015  . Commands enable you to extend the Office UI across multiple platforms. We have seen that users are more likely to continue to use add-ins that have command entry points in the Office ribbon, so using add-in commands can increase the retention rate for your add-ins.    

In this post, we highlight some of the important benefits that commands introduce, as well changes we are making to Office Store policies to require the use of commands in Word, Excel, and PowerPoint add-ins. We are also announcing the deprecation of the custom pane extension point in Outlook add-ins. 

Benefit: Integration with the Office UI

Add-in commands allow you to extend the Office UI to add custom buttons to the Office ribbon. You can extend existing tabs, create your own custom tab, or extend contextual menus. To see add-in commands in action, watch the Add-in commands in the Office ribbon video.

The following are some examples of add-ins that use commands.

Figure 1. Boomerang  add-in extending the Message tab in Outlook

Figure 2. Pickit add-in command in the Office ribbon

Figure 3. XLSTAT add-in custom tab

Benefit: Increased discoverability and retention

Users expect to be able to find all the tools and actions that they need on the Office ribbon. When you adopt commands, you make it easier for users to access and use your add-in. By using commands, you can:

  • Make your add-in more discoverable by placing add-in buttons with relevant user flows.
  • Make your add-in more efficient to use by making specific actions accessible on the ribbon.
  • Provide a familiar experience for users, and increase user retention, by extending the Office suite. Users will be more likely to come back to use your add-in again.

To give you an example of the positive impact that we’ve seen so far, several Outlook add-ins had doubled retention rates after they were updated to use commands.   We are seeing a similar positive impact across add-ins for other applications.

Benefit: Teaching UI

The teaching UI feature is currently rolling out and will be fully deployed in a couple of weeks. You can use teaching UI to show users where an add-in is installed and how to get started using an add-in when they install it from the Office Store. The following is an example of an add-in that uses teaching UI.

Benefit: Support across multiple platforms

Add-in commands for Outlook are already supported for Outlook 2013 and Outlook 2016 desktop, and will be supported in Outlook for Mac and Office Online within the next two months. Add-in commands for Word, Excel, and PowerPoint are currently supported   in Word, Excel, and PowerPoint in Office 2016 desktop clients and Office Online, and will soon be supported in Office for Mac. For the latest support information for this and other features, see Office Add-in host and platform availability.  

Does that mean that you need to wait until commands are supported everywhere to use them in your add-in? Not at all. Today you can create an add-in, with a single manifest and a single submission to the Office Store (if you are distributing via the Store), that targets all the Office platforms that support Office Add-ins. Clients that do not support commands, such as Office 2013, will run your add-in as a task pane.

Benefit: Creating commands is easy

It only takes a few minutes to add commands to your add-in.

If you are creating a new add-in, you can start from one of our existing samples. If you are a Visual Studio developer, you can use the Office Developer Tools. The Office Web Add-in templates include a sample command.

If you have an existing Outlook or task pane   add-in, add a VersionOverrides node to your manifest. You can start by adding a button to launch your task pane. You can also go a step further and re-envision your add-in to take advantage of ribbon integration. For more information, see best practices for using add-in commands.

If you run into issues, see our FAQs for help with troubleshooting. You can also post questions to StackOverflow and tag with [office-js].  

Requirement: New Office store policies and deprecated features

Word, Excel, and PowerPoint add-ins

Effective February 1, 2017, Word, Excel, and PowerPoint add-ins that use the taskpane manifestmust use add-in commands in order to pass Office Store validation. This policy will apply to both new submissions and updates to existing Office Store add-ins.

If you need to request an exception to this requirement, indicate the reason for the exception in the testing notes field when you submit your add-in.

Outlook add-ins

Add-in commands are already required for all Outlook add-ins in the Office Store. We are also announcing that custom panes in Outlook will no longer be supported as of February 1, 2017. This applies across all platforms.

Add-in commands provide a significant advantage in terms of user engagement and discoverability over the legacy custom pane experience (shown in the following image).

Effective November 7, 2016, Outlook add-ins submitted to the Office Store must not declare the CustomPane extension point in the VersionOverrides node . This applies to both new submissions and updates to existing Office Store add-ins. This means less work for you as a developer because you don’t have to include an unnecessary extension point if you already have commands.

Call to action

We encourage you to adopt commands in your add-in as soon as possible. You will see higher adoption and retention rates and more satisfied users. The following are the effective dates for the Office Store requirements :

  • New and updated Word, Excel, and PowerPoint add-ins using the taskpane manifest must use commands to pass Office Store validation effective February 1, 2017.
  • Outlook add-ins that do not support commands will be removed from the Office Store effective February 1, 2017.
  • New and updated Outlook add-ins in the Office Store must not include the CustomPane extension point in the VersionOverrides node effective November 7, 2016.

New SharePoint CSOM version released for SharePoint Online - October 2016

$
0
0

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 access on latest version, rather than downloading the SDK to your machine.

Version of the newly released CSOM package is 16.1.5813.1200. Previous versions of the NuGet has not been removed, so that your existing solutions will continue working without issues and you can decide when the new version is taken into use. Notice that even though the Nuget version is increased to 16.1.5813.1200, actual assembly version of the released assemblies is 16.1.0.0. You can also check the version of the assemblies from the File Version attribute, which aligns with the Nuget version.

Screenshot of the NuGet package manager in the Visual Studio 2015 with Micorosft.SharePointOnline.CSOM package shown

Notice that since this NuGet package is targeted to SharePoint Online, you cannot use it directly in on-premises environments (SharePoint 2013 or 2016). This is because of the server side dependencies of the APIs. CSOM versioning model and dependency to your target environment is clarified in following blog post - Using correct Client Side Object Model (CSOM) version for SharePoint customizations. We have released separate NuGet packages for on-premises. See following blog post for additional details - SharePoint CSOM versions for on-premises released as NuGet packages.

New properties and methods cross assemblies

Here's a raw list of all the changes in the classes, properties and methods within this package. 

Microsoft.SharePoint.Client

  • public property Microsoft.SharePoint.Client.Attachment.FileNameAsPath
  • public property Microsoft.SharePoint.Client.Attachment.ServerRelativePath
  • public method Microsoft.SharePoint.Client.AttachmentCollection.AddUsingPath
  • public method Microsoft.SharePoint.Client.AttachmentCollection.GetByFileNameAsPath
  • public class Microsoft.SharePoint.Client.AttachmentCreationInformationUsingPath
  • public property Microsoft.SharePoint.Client.ChangeItem.FileSystemObjectType
  • public property Microsoft.SharePoint.Client.ChangeItem.FileType
  • public property Microsoft.SharePoint.Client.RemoteWeb.Web
  • public property Microsoft.SharePoint.Client.SharingLinkInfo.Expiration
  • public method Microsoft.SharePoint.Client.Site.CreateCopyJobs
  • public method Microsoft.SharePoint.Client.Site.GetWebPath
  • public method Microsoft.SharePoint.Client.Web.GetListItemUsingPath
  • public method Microsoft.SharePoint.Client.Web.GetListUsingPath
  • public property Microsoft.SharePoint.Client.WebParts.WebPart.ExportMode
  • public enum Microsoft.SharePoint.Client.WebParts.WebPartExportMode
  • public class Microsoft.SharePoint.TenantCdn.TenantCdnUrl

Microsoft.Online.SharePoint.Client.Tenant

  • public enum Microsoft.Online.SharePoint.TenantAdministration.SPOTenantCdnOriginScope
  • public enum Microsoft.Online.SharePoint.TenantAdministration.SPOTenantCdnType
  • public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.AddTenantCdnOrigin
  • public property Microsoft.Online.SharePoint.TenantAdministration.Tenant.DisableReportProblemDialog
  • public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.GetTenantCdnAllowedFileTypes
  • public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.GetTenantCdnEnabled
  • public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.GetTenantCdnOrigins
  • public property Microsoft.Online.SharePoint.TenantAdministration.Tenant.NotificationsInOneDriveForBusinessEnabled
  • public property Microsoft.Online.SharePoint.TenantAdministration.Tenant.NotificationsInSharePointEnabled
  • public property Microsoft.Online.SharePoint.TenantAdministration.Tenant.ODBAccessRequests
  • public property Microsoft.Online.SharePoint.TenantAdministration.Tenant.PermissiveBrowserFileHandlingOverride
  • public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.RemoveTenantCdnOrigin
  • public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.SetTenantCdnAllowedFileTypes
  • public method Microsoft.Online.SharePoint.TenantAdministration.Tenant.SetTenantCdnEnabled
  • public property Microsoft.Online.SharePoint.TenantManagement.Office365Tenant.NotificationsInOneDriveForBusinessEnabled
  • public property Microsoft.Online.SharePoint.TenantManagement.Office365Tenant.NotificationsInSharePointEnabled
  • public property Microsoft.Online.SharePoint.TenantManagement.Office365Tenant.ODBAccessRequests

Microsoft.ProjectServer.Client

  • public enum Microsoft.ProjectServer.Client.QueueMsgType

 

“Sharing is caring”


Vesa Juvonen, Senior Program Manager, OneDrive-SharePoint Engineering, Microsoft - 28th of October 2016

People API replaces preview API for working with

$
0
0

We have started taking steps to replace the existing preview WorkingWith API (https://graph.microsoft.com/beta/me/WorkingWith) by the new People API.

We recommend that customers and partners transition their solutions to the preview version of the People API (https://graph.microsoft.com/beta/me/people).

 

What is the People API?

The People API aggregates information about a person from across mail, contacts and social networks. People can be local contacts, contacts from social networking, your organization's directory, and people from recent communications (such as email and Skype).

Read more here: https://graph.microsoft.io/en-us/docs/api-reference/beta/resources/person

 

Browse for the people who matter most to you

The People API dynamically ranks people based on their relevance to the logged-in user. A person 10 hops away in the organization may be highly relevant.

https://graph.microsoft.com/beta/me/people?$top=1000&$select=displayName,companyName

 

Browse for people related to people

Who does your manager work with? Security and privacy are always preserved.

https://graph.microsoft.com/beta/users/alexsi@contoso.com/people

 

Search for people

Search results ranked on relevancy. The People API supports fuzzy matching for misspelled names and phonetic search. Topics can augment search query to get more relevant results.

https://graph.microsoft.com/beta//me/people?$search="Jonh"

 

Why is the WorkingWith API superseded by the People API?

The People API currently has  more complete and richer AD metadata from users compared with the small subset available in the WorkingWith API, aggregates contacts and directory users and support search. 

There is also a relevant ranking in the results for the new API, meaning that the most relevant people for the target user will be ranked on the top. This ranking is built by using the user's communication, collaboration, and business relationships.

 

The WorkingWith preview API, and all the related documentation, will be removed from the MS Graph before the end of the 2016.


SharePoint PnP Webcast – Building a sample search web part with SharePoint Framework using React

$
0
0

In this PnP Webcast, we concentrated on covering sample web part with search capability. This sample is available for you from SharePoint GitHub organization in the sp-dev-fx-webparts repository. Sample search web part is built using React and implements Flux pattern for the cross-component communications in React. It also demonstrates multiple other valuable capabilities which you could take into use in your own customizations.

Notice. When this webcast was released, SharePoint Framework was available as a Developer Preview release.  

Presentation covers following topics:

  • Different UIs in the provided sample for showing search results
  • Configuration options for the client-side web part
  • Patterns and technologies used with the web part
  • Basic flow of flux and how it works

Web cast demo (6:57) shows following details

  • Demonstration of the basic capability
  • Different configuration options
  • Logging pane implementation for seeing possible configuration options with web part
  • Structure of the sample solution
  • Flux implementation in the web part
  • How external templates are loaded to web part and used optionally in result presentation

Webcast presenters: Elio StruyfVesa Juvonen

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

Video at YouTube.

Additional resources

See following resources around the SharePoint Framework. 

What is SharePoint / Office DevPatterns & Practices (PnP) web cast series?

SharePoint / Office Dev Patterns and PracticesSharePoint / Office Dev Patterns & Practices (PnP) webcast 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 minute long web cast each Monday with few slides and a live demo on the covered topic. All web casts are published at the PnP YouTube channel 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 http://aka.ms/SPPnP-Call

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 Microsoft Tech Community (SharePoint Developer group).

“Sharing is caring”


Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 31st of October 2016

Announcing the Microsoft Teams Developer Preview

$
0
0

Today we announced the preview of Microsoft Teams, the new chat-based workspace in Office 365 that brings together people, conversations, content and the tools that teams need, so they can easily collaborate to achieve more. Every team is unique, and teams today use a variety of apps and tools.  That’s why we’re excited to introduce the Microsoft Teams Developer Preview.  The Microsoft Teams platform allows you to integrate and showcase your offering on our rich collaboration canvas, whether it’s a custom app for your enterprise or a cloud-based service.

Join the many developers and partners that have already committed to building apps for the Microsoft Teams platform, including Zendesk, Asana, Intercom, Hootsuite, Polly, Meekan, and Workato.  Here’s what you can do today:

  • You can create Tabs that surface your web experience directly within Teams, so people can instantly access your service in the right context, and collaborate around its content.
  • You can write Bots that surface your experience in chat and teams can engage with your service via queries and quick actions.
  • You can send Connector notifications in channels so teams can easily get updates from your service.

Stay tuned for updates from us on new and exciting ways for your app to integrate with Microsoft Teams.

Create your own branded tabs

Tabs allow team members to access your service on a dedicated canvas within a channel.  This lets teams work directly with the tools and data you provide, in the channel’s context, and to have conversations about them.  Examples of tabs include dashboards and data visualization, documents and notes, group task management and shared design canvases: whatever the channel needs to succeed.  It's easy for you to create a tab from your existing web app.  Get started with tabs

Screenshot of tabs in Microsoft Teams

(Example tab, coming soon)

 

Build intelligent bots

Build and connect intelligent bots using the Microsoft Bot Framework, the same framework you use to build bots across Microsoft platforms including Skype and Office 365 mail.  Now you can enable information retrieval and task completion in Microsoft Teams.  Your bot can enable people to do things like give kudos to team members; create lightweight surveys; answer natural language questions about sales and customer usage data; or manage tasks and schedules. Get started with bots

Screenshot of bots in Microsoft Teams

(Example bot, coming soon)

Have an existing bot on Slack?  Message.io can port your app to Microsoft Teams. Find out more here.

 

Deliver content and updates to channels with Office 365 Connectors

Office 365 Connectors bring key content and updates from your apps and services right into channels in Microsoft Teams.  This enables teams to do things like track relevant Twitter feeds, collaborate on a coding project on GitHub, or stay on top of tasks in Dynamics 365.  Over 70 Office 365 Connectors are available today for Microsoft Teams, and the list is growing.

You can build Connectors through incoming webhooks to generate rich connector cards. Once you build the Connector, you can submit it for Microsoft Teams as well as Office 365 Groups.  Get started with Connectors.

Screenshot of connectors in Microsoft Teams

Get started today

Get started today by going to dev.office.com/microsoft-teams: you can build Tabs, Bots and Connectors and distribute them inside your organization.  And to stay up-to-date with the Microsoft Teams Developer Platform, keep an eye on this blog or sign-up here.

SharePoint PnP Webcast – Reuse your existing JavaScript libraries with SharePoint Framework

$
0
0

In this PnP Webcast, we concentrated on covering the steps on how you can reuse your existing investments on JavaScript when developing with SharePoint Framework solutions. Lot of customers and partners have developed their existing plan JavaScript libraries, which have been used with custom web parts or using script editor web part. You do not need to rebuild these to be able to take advantage of them with SharePoint Framework solutions, but there are few steps for making them usable, which are being presented in this webcast. In general, we do recommend usage of TypeScript on development time, since it provide multiple benefits, but that's not a hard requirement and you can use your existing plan JavaScript customizations as such also with SharePoint Framework. 

Notice. When this webcast was released, SharePoint Framework was available as a Developer Preview release.  

Presentation covers following topics:

  • Options for using existing JavaScript libraries in SharePoint Framework solutions
    • Reference exteranl libraries from URL
    • Include JavaScript directly to your solution
    • Reference NPM packages
  • Considerations when you use your own scripts
    • You will need to adjust your script and markup to support modular access
    • You can use plain JavaScript directly with TypeScript
    • You can reuse easily your existing investments on plain JavaScript

Web cast demo (6:40) shows following details

  • Use case - using custom library with classic script editor web part
  • How your custom JavaScript files are bundled to the JavaScript files with SharePoint Framework
  • Steps to make your custom JavaScript working with SharePoint Framework solutions
  • Considerations around adding event receivers on the html components used in SharePoint Framework solutions

Webcast presenters: Waldek MastykarzVesa Juvonen

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

Video at YouTube.

Additional resources

See following resources around the SharePoint Framework. 

What is SharePoint / Office DevPatterns & Practices (PnP) web cast series?

SharePoint / Office Dev Patterns and PracticesSharePoint / Office Dev Patterns & Practices (PnP) webcast 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 minute long web cast each Monday with few slides and a live demo on the covered topic. All web casts are published at the PnP YouTube channel 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 http://aka.ms/SPPnP-Call

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 Microsoft Tech Community (SharePoint Developer group).

“Sharing is caring”


Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 7th of November 2016

Extending the PowerBI content pack for Project Online

$
0
0

In September 2016, the Project team released the Project Online Power Bi Content Pack on GitHub.  This release enables users of Power BI Desktop to customize and expand on the capabilities of the original Microsoft Project Online Content Pack released last year for use with the Power BI service available for Office 365.

This release of the content pack includes the basic instructions needed to connect the Power BI report to your Project Online portfolio.

Tips and Tricks to expand the content pack

The content pack starts with data on risks, issues and work status for the entire portfolio of projects.  It is a small sample of how Power BI and Project Online can work together to provide powerful insights into project portfolios.  

The Project team is providing these tips & tricks to help customize this content and expand insights into different aspects of a portfolio.





Tip #1 Stay focused

After reading this blog post, resist adding all of the tables and fields from your portfolio.  Even a modest portfolio in Project Online will have a large amount of data behind it.  Bringing in everything can create long data updates and make creating useful data relationships more complex.  Stay focused on the goal of the report such as costs and resources.



Tip #2 Add and Remove Fields

This content pack is an example on how to narrow queries towards the topic being explored. There are useful fields useful for other topics that have been excluded.  Fields can be added back to the queries to expand or change the focus of the Power BI report.

Example: Exploring Costs and Cost Variations.

  • Choose ‘Edit Queries’ on the ribbon and select on the ‘Projects’ table at the left.
  • On the right side under ‘Query Settings’ select the gear icon next to ‘Removed Other Columns.’





  • Type “Cost” into the ‘Search Columns’ control.
  • Add the fields ‘ProjectActualCost’, ‘ProjectCost’ and ‘ProjectCostVariance.’ These are all standard Project fields.
  • Select ‘Close & Apply’ on the ribbon in the ‘Edit Queries’ window, then choose ‘Refresh’ on the main Power BI window’s ribbon.





Just adding in those fields allows the creation of this scatter chart looking at both work and cost variances in





Tip #3 add and remove data tables


For users wanting to look at resource allocation the base report is missing two key tables of ‘Resources’ and ‘Assignments.’  The content pack design has made it easy to bring in new Project Online data tables.

  • Choose ‘Edit Queries’
  • Select the ‘ODataUrl’ query in the left hand column.
  • Right-click on the on the word ‘Table’ next to “Resources” and choose ‘Add as New Query’  
  • Do the same for ‘Assignments’







Also as in Tip #2, edit the ‘AssigmentBaselineTimePhasedDataSet’ and ‘Assignment Baseline Work’ queries to add back in the field ‘ResourceID’ in each table to explore this data as it relates to resources not just projects.

  • Choose ‘Close & Apply’ on the ribbon.
  • On the ribbon of the main Power BI screen, select ‘Manage Relationships’ and click the ‘Auto Detect’ button at the bottom.  Power BI will discover the new data relationships in the report. When complete, it will display how many new relationships it found now that new data and fields have been added in.





Using the additional data and relationships, a stacked column chart using ‘ResourceName’*, ‘Project Name’ and ‘Assignment Baseline Work’ is possible. This one where the work of each resource is allocated.





*Note: The added fields don’t have spaces in the name.  That is created by using the ‘Rename Field’ feature of Power BI. Doing this will make charts look more professional and improve natural language queries if the data is brought into cloud for use with Power BI service in Office 365.



Tip #4 Let Power Bi help find insights

Now that the report has added fields and tables there are insights in this data that may be missed.  The Power BI service available for Office 365 has features that will discover new insights and let the user pin the useful ones to dashboards. 

  • Open the Power BI service in Office 365
  • On the ‘Welcome’ page choose the ‘Files’ option and load your update version of the Power Bi report from the content pack.





Natural Language Q&A

Power BI will start on an empty dashboard with a single object representing all the data and connections in the report just loaded.  It is ready to accept questions about the data in natural language.

Example: Ask Power Bi to “Map cost variance by resource name and project owner” and it provides a geographical view of your cost variances tied to the resources and project owner. 



Power BI Quick Insights


Next choose the ellipses ‘…’ menu for the dataset and select ‘Quick Insights’.  After a few seconds or minutes, depending on the dataset, Power BI will offer some insights it sees in the data.  Some will make no sense and some may expose issues.  It appears Lidia is running behind on her projects or on her updates of the project status.





A Power BI dashboard is born


When the Natural Language Q&A and the Quick Insights create a visual worth keeping, just pin them to the dashboard. This is just the beginning of how Project Online Power Bi Content Pack can provide powerful views into Project Online portfolios.



SharePoint / Office Dev Patterns & Practices – November 2016 release

$
0
0

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)?

SharePoint / Office Dev Patterns and Practices 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.

Some key statistics around PnP program from October 2016

  • GitHub repository forks at different repositories 
  • 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

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.

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.

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.

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.

 

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 avaialble from the SharePoint client-side webpart 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 addative 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

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!

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.

 
 ClearPeople
 Canviz
 Content and Code
 piasys
 onebit software
 rencore
 Slalom
 Triad


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

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

Microsoft Graph Explorer Update – Revamped and Expanded

$
0
0

Hi folks! We’re Toby Baratta& Elizabeth Dinella, Office Extensibility Interns who worked on the Graph explorerover the summer. Graph explorer is a web application for exploring Microsoft Graph, the unified endpoint for Office 365 and more Microsoft Cloud services. In its previous version, Graph explorer had a limited set of capabilities that didn’t allow developers to fully discover and leverage all that Microsoft Graph has to offer. Today we are happy to announce lots of cool functionality that we enabled during our internship! Now you can:  

 

Learn about what the Microsoft Graph has to offer with a cool autocomplete feature built in the request builder.  

Before, Graph explorer was clean and simple for easy REST tests. However, you needed to know the structure of queries to be able to use it - this means a lot of time flipping back to the documentation, rather than just exploring! The new Graph explorer has autocomplete, as seen below so as soon as the user starts typing, the explorer presents the options for continued queries.  



Access and use the Graph explorer, regardless of disability. 

Graph explorer is now screen-reader accessible as well as tab-through accessible. We're working with the Accessibility team to keep the Graph explorer to Microsoft's standards of accessibility to allow all developers to explore the Graph. 

 

Use the Graph Explorer even if you do not have an Office 365 account, by accessing sample data. 

You can now use the Graph explorer to access sample data without having to log in with your own account. You can run any kind of GET command that you would if logged in with your personal or work/school account, and get a response back from a demo account in Office 365.  

 

Use your personal Microsoft Account to log-in to the Graph Explorer; it previously only supported work and school accounts. 

All Microsoft accounts on Office 365 have access – including: live.com, hotmail.com, and outlook.com accounts. We're saying goodbye to the 'cannot consent' errors and saying hello to your own personal data with explicit consent. Rather than being told you cannot consent, you now can access all your personal content on your personal accounts!  

 

Access the Graph explorer with a work or school account, even if you are not an organizational administrator. 

You can now use Graph explorer to interact with your data even if you are not an administrator. Before you would hit an error message about consent, but now you can access your own information and play.  If you do have an admin account, you can explicitly consent for scopes that require admin consent on behalf of your entire organization. 





Review and return to past queries. 

In addition, we've added in a history option, so now one can quickly see what queries were previously executed in the session, as well as what the return values of those queries were. This makes it easy for someone to make small changes and revert back, or to debug different types of queries. 



 

Customize your request headers to allow in-depth testing.  

Finally, we’ve allowed you to customize any request headers. This works well with the new Excel REST APIs, allowing you to establish a session with a workbook. It also allows you to test with your own authentication token, rather than the one generated through the Graph explorer application.  

 

We hope you enjoy all the improvements we have added to the Graph explorer, if you have feature requests let us know on User Voiceor questions Stack Overflow. This internship was amazing and we are looking forward to seeing increased usage of the Graph explorer as a result of the improvements we added to it!  

 

Thanks! 

Toby & Elizabeth 

SharePoint PnP Webcast – Building multi-view Angular 1.x client-side web parts with SharePoint Framework

$
0
0

In this PnP Webcast, we covered considerations around multi-view web parts, where the presentation layer is changed based on the status of the web part. Typically single-page application solutions are implemented in a way that they store the view status within the URL. Since client-side web parts are however hosted in SharePoint pages, this is not possible and you'll need to use alternative approaches for maintaining the UI state in your customizations. Considerations are being also demonstrated with a client-side web part built with Angular 1.x.

Notice. When this webcast was released, SharePoint Framework was available as a Developer Preview release.  

Presentation covers following topics:

  • Considerations on UI state handling with client-side web parts
    • Typically this is done with URL, but that's not possible in the context of SharePoint
    • Challenge is around tracking UI status and transition accordingly based on user actions
    • Detailed technical solution depends on the exact used JavaScript framework - like React or Angular
  • UI views in the example use case

Web cast demo (7:03) shows following details

  • Use case - How the sample web part built with Angular 1.x works in practice
  • How to use UI router in Angular for tracking the UI status without URL based tracking
  • Transitions between the state and how it's implemented in the solution

Webcast presenters: Waldek MastykarzVesa Juvonen

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

Video at YouTube.

Additional resources

See following resources around the SharePoint Framework. 

What is SharePoint / Office DevPatterns & Practices (PnP) web cast series?

SharePoint / Office Dev Patterns and PracticesSharePoint / Office Dev Patterns & Practices (PnP) webcast 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 minute long web cast each Monday with few slides and a live demo on the covered topic. All web casts are published at the PnP YouTube channel 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 http://aka.ms/SPPnP-Call

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 Microsoft Tech Community (SharePoint Developer group).

“Sharing is caring”


Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 14th of November 2016


Setup SharePoint 2013 Developer VM on Azure

$
0
0

In the past setting up a SharePoint Development box was a complex and tedious experience where a little misstep would, most likely, lead to resetting the machine and starting over.  So now we have Virtual Machines on Azure, specifically there is a Marketplace image that has SharePoint Server 2013 Trial setup and Visual Studio 2015 with the Office tooling installed.  That’s most of the software that is needed to start developing against SharePoint using a single box, but we have a few items to do first.



Create Virtual Machine on Azure using SharePoint Server 2013 Trial Marketplace image

This is fairly straight forward, there a several different posts about how to create VMs.  The condensed version is to fire up the Azure Portal on your favorite browser, select New Virtual Machines, search for SharePoint Server 2013 Trial.

Select the Marketplace image and Create filling in the information that is presented to you in the different blades to customize the VM.  On the last blade before the VM is actually created there is the option to download the ARM template and parameters files.  These files and a Powershell deployment script will allow you to recreate this VM without having to go through the Azure portal.



Select OK, and the Virtual Machine is created.  Once the box is running attach to it using the Connect and the generated .RDP.





Install SQL Server 2012 Express locally

The SharePoint Server 2013 standalone installation did was to install SQL Server 2008 r2 Express locally which SharePoint would use as the data storage, but SQL Server 2012 Express works as well.  So download and select a “New SQL Server stand-alone installation or add features to an existing installation” using the default options for the wizard options.  Notice under the “Database Engine Configuration” SQL will be using Windows authentication mode with the current user as the administrator, even if that user is a local account only.  As this box is being setup as a development machine this will work best.  If the machine is to be used for non-development usage there is a different set of instructions for Setting up a SharePoint Farm.  Now that SQL Server is installed on the VM, we can move onto getting SharePoint configured.



Creating SharePoint Configuration Database

To create the SharePoint Configuration Database using the SQL Server administrator account, we will use the New-SPConfigurationDatabase in Powershell.  This is an impressive script:

Add-PSSnapin Microsoft.SharePoint.Powershell

 New-SPConfigurationDatabase -DatabaseName "<YourDBName>" -DatabaseServer "<usually ComputerName\SQLEXPRESS>" -AdministrationContentDatabaseName "<YourOtherDBName>"-Passphrase (ConvertTo-SecureString "<new passphrase>" -AsPlainText -force) -FarmCredentials (Get-Credential)

 This will prompt for the FarmCredentials which will be the user name and password for the SQL Server Administrator.  So now the databases are created and ready for use.



Configuring SharePoint

The last piece of the puzzle is to run the SharePoint 2013 Products Configuration wizard.  Since the SharePoint databases have been created, the wizard will automatically pick this up.  For this example, I created a VM named SHPT13DevBox and the database SP_ConfigDB with the New-SPConfigurationDatabase



Select Next



Select Next



Select Next and Finish which will configure the SharePoint Server.



Creating the default SharePoint site collection.

When the wizard has finished the default browser will open to the SharePoint Admin site and will, most likely, ask for the Farm Credentials user name and password.  Select the “Start the Wizard” option

Select the “Use existing managed account” and review the services being installed.  Some services may need additional information or setup and may fail, if not configured properly.  The SharePoint Farm will be configured properly even if some services fail.



The final step is to setup the Developer site collection.  The Site Collection requires a title and setting the template to the Developer site.  To improve the development experience changing the URL from “/my” to the simple “/” will set the developer site as the default site.



Select OK and the Developer site is created.



The Developer box is now ready for business! 



Can I automate this?

The simple answer is YES!  There are various articles available on using Powershell  Microsoft.SharePoint.Powershell PsSnapin and SharePoint PSConfig.exe to run the SharePoint configuration and to setup the site collection.  Finding the right solution depends on your needs and expertise.  Here is a set of different ways automate the VM creation.

-         Azure Resource Manager template

-         Azure DevTest Labs with Artifacts

-         Azure Automation

I hope this helps!

Roger Best – Senior Software Engineer, Microsoft

Building Intelligent Apps with Office at Connect() 2016

$
0
0

Across Office, we’re working to bring relevant information and automatically created insights – the intelligence  together for users so that they can make better decisions more quickly. Developers can harness this work to save users time and make their solutions more appealing and useful for their users.

Since its launch last year at Connect();, Microsoft Graph has been a key surface for exposing this intelligence – which pulls from an unparalleled amount of data across the more than 1.2 billion Office users. Microsoft Graph has been expanding the set of scenarios it covers, adding more of OneDrive, SharePoint, Planner, Excel, and OneNote. Intelligence features have been added, making it possible to get at the insights around ad-hoc working relationships and trending files in an organization -- that also happen to power the ever-useful MyAnalytics (formerly Delve). Microsoft Graph does this all while simplifying the developer experience via a simple, consistent API surface and a rich set of developer SDKs. Today at Connect(); we announced that Microsoft Graph usage is growing 35% month-over-month, that over 47,000 applications have been created by our partners and developers, and we have processed over 1 billion API transactions over the last month. We expect this momentum to increase as more services, data, and insights from across Microsoft are rolled into Microsoft Graph, and as organizations connect Microsoft Graph to their on-premises servers via expanding Hybrid support in Graph.

Of course, intelligence is only useful if people can see and act upon it. Across Office, we’re adding more extension points so that developers can bring relevant information and intelligence to users right where they work.

For many users, much of their time is spent in conversation with their colleagues, whether in e-mail, chat, or meetings, which is why bringing contextually aware information to these conversations can be so useful. Contextual awareness is a key part of the Microsoft Teams platform, currently available in preview. Users can interact with bots relevant to the work they are doing – for example, checking on the status of processes in their organization or issuing simple commands to change the flow of work. Connectors in Microsoft Teams can, for example, pull in the right information from sources such as Twitter & UserVoice to help make customer feedback close at hand for a team.

With the goal of always working toward contextual awareness, we announced Actionable Messages for Outlook at Microsoft Ignite. An actionable message lets senders embed buttons and dialogs that let users take relevant actions quickly in the context of their conversations.

For example, in an approval process mail, "Approve" actions can be taken so that users can quickly Approve, Reject, or Re-route an approval inline, alongside relevant information.

Office Add-ins feature a variety of ways to connect content in Office applications to relevant business processes, inline in your documents; we’re working to ensure those add-ins are always available and present, whether you’re working on mobile devices, a PC, or a Mac.

Intelligence and contextual awareness, as announced at Connect(); 2016, shows how these features can really transform how users work in their organization. We’re not done, though; now that we have the foundation of Microsoft Graph, Microsoft Teams, Outlook extensions, and Office add-ins well established, we’ll be able to add even more of these features at a rapid pace. You can get started by checking out the relevant SDKs for Microsoft Graph and Microsoft Teams, and stay tuned to this blog for more new intelligence capabilities.

SharePoint PnP Webcast – PnP Core team on the future of SharePoint development

$
0
0

During early November, we had a really rare occasion to have many of the SharePoint PnP Core Team members in one location at the same time, so we wanted to record a special PnP webcast with multiple team members. MVPs were there to participate in the MVP Summit and we had many of the Microsoft team members also in Redmond, so this opened up a great opportunity to have a discussion on different topics around the SharePoint customizations. This was more a podcast type of a recording, but we added some content on provided video around the covered topics with few pictures. 

Key topic which we wanted to address was around providing more insights on the future of SharePoint customizations. Where are we heading and what would be the key considerations around the customizations in the future? We built the discussion around following key questions for different people in the team. 

  • What's the future of PowerShell based customizations and PnP PowerShell cmdlet's?
  • What's the future of PnP Provisioning Engine around SharePoint Online and on-premises?
  • Will all the future APIs come only from Microsoft Graph in the future also for SharePoint?
  • How to learn the new development stack for SharePoint Framework? Guidance and pointers?
  • What's the relationship with PnP JS Core library and SharePoint Framework? What's the future for PnP JS Core JavaScript library?
  • Is all the development just JavaScript with SharePoint in future?
  • PnP has been growing from a small grass root effort as a global initiative in few years, how do you feel about that?

Webcast presenters:

Video at YouTube.

Additional resources

Here are some additional resources around the covered topics. 

What is SharePoint / Office DevPatterns & Practices (PnP) web cast series?

SharePoint / Office Dev Patterns and PracticesSharePoint / Office Dev Patterns & Practices (PnP) webcast 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 minute long web cast each Monday with few slides and a live demo on the covered topic. All web casts are published at the PnP YouTube channel 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 http://aka.ms/SPPnP-Call

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 Microsoft Tech Community (SharePoint Developer group).

“Sharing is caring”


Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 21st of November 2016

New SharePoint CSOM version released for SharePoint Online - November 2016

$
0
0

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 rhythm 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 access on latest version, rather than downloading the SDK to your machine.

Version of the newly released CSOM package is 16.1.5903.1200. Previous versions of the NuGet has not been removed, so that your existing solutions will continue working without issues and you can decide when the new version is taken into use. Notice that even though the Nuget version is increased to 16.1.5903.1200, actual assembly version of the released assemblies is 16.1.0.0. You can also check the version of the assemblies from the File Version attribute, which aligns with the NuGet version.

Picture of SharePoint Online CSOM NuGet package from NuGet Gallery with version 16.1.5903.1200

Notice that since this NuGet package is targeted to SharePoint Online, you cannot use it directly in on-premises environments (SharePoint 2013 or 2016). This is because of the server side dependencies of the APIs. CSOM versioning model and dependency to your target environment is clarified in following blog post - Using correct Client Side Object Model (CSOM) version for SharePoint customizations. We have released separate NuGet packages for on-premises. See following blog post for additional details - SharePoint CSOM versions for on-premises released as NuGet packages.

New properties and methods cross assemblies

Here's a raw list of all the changes in the classes, properties and methods within this package. 

Microsoft.SharePoint.Client

Following property has been removed.

  • public class Microsoft.SharePoint.Client.AttachmentCreationInformationUsingPathl

Following properties, classes and methods have been added.

  • public property Microsoft.SharePoint.Client.Field.NoCrawl
  • public property Microsoft.SharePoint.Client.Field.Sealed - Set support added

  • public method Microsoft.SharePoint.Client.FileCollection.AddUsingPath
  • public class Microsoft.SharePoint.Client.FileCollectionAddParameters
  • public class Microsoft.SharePoint.Client.FolderCollectionAddParameters

  • public property Microsoft.SharePoint.Client.List.AllowDeletion
  • public method Microsoft.SharePoint.Client.List.SaveAsTemplate
  • public method Microsoft.SharePoint.Client.List.SyncFlowCallbackUrl

  • public property Microsoft.SharePoint.Client.ListItem.IconOverlay
  • public property Microsoft.SharePoint.Client.ListItem.Properties
  • public method Microsoft.SharePoint.Client.ListItem.UpdateOverwriteVersion

  • public property Microsoft.SharePoint.Client.Web.SiteLogoDescription
  • public property Microsoft.SharePoint.Client.Web.ThemedCssFolderUrl

  • public property Microsoft.SharePoint.TenantCdn.TenantCdnUrl.ExpirationTimeUtc

Microsoft.Online.SharePoint.Client.Tenant

Following properties have been removed.

  • public property Microsoft.Online.SharePoint.TenantAdministration.Tenant.BlockAccessForUnmanagedDevices
  • public property Microsoft.Online.SharePoint.TenantManagement.Office365Tenant.BlockAccessForUnmanagedDevices

Microsoft.ProjectServer.Client

Following property has been removed.

  • public enum Microsoft.ProjectServer.Client.QueueMsgType

Following properties have been added.

  • public property Microsoft.ProjectServer.Client.DraftTask.TaskType
  • public property Microsoft.ProjectServer.Client.PublishedTask.TaskType

 

“Sharing is caring”


Vesa Juvonen, Senior Program Manager, OneDrive-SharePoint Engineering, Microsoft - 24th of November 2016

SharePoint PnP Webcast – PnP Core team on the future of SharePoint development

$
0
0

During early November, we had a really rare occasion to have many of the SharePoint PnP Core Team members in one location at the same time, so we wanted to record a special PnP webcast with multiple team members. MVPs were there to participate in the MVP Summit and we had many of the Microsoft team members also in Redmond, so this opened up a great opportunity to have a discussion on different topics around the SharePoint customizations. This was more a podcast type of a recording, but we added some content on provided video around the covered topics with few pictures. 

Key topic which we wanted to address was around providing more insights on the future of SharePoint customizations. Where are we heading and what would be the key considerations around the customizations in the future? We built the discussion around following key questions for different people in the team. 

  • What's the future of PowerShell based customizations and PnP PowerShell cmdlet's?
  • What's the future of PnP Provisioning Engine around SharePoint Online and on-premises?
  • Will all the future APIs come only from Microsoft Graph in the future also for SharePoint?
  • How to learn the new development stack for SharePoint Framework? Guidance and pointers?
  • What's the relationship with PnP JS Core library and SharePoint Framework? What's the future for PnP JS Core JavaScript library?
  • Is all the development just JavaScript with SharePoint in future?
  • PnP has been growing from a small grass root effort as a global initiative in few years, how do you feel about that?

Webcast presenters:

Video at YouTube.

Additional resources

Here are some additional resources around the covered topics. 

What is SharePoint / Office DevPatterns & Practices (PnP) web cast series?

SharePoint / Office Dev Patterns and PracticesSharePoint / Office Dev Patterns & Practices (PnP) webcast 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 minute long web cast each Monday with few slides and a live demo on the covered topic. All web casts are published at the PnP YouTube channel 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 http://aka.ms/SPPnP-Call

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 Microsoft Tech Community (SharePoint Developer group).

“Sharing is caring”


Vesa Juvonen, Senior Program Manager, SharePoint, Microsoft - 21st of November 2016

Viewing all 429 articles
Browse latest View live