Archive for May 19, 2015

Microsoft Ignite key takeaways

Great Content, Great Vibe; Ignite is here to stay

The first thing I learned from Ignite is that it wasn’t a mistake to attend to this conference. What a vibe! It’s always good to be around people with same interests and passion when it comes to technology. At first I was a bit skeptic about the integration of different Microsoft events but it turned out to be a success. The high quality sessions, well organized location (WiFi still kinda sucked but let’s call that a tradition) and for the first time I felt the Expo hall was actually a great addition to the conference. Normally this is just a platform for vendors but this time Microsoft had the biggest stands which were really good. People from the product teams where walking around every day to give information and support on a level I hadn’t experienced before. Awesome! So what are the key takeaways for me as a SharePoint / Office developer?


Self-contained Applications Cross Platform using ASP.NET

During the conference it was made clear that to drive productivity to the next level, the experience Microsoft offers should not be bound to a particular brand of device or even Operating System. This is a very bold statement if you ask me. The verge wrote an excellent article comparing its vision to Apples vision on this matter:

A big help in getting to that experience are Self-contained Applications. We know this principle from Java for quite some time now. Basically Self-contained Applications include their own runtime and are built in a way that they’re deployable to any kind of platform. For instance using NodeJS for server operations and using AngularJS to build a Single Page Application you can create a package that is deployable to every platform that runs NodeJS. On top of that the entire application model (server – client) is written in 1 common (cross platform) language: JavaScript. These are non-Microsoft technologies but are advertised by Microsoft to leverage the new API’s Microsoft is offering in Office 365. The Office Dev team even supported this by handing out Raspberry Pi’s to stimulate development for Office on different platforms.

Finally Microsoft adopts this principle with the new ASP.NET 5. The DNX (.NET Execution Runtime) is open source now that can be found on GitHub ( and can run on any kind of platform. Given this fact we don’t have to run an ASP.NET MVC Application on an IIS server but we can use a Linux based server with the ASP.NET 5 runtime! Making the runtime open source gives a lot of insight in the .NET platform and is a huge leap forward for Microsoft. See a great session from Glen Condron here:


Office 365 as Data Hub (ePaas)

Is SharePoint going away? Expected is that the brand name “SharePoint” is fading but the SharePoint technology is very much alive. It is the very foundation of the Next Gen Portals in Office 365. These portals are offering a way better experience for End Users but also from a developers perspective this is a huge improvement. For a while now Microsoft is unifying its API for Office 365 into one endpoint. With this endpoint developers can get all the data out of Office 365 they want. There was an example in a developer session where Rob Howard rebuilt the Video Portal by just using the Unified API in his own app running on NodeJS. In this case Office 365 is used as a Data Hub and not as a platform where we try to customize the OOB experience. When a different experience is required, we can now built it ourselves by leveraging the API. Andrew Connell describes this as ePaaS (Enterprise Platform as a Service) in this excellent post:


SharePoint 2016

Remember the SharePoint Conference in 2012? In my opinion this was quite a confusing one. Microsoft just bought Yammer and was hinting towards the Cloud first approach for SharePoint Online thereby leaving the development on the On-premises version a little bit in the open. There was a lot of speculation on if SharePoint would made it to a next On-Premises version or not. In 2014 it became clear that SharePoint 2016 will be the successor of SharePoint 2013 On-premises.

Now at Ignite, Bill Baer announced what SP2016 is going to offer us On-premises and a little hint (again) on the future. “SharePoint 2013 will be the Foundation of every future SharePoint version.” he said in a session full of SharePoint 2016 intell! Wait, does that mean we can expect a SharePoint vNext On-premises after 2016? That wasn’t confirmed but wasn’t denied either. The vision on this I think is to bring SharePoint On-premises and SharePoint Online more and more together and fade the boundaries between the two. The Hybrid scenario for instance now is part of the SharePoint Products configuration wizard with the Scenario picker. This will make it way easier for admins to configure a hybrid scenario between SharePoint On-Premises and Office 365.

Microsoft has done some outstanding work under the hood to make SharePoint 2016 “Cloud-like”. For instance they’re introducing zero-downtime patching (just like Office 365), a new server role called minRole (minimal server role to scale up fast) and again a stretch of the limits and boundaries.

On a telemetry perspective, SharePoint 2016 will introduce a complete new experience to monitor real-time usage data of the entire SharePoint Farm. Think Google Analytics interface with lots of graphs for indication. Things that are monitored for instance are 404 responses, browser / device info and latency statistics between client, server and SQL.


We need windows 10!

This was already a big factor in the Keynote. Windows 10 will give us a whole new level of user experience. With Cortana integrated in and a lot of new compliance and security features all indicates this will be the biggest release of the Windows operating system to date. A couple of features can be found here:

Cross Device experience will be elevated to the next level with Continuum! This Experience will bring mobile devices and desktop / laptop devices even closer together. This can finally leverage the mobile devices to a “work machine” instead of a “reading machine” when connecting to an external display.

From a developer perspective the thing I liked most is that Microsoft is coming with a Windows 10 Nano version that can be run from a SD card for instance on a Raspberry Pi. This move clearly indicates Microsoft is betting on the IoT (Internet of Things) world to use Windows 10 as a platform for this. There is already a preview available as part of the Windows 10 Insider program:

More of the new key Windows 10 features:



It was great to (re)connect to all my SharePoint friends worldwide and see a lot of excellent content, sessions and labs. Ignite was a great event for me and I hope to return next year! Here a some links to other sessions I saw that I think were very good.

Deep Dive into Safe SharePoint Branding in Office 365 Using Repeatable Patterns and Practices

Building Business Apps Like They Do in the Valley with AngularJS, Node.js, and More

Transforming Your SharePoint Full Trust Code to the Office App Model

MVP Panel: Sample Apps and Intelligent Solutions Showcasing Office Graph and Delve Extensibility

Developing Web and Cross Platform Mobile Apps with Azure Active Directory

Dealing with Application Lifecycle Management in Microsoft Office 365 App Development

How to setup a dev environment with Officedev/PnP using Visual Studio Code in under 15 minutes

Ok so maybe 15 minutes is a little bit ambitious, but the point of this post is to show how easy you can setup a dev environment for anyone that is interested in contributing to PnP (or any other GitHub project for that matter).

Visual Studio Code

Recently Microsoft released a preview version of Code. Basically Code is a very slim (and free) version of Visual Studio and can be used to “Build and debug modern web and cloud applications.”. Sounds good right!? At first sight Code is not much of an editor when compared to Visual Studio of course. But since it’s free and has GIT compatibility I wanted to gave it a shot with the OfficeDev PnP Git repository to show how easy it is to contribute to the community.


Let’s set this environment up!

Before I start writing this post I already had a Github account and forked the PnP to my Company Github. This is a very easy step which is described in the first chapter of this wiki:

After you have this fork in place you can close down this wiki and continue here and Download Code from and run setup. No further questions asked it just installs. Opening Code gives us the following interface.


Advanced GIT setup

In my search for good tutorials on how to setup GIT with PnP I came across the PnP Wiki which I mentioned before, but also this post from Patrik Björklund I decided to follow this last one for a good GIT setup. The next steps are coming from this post.

Download CMDer ( and Pathman ( and unzip in a folder of choice for tooling. Pathman is a nice piece of software with a GUI to add Path variables. CMDer is a good looking commandline tool with GIT aboard. When both tools are unzipped start Pathman and add the path to bin folder where git.exe is stored “[CMDER folder]\vendor\msysgit\bin\”


Next up you can follow step 2 of Patriks Blog to setup authentication with Github. This makes it easy to stay authenticated so you don’t have to put in your credentials constantly when developing. However if you don’t want to do this you can continue here.

Get your GIT together

Ok the following step is to get all Git repositories in sync so we can start developing! Fire up CMDER and start typing the following set of commands:

First set your CMDER path to a folder on your filesystem where you want your PnP repository to land. Then type:

git clone (This is the url to the Fork you made in the very first step of this post)

The clone will land in the folder “PnP” so use cd PnP to go to your new clone. Next you need to create a remote to the original OfficeDev PnP repository to retrieve latest updates when you want to.

git remote add upstream

Now we create a dev branch for development by using:

git checkout -b dev origin/dev

Now make sure that the upstream remote is fetched so we can pull it to the dev branch

git fetch upstream

In order it looks like this


The final step now is to checkout the dev branch and pull the upstream to the dev branch

git pull upstream dev

This action will fill your console with a lot of info so I’ll spare you that screenshot :). When this is done you can setup Code with this fresh Git branch.

Code and GIT

Now we have a valid dev branch on our local dev machine we can configure Code to use this folder. This way we can commit changes to our branch from Code. The only thing you have to do is Open Folder and choose you PnP GIT repository on your filesystem and start Coding!