Full Framework 4.7 & Core 2.1 project in solution, Frosting the only runner I can use?

[klabranche]

I'm currently on cake 0.33, was looking to go to 1.0.

Am I reading the docs right? I'd have to move to cake frosting to get a single build script as I current have atm in 0.33?

[pascalberger]

There hasn't changed anything in this regard between 0.33 and 1.0.

There are different runners available for Cake. Cake.Frosting, which allows to write your build script as console applications is one of those. But you still can use any of the script runners, like Cake .NET Tool or Cake Runner for .NET Framework. Cake Runner for .NET Core is also still available if you need to run on .NET Core 2.0. For newer .NET Core versions Cake .NET Tool is the recommended way to run Cake scripts. These runners were also already available like this in 0.33. See Cake Runners for an overview of the available runners and supported platforms.

[gitfool]

Really? Why? That has not been my experience. I have a number of projects using the old .csproj format being built by Cake, using the dotnet tool.

Maybe I'm misremembering since I switched to the new csproj format for all projects, old (full framework) and new (dotnet core), a long time ago.

[pascalberger]

It should really not make a difference if your buils runs on .NET Core or .NET Framework. In both cases it in the end just calls out to msbuild or dotnet. There's no hidden magic involved in here, only the Cake build script starting a process.

[klabranche]

Understood. :-)

[augustoproiete]

If it helps, here is an example of a Cake script that builds a .csproj in the old format using the dotnet cake tool.

[klabranche]

Not that you need my assurance but can confirm that cake tool runner is able to work with ff & core just fine, new and old csprojs... Just converted my project to use dotnet cake instead. build.cake worked without any changes accept for one addin that isn't compatible with 1.0.... luckily was easy enough for me to get around that issue. :-)