Blog (Page 17)

Version 0.19.3 of Cake has been released.

This is a minor hotfix release for 0.19.2, which fixes so SignTool path is resolved by default also with the Windows 10 SDK.

Contributions were included from:

Full details of everything that was included in this release can be seen below.

Version 0.19.2 of Cake has been released.

This is a minor hotfix release for 0.19.1, which fixes an issue discovered with MSBuild logger paths not being correctly quoted, causing issues logging to paths containing spaces.

Contributions were included from:

Full details of everything that was included in this release can be seen below.

Since version 0.18.0 of Cake, there has been support created for Visual Studio 2017. The support was added to the MSBuild tool to search for the default installation locations of the various flavors of MSBuild. The default locations did not require an external dependency on the Microsoft.VisualStudio.Setup.Configuration.Interop package that was created by Microsoft to help locate Visual Studio 2017 installations.

Shortly after the release of version 0.18.0, Microsoft released a tool called vswhere to help locate Visual Studio and other products in the family. This tool was released with Cake version 0.19.1 to allow everyone that moved to Visual Studio 2017 to get their builds up and running.

This post is going to walk through the different pieces of functionality supported by the VSWhere tool.

Version 0.19.1 of Cake has been released.

This is a minor hotfix release for 0.19.0, which fixes an issue discovered in the new VSWhere aliases.

So what is VSWhere? One issue with Visual Studio 2017 is that it can be installed anywhere, and you can have multiple versions side by side. As a result the registry keys, and standard paths previously used to identify where Visual Studio was installed, no longer apply.

This is where VSWhere comes in. It's a utility that can identify and list current installations of Visual Studio, as well as other developer products.

VSWhere is available on NuGet (and Chocolatey) which means you can fetch it using the tool pre-processor directive like this:

There are a couple of VSWhere aliases available in Cake. If you just want to use the latest Visual Studio version available - then there's the VSWhereLatest alias. A complete example of fetching the VSWhere tool and using it to find path to MSBuild is shown below:

Contributions were included from:

Full details of everything that was included in this release can be seen below.

Version 0.19.0 of Cake has been released.

This release of Cake is a smaller release in preparation for upgrading Cake itself to utilize latest RTM .NET SDK and Visual Studio 2017. The goal for v0.20.0 is also to unify around one scripting engine - Roslyn version 2.0 and depreciating the Mono scripting engine, this will likely result in raising the minimum supported version of .NET and Mono. We will before next release document and communicate exact versions.

We strongly recommend you pin the current version of Cake your using to avoid any unplanned interruption in your builds as the result of any potential future breaking changes. The Pinning Cake Version under the tutorials section of our website describes how to achieve this with the default bootstrappers.

Please let us know if you run into any issues with this latest release.

Once again, the Cake Team have been overwhelmed by the number of contributions from our Community Members. Simply put... THANK YOU!

Contributions were included from:

Full details of everything that was included in this release can be seen below.