Version 0.22.0 of Cake has been released.
So, let's be clear, this release will break things - but it is all intentional!
This release was initially about updating Roslyn, unifying scripting engines, and targeting .NET 4.6. But one thing led to another which resulted in better support for tool and addin versioning when using preprocessor directives, and an optional in-process NuGet client.
Updating Roslyn and unifying scripting engines has been a long-awaited improvement for many of you. This brings you C# 7 features (without need for
--experimental switch), debugging with Mono (as we completely removed the old Mono scripting engine), and much, much more. It also allows us to ship Roslyn with Cake, so there's no need for Cake to actually download Roslyn anymore. In order for us to update Roslyn, we also needed to change target framework to .NET 4.6.
Tool and addin versioning when using preprocessor directives has been an issue, which has caused many questions. E.g. you may have noted that when changing version for a tool or addin, the old version was still used. Prior to this release, the only solution was to delete the tool/addin from the
tools folder. This is now fixed as Cake supports side-by-side downloading of different versions of tools and addins.
Due to unpredictable results when downloading packages using
nuget.exe, tool/addin versioning was solved by adding a intermediate directory containing the version number. This intermediate directory can however cause
MAX_PATH issues when downloading some specific packages. To address this issue, we implemented functionality in
Cake.NuGet to allow Cake to download tools and addins without the need for
nuget.exe. This functionality is currently optional through configuration, and is the first step towards removing need for
nuget.exe in Cake. Example usage to opt-in for the in-process NuGet client:
The in-process NuGet client also gives the possibility to load assemblies from NuGet dependencies. This behaviour can be enabled either via configuration or directive. Example usage for loading dependencies:
As 0.22.0 has several breaking changes, it will require addins to reference Cake.Core 0.22.0 or newer to be loaded, there's a "you're on your own anything can happen" setting to skip verification but we recommend to start targeting the newer version as soon as possible. Example usage to skip verification:
We have said it before, but here it comes again. Regardless of intentional or unintentional breaking changes, the possibility of new releases breaking something is why we always recommend you pin the version of Cake you're running, thus avoiding any unplanned broken builds. You can read more about pinning Cake version here. We always try to avoid breaking changes, but we think these new features and improvements justify the friction, and we hope you will too!
And as always thanks to all Cake contributors and users, Cake wouldn't have been possible without you!
Contributions were included from:
Full details of everything that was included in this release can be seen below.Read more...
Hi! My name is Martin Björkström and I'm a .NET Developer and father of two from Finland. I started using Cake in early 2016 and have been making contributions ever since. So far, the most notable is probably debugging support. As of April, I'm also a member of the Cake Team!Read more...
As you might already know, debugging Cake scripts using Visual Studio has been supported since the v0.12.0 release of Cake. But since the v0.16.1 release of Cake, thanks to porting Cake to .NET Core, it is now also possible to debug Cake files using Visual Studio Code.Read more...