PnP Sites Core and PowerShell Special Interest Group May 3, 2017

Here is the summary for the PnP Sites Core and PowerShell SIG call from May 3, 2017. I will add the link to the video and add the timings when the video recording has been posted.

Updated May 6, 2017 – Added video link and timings.

 

3:16 – April Stats

  • 4,916 Unique Tenants
  • 2,048,306,419 http requests
  • 22,850 Unique Github Visitors (avg 2 weeks) – GitHub limitation
  • 127,343 Views in Github(avg 2 weeks)
  • Most used capability – Provisioning Engine 1306 tenants
  • Top 5 countries based on tenants
    • US
    • UK
    • Netherlands
    • Germany
    • Sweden
  • Top 5 countries based on requests
    • US
    • Netherlands
    • Denmark
    • Sweden
    • Germany
  • Guidance and code on customizations options around SPO modern experiences
  • They are aware of the limitations and missing functionality must make sure things are constant and not changing for next 3-5 years

8:28 – Modern UI Experience Scanner – Released

  • Demo by Bert Jansen
  • Analyzes your tenant for “modern” user interface compatibility
  • Scanning for:
    • Sites not using “modern” pages
    • Lists and Libraries rendering using the classic user interface and the reasons why they do so
    • Customizations in the modern user interface
  • Working on modern equivalent for user custom actions
  • Open source on Github – https://aka.ms/sppnp-modernuiscanner
  • Quick start guide on Github
  • Requires access to everything because it scans everything
    • Can use app-only Principal
      • Instructions on Github readme
      • Safe guard your client id and secret
  • Everything starts in parallel defaults to 10 threads
  • Can get throttled if you are too aggressive
  • Depending on site collection account it could take days to run, not a big deal because low memory usage
  • Outputs reports in csv files
  • Where should the modern page experience be enabled?
  • Enabled for all modern team sites
  • Enabled on most classic team sites
  • If the site has a lot of custom pages they assumed the site does not want modern experience
  • Modern ui not currently created for all list types
    • Announcements, tasks, and calendar lists
  • JSLink and XSLLink customizations disable modern experiences
  • Shows where the feature has been disabled site collection, web, or list
  • Publishing fields and geo-locations fields prevent modern ui
  • Reports show customizations which would be ignored on modern ui
    • Masterpage
    • Custom action
      • ScriptLink not allowed on modern ui
    • Alternate CSS

39:36 – New Provisioning Engine Schema design in Progress

41:12 – New Guidance

44:12 – Q&A

  • SharePoint FrameWork Referencing Styles – CSS/styles encapsulated with a prefix
  • Guidance on testing and provisioning a site – Provisioning engine tested on a regular basis
  • Dev/Test/Prod (ALM) – Working on Guidance

Office Dev PnP – SPFx/JavaScript Special Interest Group 4/27/17

A friend of mine mentioned an idea to me that I really liked and I could definitely see the need for. He suggested that, at the moment, there is no good synopsis of what happens in the Office Dev Patterns and Practices calls that happen on a regular basis. He said he didn’t have the time to take this on but I was free to if I wanted, thank you Eric. I’ll do my best to get a synopsis published the same day as the calls. I’ll run a synopsis of all the calls for PnP.

What is Office Dev PnP?

The Office Dev PnP is an open source, community driven initiative that is backed by Microsoft and Microsoft resources. The goals are to provide tools, samples, and guidance on developing for SharePoint and Office365. There are a lot of samples in the PnP GitHub Repository. There are other repositories in this area as well if you want to contribute to the PnP.

 

Special Interest Group Calls

There are a few Special Interest Group calls relating to different areas of the Office Dev PnP. Eric Overfield does a pretty good job of explaining what these calls are and how to join them so check out his article, Participating in the SharePoint / Office 365 Dev Patterns and Practices (PnP) Community Initiative.

 

April 27, 2017 SPFx/JavaScript SIG Call

4:17 – Opportunities to Participate

  • Demo an SPFx Webpart
  • Demo sp-pnp-js in a Project
  • Contribute on GitHub
  • Provide Feedback

5:14 – PNP-Core Updates

  • 2.0.4 Released – Fixes SPFx blocking bug
  • Doing beta releases now – sp-pnp-js@beta
  • Checkout wiki and developer guide
  • Search Improvements
  • Updated React SPFx samples to work with sp-pnp-js
  • Report issues in the GitHub issues list with enough details
  • Graph support in process though early stages, discussion in issues list

11:58 – SharePoint Framework Updates

17:30 – What engineering is working on

  • New capabilities
    • Web part to web part connections – sending events
    • Modern UI extensions
      • Modern JSLink and UserCustomAction
      • Additional Yeoman templates
    • Workbench improvements
    • SPFx improvements
    • Numerous topics for both online and on-premise.
    • Working on on-premise for 2016, not 2013 at first depending on demand
  • Other
    • SharePoint document consolidation to single location eventually to docs.microsoft.com/sharepoint
      • MSDN docs will go away because the platform is super old
      • All MSDN SharePoint docs will be moved to dev.office.com/sharepoint then to final location

20:34 – Demo Vesa SPFx VS Extension http://aka.ms/spfx-vs-extension

  • Still using Yeoman for templating
  • Early alpha release available
  • Other releases coming soon
  • Template shows under the Office/SharePoint section for new project
    • Launches wizard
    • Can click generate or go to Advanced to see/modify the full yeoman command
      • -skip-install switch to skip the npm install
  • Can add more web parts
    • Add new item to project
    • Select Office/SharePoint – SharePoint Framework
    • SPFx Web Part
    • Prompted with smaller wizard
  • F5 launches gulp serve
  • Does not introduce any new templates, just uses the yeoman templating
  • Missing Features
    • Native debugging
  • This is for those that want to do SPFx in Full Visual Studio instead of VS Code

30:09 – Demo Sebastien RiotJS

  • List Viewer Web Part

Available in Github https://github.com/sebastienlevert/spfx-riot-list

  • Need riot and riot-typescript added to package.json
  • tsconfig.json add experimental decorators to true
  • Extend RiotClientSideWebPart
    • Handles the mounting to the DOM
  • Riot allows separation of view and component like Angular
  • Using await/async from TypeScript
  • Using PnP getAs ODataEntity
  • Must call update to update the ui after asynchronous calls
  • Riot also includes a router

46:08 – Open Discussion

  • Any headway with gov farm support for SPFx?
    • No dates
    • Wrong people to ask
    • Right way to find right people to ask would be to have the gov client to contact the gov farm people.

Guidance on calling external APIs, WebApi/Azure Functions early next week

Next Meeting May 11th.