Mattias Karlsson

This is what I got on a 2 year old Intel nuc i7 with SSD First run: ``` Task Duration -------------------------------------------------- Clean 00:00:00.0160194 Restore-NuGet-Packages 00:00:03.1897614 Build 00:00:02.8009840 Run-Unit-Tests 00:00:01.3675296 --------------------------------------------------...

Reran it on another machine HP Envy i7, 8gbs ram and SSD First run: ``` Task Duration -------------------------------------------------- Clean 00:00:00.0157910 Restore-NuGet-Packages 00:00:01.8415308 Build 00:00:01.8083681 Run-Unit-Tests 00:00:01.1041097 -------------------------------------------------- Total: 00:00:04.7712985 Days...

Is this still an issue I just in Cake 2.1 tried the following ```cake #addin nuget:?package=Microsoft.Data.SqlClient&version=4.1.0&loaddependencies=true var target = Argument("target", "Test"); Task("Test") .Does(() => { const string connStr = "Data...

VSWhere support is already built into Cake https://cakebuild.net/api/Cake.Common.Tools.VSWhere/VSWhereAliases/ Was added 2017 in Cake `0.18.0`. https://cakebuild.net/blog/2017/03/vswhere-and-visual-studio-2017-support

I think this initially best would be implemented and tested as Cake module. Example of Cake modules: https://github.com/cake-contrib/Cake.DotNetTool.Module https://github.com/cake-contrib/Cake.Chocolatey.Module Documentation around modules here https://cakebuild.net/docs/fundamentals/modules

Hmm there's something interesting potentially happening on MacOS, see this in the Bitrise MacOS logs too now ``` Starting test execution, please wait... A total of 1 test files matched...

@MariaSolOs https://github.com/cake-build/cake/pull/3456 sorts the issue you're seeing

You should be able to use any newer .NET 6 SDK with Cake, do you have an example of what you're trying to do with Cake that doesn't work.

In develop Cake already uses NuGet client libraries 6.2.1, so that will come out with the next release. Those client libraries are only used internally by Cake to install addins...

ok, you could probably do `dotnet restore ./` too to restore all.