Everything is in the title. My French blog has been running for more than six years now (gee, I’m getting old).

From 2013 to 2014, before I decided to open an English dedicated blog, I was posting every blog entry in English and in French.

Over time it got messy for both communities so I decided to open this blog. But I couldn’t move the old content to this new blog without having to spend hours doing so.

A few months ago I published articles about continuous integration for dot net core projects.

Obviously it was really early in this “new framework” lifecycle (we were still on a beta version back then) and the tooling plus processes evolved a lot since.

Good news is you don’t need anymore a complex and often crashing powershell script. You don’t need anymore special tasks either other than standard command line and azure publishing tasks.

This year I have the privilege to speak at SPS Brussels

I’ll give a speech about “setting up your release pipeline for office 365/SharePoint”. (aka devops)

We’ll see together how you can leverage azure and visual studio team services to implement devops processes and increase quality and save time.

If you’re in the area on Oct the 15th don’t hesitate to register to the event. Just as a reminder SPS are free events organized by the community with lot of great sessions. This is a good occasion to expand your network, learn a lot of things and to spend a good day.

That’s good news for SharePoint developers, the SystemUpdate method is finally available in Client Side Object Model.

Indeed, Microsoft has recently released an update for nugget packages and the method is part of the new stuff.

https://dev.office.com/blogs/new-sharepoint-csom-version-released-for-Office-365-august-2016-updated

It’s an important method because it allows you to update a list item without changing modification date, author, publishing and versioning information.

Moreover, we’re numerous SharePoint developers migrating a lot of full trust solutions to SharePoint Add-ins, some of which were using this method and in some cases we have only an app-only context. Usage of this method instead of the regular update method will avoid having documents last updated by “SharePoint App”.

This year I have the privilege to speak at SPS Oslo

I’ll give a speech about “setting up your release pipeline for office 365/SharePoint”. (aka devops)

We’ll see together how you can leverage azure and visual studio team services to implement devops processes and increase quality and save time.

If you’re in the area on Oct the 22nd don’t hesitate to register to the event. Just as a reminder SPS are free events organized by the community with lot of great sessions. This is a good occasion to expand your network, learn a lot of things and to spend a good day.

This year I have the privilege to speak at SPS Detroit

I’ll give a speech about “setting up your release pipeline for office 365/SharePoint”. (aka devops)

We’ll see together how you can leverage azure and visual studio team services to implement devops processes and increase quality and save time.

If you’re in the area On Sept the 10th don’t hesitate to register to the event. Just as a reminder SPS are free events organized by the community with lot of great sessions. This is a good occasion to expand your network, learn a lot of things and to spend a good day.

A few months ago I wrote a series of articles on how to set up a release pipeline for dnx/dotnetcore projects with vsts targeting azure web apps.

This series would require you to use a few scripts to build and publish the website executing them using powershell tasks in the build definition.

You don’t need to do that anymore because two new extensions are available on the marketplace:

I’ve been able to replace most of my scripts using VSTS DNX Tasks

This year I have the privilege to speak at SPS New York City.

I’ll give a speech about “setting up your release pipeline for office 365/SharePoint”.

We’ll see together how you can leverage azure and visual studio team services to implement devops processes and increase quality and save time.

I’ll also be giving Sebastien Levert’s session “deep dive in Microsoft graph” as he can’t make it to the event.

If you’re in the area today (I know it’s short notice) don’t hesitate to register to the event. Just as a reminder SPS are free events organized by the community with lot of great sessions. This is a good occasion to expand your network, learn a lot of things and to spend a good day.

Microsoft just released the new experience for SharePoint libraries and I know a lot of you built custom look and feel and/or components on top of the library ui. (I’m thinking in particular about ScriptLink actions)

You might be in a situation where the code you need to run will be different depending on the experience being used.

After a little bit of research, here is an example of solution.

WIth the release of SharePoint 2016 and the new MinRole feature, a lot of you would like to test migration of their custom solutions (Full Trust Code)

In order to do so, you need a 2016 dev machine (vs 2015 up to date with the latest version of the office sdk) and to install on top of that the office sdk preview 2.

https://www.microsoft.com/en-us/download/details.aspx?id=51683&WT.mc_id=rss_alldownloads_all&utm_source=twitterfeed&utm_medium=twitter

Then you only need to update references and targeted versions.