TL; DR

Planning, Sources, Build, deployment, testing: VSTS. Analysis: Azure VM (SonarQube), Azure SQL.

Parts of our software factory

Because we use a maximum of services cloud at 2toLead I realized the following installation:

• Source control: VSTS (git or tfsvc, doesn’t matter)
• Build system: build 2015 VSTS
• Build machine: provided by VSTS as a service
• SonarQube machine: Ubuntu Server hosted in Azure
• Data SonarQube: Azure SQL Database, 10 DTU

Note that to facilitate the management of the SonarQube “box" we are going to install Docker on the ubuntu machine. Once docker installed, we’ll hydrate two containers, nginx and SonarQube.

TL; DR

Static analysis allows you to understand weaknesses of your code based on a set of rules. You can have it run automatically on a server or from the IDE.

Introduction to static analysis

The principle of static analysis is to take advantage of rules set more or less complex, those will detect patterns in the code that are problematic, categorize their importance and suggest a resolution.

A few examples:

This year again I have the opportunity to speak at the SPS Ottawa.

I’ll give a speech about the graph “Migrate your custom components to the SharePoint Framework ”. We’ll see how you can migrate your existing investments in SharePoint development (either full trust solutions or add-ins) to the new SharePoint framework. Migrating these components will not only help you make sure you stay ahead of the technology but will also improve users experience and help migrating to Office 365.

TL; DR

This series will explain *how to set up an automated code quality analysis* which is almost free of charge with Visual Studio Team Services, Docker, Azure, and SonarQube.

Preamble

There is bad quality code in every development project. This goes from the quick and dirty hack we are not proud of, to the long-forgotten code written by a developer who quit the company.

The problem with this code is that it will eventually accumulate and slow down the pace of new features delivery. The reasons are various, a lot of time spent in bug fixes, refactoring, support…

This year again I have the opportunity to speak at the SPS Brussels.

I’ll give a speech about the Azure functions and Microsoft flow “Introduction to Azure Functions and Flow”. Flow and Azure Functions are two new tools you now have for rapid applications development. It’s a revolution that changes the way of building and delivering modern applications. Instead of shipping a monolithic bloc, which can take up to a few months, we’ll now deliver each feature as a part of the solution.

You may not know it but Microsoft has changed the organization of the MVP program during these last few years. They used to nominate new MVP’s every 3 months and renew people every year on anniversary date. One of the changes the brought to the program is around the renew and nomination cycles. New MVP’s are awarded every month and existing ones are renewed all together every year in July. I used to be an “April MVP” and I was used to blogging about my renewal in April. I’m pleased to announce I’ve been renewed MVP for year 2017-2018 on the Office Servers and Services category. Let’s go for another year :)

This year again I have the opportunity to speak at the SPS NYC. I’ll give a speech about the SharePoint Framework and devops methodologies “Is it possible to do devops with the SharePoint framework?”. You had it all right with solutions and add-ins. Your release pipeline was set up. Do new technologies and methodologies mean starting over? Don’t panic I’m here to help! Together we’ll see how to set up a devops pipeline for SPFX developments with:

If you’re following the SharePoint community, you’ve probably heard of the “SharePoint framework in his own words” video series. https://www.voitanos.io/ is behind that initiative

( @andrewconnell founded voitanos recently)

The idea is to get the thoughts from the community and people who have been around the SharePoint development for a few years. If you don’t know that series I’d encourage you to check it out and I also hope that the product team behind the framework is listening the that super valuable feedback.

If you’re building modern SharePoint components (Framework or not), there’s a high chance you’re using TypeScript.

In that case you’re probably using @types/SharePoint to provide auto-completion as well as some level of understanding for the compiler of what’s going on.

There’s one object in particular that SharePoint hydrates for us to give some understanding of where the user is and what he/she is doing: _spPageContextInfo.

A lot of properties were missing in those type definitions, old stuff like the web Id but also new things coming from SharePoint Online like canUserCreateMicrosoftForm.

Microsoft recently made changes around look and feel customizations for SharePoint Online.

If you create a new site collection and try to edit page layouts, master pages or even image renditions, there’s a high chance you’ll get an access denied error message. That even if you’re site collection administrator.

Investigating further and checking your permissions on the master page gallery library, you will notice that every and each user has a “deny” permission for “Add and Customize Pages”. That permission level is not one of the originals we’re used to in SharePoint.