The history being this situation…. Internet Explorer has been a corporate browser for two decades now. And many of us remember the dark ages of web development when we needed to have “IE compatible code” and “web compatible code”. As many companies invested deeply in the browser building portals that worked with specific versions, Microsoft provided a decade ago a compatibility mode, allowing the browser to “behave” like a former version of itself and stay compatible with websites that had not been updated.

Part of my role at 2toLead is to help set guidance around best source management practices either internally or for our customers. One of the questions I get often is: Should I fork this repository or do something else with it? It’s hard to get clear and simple guidance on the web so I thought I’d take a stab at it. As we’re using Visual Studio Team Services, my examples and screenshots will be based on it, but it really applies to any git service like Github or internal git servers.

TL;DR; I added two new SharePoint framework WebParts PnP sample to demonstrate how to use the Unified Communications Web API JavaScript SDK from Skype for business. This SDK allows you to do things like subscribe to a person status, start instant messaging conversations, calls… To get a look: The plain JS sample The reactJS + Office UI Fabric React sample(persona card) Long version I recently had the occasion to make my first contribution to PnP (besides creating issues and helping investigate those).

SharePoint Fest DC (Washington) 2018 is happening from March 26th to March 30th. This event will feature 2 days pre-conference workshops and 3 days of conference. You can find more information about it on the website. I’ve been selected amongst 44 other speakers to present this year two sessions: AZR204 – Microsoft Graph and SharePoint framework under steroids with Azure Functions “Modern development means client side first, backend second. However, there are still cases where you might need some backend processing, for long running operations, heavy computing consuming tasks or security concerns.

TL; DR; Microsoft replaced @types/es6-collections by the es2015.collection library in version 1.4.0 of the packages. Those had a conflicting definition of weakmap which caused issues with packages like lodash. Long version Microsoft recently release v1.4.0 of the SharePoint Framwork and it’s packages. It contains a lot of improvements and one of those probably went unnoticed by many of us. @types/es6-collections has been replaced by es2015.collection library (native, comes with the compiler/JS Engines).

This year again I have the opportunity to speak at the SPS Detroit. I’ll give a speech about “Improving DevOps using Microsoft’s Business Productivity Tools and more” and I’ll be co-presenting the session with my friend Haniel Croitoru. We’ll explore together how DevOps practices impact and improve solutions delivery for your customers and for the best. With real life scenarios and experience for the field we’ll show you how you can get started and what to expect out of it.

Visual Studio Team Services (VSTS) provides great Continuous Integration (CI) and Continuous Deployment (CD) functionalities you can leverage to implement DevOps pipelines and automation with your custom developments. If your custom solutions rely on PnP PowerShell during their build and/or deployment processes, you will need PnP PowerShell to be installed on the agent. Unfortunately the Hosted Agents do not have PnP PowerShell installed by default. Note: that documentation only applies to the Hosted and Hosted 2017 agents, the Linux Hosted Agent is not supported at the moment

Installing and setting up SonarQube may seem quite complex and tedious. I hope that this series has helped you to go faster implementing it. Now, you can clearly identify your technical debt and take actions to improve the quality of your developments. It is obvious that when a thousand problems appear in the code at once, it can be discouraging, just keep this in mind: There are false positives, make a first pass to ignore/exclude those

TL; DR You can display SonarQube static analysis results live in Visual Studio error and information console using the same rules set as the SonarQube project. Installing the extension Just go to https://www.sonarlint.org/VisualStudio/index.html and proceed with the installation. Binding the Visual Studio solution to the SonarQube analysis From the Team Explorer click SonarQube Click on connect. (if you obtain a certificate error, you must install the self-signed certificate of the SonarQube server on your machine)

TL; DR Static analysis errors will appear as of the warnings in the compilation section. A static analysis badge will also appear on the build report and you’ll be able to have detailed and comprehensive information from SonarQube. Information incorporated with the build When displaying the details of a build, you’ll now find a new section dedicated to SonarQube. Within that section, besides the quality badge, you’ll also find a link to the static analysis results details.