• 18/11/2015

    Automatically increment SharePoint feature version number during build with build 2015

    A few months ago Microsoft released a new automated build system with visual studio online /tfs 2015.

    This new mechanism is way more open than previous XAML builds, tasks based and easier to customize.

    One of the available tasks allows you to run a powershell script.

    Let’s  say that for one reason you want to increment automatically the version number of your SharePoint features when building.

    If you have a quick look at the “.feature” file you’ll notice that the version attribute looks like a serialized object (instead of simply being the version number), this is way more complicated than simply parsing a XML file.

    If there is a well-documented solution for XAML builds, none exist for the new build mechanism.

    So I took the time to find a solution and create a powershell script which does something similar and that you can customize to fit your needs. Have fun building stuff!

    • 10/11/2015

    Speaking at SharePoint Saturday Ottawa 2015

    This year again I have the opportunity to speak at the SPS Ottawa. I’ll give a speech about the ALM capabilities for SharePoint/Office365 in Azure “Setting up your release pipeline for SharePoint in Azure”.


    If you’re in the area Saturday November the 21st 2015 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.


    See you there!


    • 3/11/2015

    Disabling SharePoint’s SEO features

    I recently had a customer who wanted to disable SharePoint’s native SEO capabilities (Search Engine Optimization) including:

    • Sitemap generation

    • Canonical url generation

    • Metadata generation on pages

    • Explicit titles generation

    • Etc

    The main reason was he had very specific needs and wanted to implement his own custom SEO features.

    The thing is that feature is hidden and enabled by default for any publishing site.

    The simplest way to disable it then is using powershell, here is the command in case anyone else needs it.

    Disable-spfeature [Guid]"17415B1D-5339-42F9-A10B-3FEF756B84D1" –Url http://urldelasitecollection