cake-build / cake-vs Goto Github PK

I was going to start an issue about another syntax highlighting issue and realized I'm starting a bunch.
The bigger picture is that it would be good to have Roslyn semantically highlighting everything so that there can be no inconsistencies to maintain, especially as new features get added to the language.

Hopefully putting the burden on Roslyn will solve these and future issues as well:

• #40 Syntax highlighting ignores /* */ style comments
• #42 C# keywords inside strings should not be highlighted
• Not all keywords are highlighted (public and static are two)
• The @ is not colored the same as the quotes in verbatim strings
• \" is incorrectly detected as an escape sequence and the string highlighting is inside out thereafter: @"Data Source=(LocalDb)\" + "v12.0"
• using is not properly colored for the statement version

Please add support for Visual Studio 2017

The task parser does not read tasks defined in nested Cake files loaded via #load

It seems to me that build.cake cannot be on a sibiling path of the solution, but only on a parent path.

With
\git\MyProject\src\MySolution.sln
\git\MyProject\BuildScripts\build.cake
The tasks are not detected

When i moved to
\git\MyProject\build.cake
it was detected

To include things like:

• GitReleaseManager for generating release notes
• GitVersion for asserting Semantic Version number, including updating of required files
• Push develop version of VSIX to MyGet

NOTE: This is not an exhaustive list, just things I am thinking about as I type.

Hi

I have noticed that PR #67 has been merged into the develop branch.

When will this make its way over to the main branch/be published to visual studio gallery so the extension can be downloaded in Visual Studio 2017?

Thanks

Right now if I want to control tab and space behavior I need to use the VS Options/Text Editor/Plain Text node, but I would really like to maintain different settings between plain text and .cake files.

Some projects may enforce special coding style guidelines on their projects. To be more flexible in this area the regex that is used to identify task names should be more flexible.

This issue is the result of the quick discussion in the gitter chat:

@gep13 https://github.com/cake-build/cake-vs/blob/develop/src/TaskRunner/TaskParser.cs#L25 Are you open to a PR that will improve that regex to https://regex101.com/r/vrnDgB/1 ?
@gep13 https://regex101.com/r/vrnDgB/3 is even better ;)
@nalla certainly not against a PR. /cc @agc93

Before 0.18.0 arrives, we can update to 0.17.0/1 (since it fixes the xUnit.NET dependency). That way, we at least get up-to-date templates etc before 0.18

This would simply be amazing!

The pattern used to identify tasks only recognises names composed entirely of letters (i.e. no numbers, symbols or whitespace).

Since these are all valid, the task parser should allow them.

• Ready for publishing to Marketplace
• Will be similar to what is done for VSTS and VsCode extensions

It seems that Cake for Visual Studio is looking for "Cake.exe" either in the solution folder or in the PATH environment variable. If not found, Visual Studio gives the status bar message : "Could not find Cake.exe in the local folder or in the PATH".
The standard use case for Cake is to use the build.ps1 bootstrapper script to install the Cake tool with its dependencies beside the solution.

I have another use case : my repository contains many solutions, and add the full Cake tool with dependencies to all the solutions would be overkill.
So I would like to add a full version of Cake (with its dependencies) to my repository, in a common path above all my solutions, to be able to use it directly when pulling the repository (without adding it to the PATH).

This use case works with a script using build.cake and cake.config files, but doesn't work with Cake for Visual Studio since it can't find Cake.exe.
So providing an option to set the Cake.exe path (absolute or relative to build.cake or the solution file) would be highly beneficial in this use case.

@DixonDs commented on Mon Mar 13 2017

Please, update Cake extension (https://marketplace.visualstudio.com/items?itemName=vs-publisher-1392591.CakeforVisualStudio) for VS 2017

Visual Studio 2015.3, extension version 0.1.1.0.

// comments are styled. /* */ are not styled, regardless of whether they are spread across lines.

Also, this should work like it does for cs files:

/*
DoA();
/*/
DoB();
//*/

So you can switch with one keypress:

//*
DoA();
/*/
DoB();
//*/

The template for a build.cake file is missing a semi-colon on line 30 and doesn't compile out of the box.

I have a build.cake file in the root of my solution. It loads another file via #load "src/base.cake". These are not loaded in the Test Runner Explorer (pictured below).

Let's start with 0.1.0 and we will apply semantic versioning going forward

Creating a new addin project using the project template creates a project targeting .NET 4.5.2 (resulting in a NuGet package using lib/net452) which is not supported by Cake.

These projects should target .NET 4.5 (net45) instead.

The idea is to be able to open a possibly pre-existing solution and then right click and select 'Initialize Cake'.

Using a gui and user input it would give you the ability to have the properly files generated for you.

In the backend it might create and add a cake script project placing the files were the user likes, where they can then edit and debug the scripts from there, but it may use the user input to add certain switches pr argument that may alter the behavior of cake initially.

I hope I explained well :D.

It would be nice to be able to collapse and expand sections of code by method and even more awesome to be able to collapse either entire Task statements or Does statement lambdas.

• Just using what is included in Visual Studio just now, but should likely add to build process at some point.

Version
0.2.0.0
Last updated
7/9/2017, 05:32:23
Publisher
Cake Build

If you have defined a task name like "Run-Unit-Tests"

Task("Run-Unit-Tests")
    .IsDependentOn("Build")
    .Does(() =>
{
    MSTest("./src/**/bin/" + configuration + "/*.Tests.Unit.dll");
});

it will not be showed/available into "Task Runner Explorer".

Changing the "minus" into "underscore" solve (workaround) the issue.

Currently var is bright blue in PreprocessorVariable = "var.SourceDir".
VS2015.3, extension v0.1.1.0

As we discussed, this is what I am seeing in the dark theme:

Seems ok in here though:

Storing the nupkg files used by the templates in the repository is inefficient and should be downloaded on demand/on build instead. Initially raised by @devlead from #11

I've got a .NET Standard class library project with the following structure,

src/
│
├───Cake/
│   ├───tools/
│   ├───build.cake
│   ├───build.ps1
│   └───cake.config
│
├───Project/
│   └───Project.csproj
│
├───Project.Tests/
│   └───Project.Tests.csproj
│
└───Project.sln

The Cake build scripts located within the src/Cake/ folder are added to the Project.sln solution within a Solution Folder (right click solution -> Add -> New Solution Folder), so that the Solution Explorer shows this (I've redacted some information),

With this project layout, the Task Runner Explorer doesn't list the tasks declared in build.cake.

Aplicación: devenv.exe
Versión de Framework: v4.0.30319
Descripción: el proceso terminó debido a una excepción no controlada.
Información de la excepción: System.NullReferenceException
en Cake.VisualStudio.Helpers.Extensions.RequiresOffset(Microsoft.VisualStudio.Text.ITextSnapshotLine, System.String[])
en Cake.VisualStudio.Editor.SmartIndent.GetDesiredIndentation(Microsoft.VisualStudio.Text.ITextSnapshotLine)
en Microsoft.VisualStudio.Text.Editor.Implementation.SmartIndentationService.GetDesiredIndentation(Microsoft.VisualStudio.Text.Editor.ITextView, Microsoft.VisualStudio.Text.ITextSnapshotLine)
en Microsoft.VisualStudio.Text.Editor.Implementation.CaretElement.MapXCoordinate(Microsoft.VisualStudio.Text.Formatting.ITextViewLine, Double, Boolean)
en Microsoft.VisualStudio.Text.Editor.Implementation.CaretElement.MoveTo(Microsoft.VisualStudio.Text.Formatting.ITextViewLine, Double, Boolean)
en Microsoft.VisualStudio.Text.Editor.Implementation.CaretElement.MoveTo(Microsoft.VisualStudio.Text.Formatting.ITextViewLine, Double)
en Microsoft.VisualStudio.Text.Operations.Implementation.EditorOperations.MoveCaret(Microsoft.VisualStudio.Text.Formatting.ITextViewLine, Double, Boolean)
en Microsoft.VisualStudio.Text.Editor.Implementation.MasterMouseProcessor.HandleMouseLeftButtonDown(Boolean, Boolean, System.Windows.Point)
en Microsoft.VisualStudio.Text.Editor.Implementation.MasterMouseProcessor.DefaultMouseLeftButtonDownHandler(System.Object, System.Windows.Input.MouseButtonEventArgs)
en Microsoft.VisualStudio.Text.Utilities.WpfMouseProcessor+<>c__DisplayClass34_0.<UIElement_MouseLeftButtonDown>b__1()
en Microsoft.VisualStudio.Text.Utilities.WpfMouseProcessor.MouseProcessorHandler(System.Windows.RoutedEventArgs, System.Action1<Microsoft.VisualStudio.Text.Editor.IMouseProcessor>, System.Action, System.Action1<Microsoft.VisualStudio.Text.Editor.IMouseProcessor>)
en Microsoft.VisualStudio.Text.Utilities.WpfMouseProcessor.UIElement_MouseLeftButtonDown(System.Object, System.Windows.Input.MouseButtonEventArgs)
en System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object)
en System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
en System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
en System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
en System.Windows.UIElement.ReRaiseEventAs(System.Windows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent)
en System.Windows.UIElement.OnMouseDownThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
en System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object)
en System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
en System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
en System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
en System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
en System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs)
en System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs, Boolean)
en System.Windows.Input.InputManager.ProcessStagingArea()
en System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)
en System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport)
en System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32)
en System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)
en System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
en MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
en MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
en System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
en System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
en System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
en MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

This will keep @patriksvensson really happy 😄

@PradeepLoganathan commented on Wed Oct 25 2017

What You Are Seeing?

Cake extension is causing VS 2017 15.4.1 to crash constantly. It is replicable easily.

What is Expected?

Cake extension should not crash.

What version of Cake are you using?

Cake for Visual Studio 0.2.0.0

Are you running on a 32 or 64 bit system?

I am running a 64 bit system.

What environment are you running on? Windows? Linux? Mac?

Windows

Are you running on a CI Server? If so, which one?

None yet.

How Did You Get This To Happen? (Steps to Reproduce)

After installing Cake for visual studio, I created a powershell bootstrapper and a cake.config file. I created a new build.cake file without any code. It crashes once this file is opened. I opened the file in notepad and it is empty.

Output Log

I do not have any output log for the issue. Trying to check if VS2017 has a log.

@SIkebe commented on Fri Oct 27 2017

There is a repository of Cake extension for Visual Studio.
https://github.com/cake-build/cake-vs

You should probably raise an issue there.

@PradeepLoganathan commented on Fri Oct 27 2017

Will do thanks !!

When you press enter, the cursor should be positioned at the same indentation level as the previous line.

Currently the cursor starts back at the first column, making typing this quite tedious:

        WiXHeat(
            stagingDir,
            projectDir + File("Files.wxs"),
            WiXHarvestType.Dir,
            new HeatSettings
            {
                ComponentGroupName = "name",
                SuppressRootDirectory = true,
                SuppressCom = true,
                SuppressRegistry = true,
                SuppressUniqueIds = true,
                AutogeneratedGuid = true,
                Template = WiXTemplateType.Fragment
            });

I'm experiencing some strange behaviors, it seems CAKE perform differently when launched via PS Bootstrapper or via VS Task Runner (using the cake-vs extension).

• Sometimes it uses an old version of the roselyn compiler (no c#6) and it won't compile the script because I use string interpolation

Error: Roslyn.Compilers.CompilationErrorException: C:/_Sources/_TFVC/CREApp/Main/src/Libraries/Libraries.cake(44,22): error CS1525: Invalid expression term ''
Process terminated with code 1.

I guessed the proble is related to the version of the compiler (and the c# language def, of course) because at the position there is this string interpolation:

	var versionSuffix = $"alpha.{versionSuffix_day}.{versionSuffix_sec}";`

• Sometimes it gives error about cake assemblies like this one:

Error: Microsoft.CodeAnalysis.Scripting.CompilationErrorException: C:/_Sources/_TFVC/CREApp/Main/src/Master.cake(158,3): error CS0117: 'OpenCoverSettings' does not contain a definition for 'TargetDirectory'
Process terminated with code 1.

Anyway, the strange part is that these problems occur ONLY using the cake-vs extension and never using the PS Bootstrapper (or the cake directly via command line).
Furthermore, during some sunny day, also using the cake-vs extension it works fine, with no reason (apparently)

My build.cake it a very simple one, just a few line more than a "Hello World".
I also double checked the file encoding, it's ok.

And, I repeat, using the PS bootstrapper everything work as expected, all the times.

I'm sorry I'm so vague but I'm no more on PC (writing on mobile) and I'll be disco for a couple of weeks.

Hope someone else matched this issue and found a workaround.

This will also involve updating xUnit.NET dependencies in testing template since Cake.Testing also now depends on beta xUnit packages.

We should allow dragging-and-dropping supported files directly into scripts.

My initial view of this should be:

• Support dropping .cake files and automatically #load them
• Support dropping .dll files and automatically #r them
• Leave existing behaviour unchanged (i.e. support dropping solution items as a file path)

This should leave the major use case of referencing per-project files supported, while adding the #load and #r behaviour.

Now that we have an SSL certificate on the website

I guess just a random project with verbosity set to Diagnostic will render enough output to make the task runner explorer unresponsive and unable to cancel the execution.

This looks like a great tool. Any chance of a version for Visual Studio for Mac, in the near future?

I received a VS2017 update Friday and it has caused the task runner explorer to fail to load any cake tasks. I setup a quick sample project to make sure the issue wasn't due to pre-existing artifacts. Same issue with the new project, although, as you see in the screenshot, that build.cake is displayed - minus its tasks. In all existing VS2017 csproj that use cake and build.cake the build.cake root node element is not even shown in the Task Runner Explorer.

Tracking issue for updating the .NET Framework target to 4.6 (shipped with 2015, our minimum supported version) and updating VSSDK dependencies to complement

I use the -experimental flag to enable C# 6 features. Apparently the extension doesn't provide a way to pass this flag to cake.exe, so my Cake tasks fail to compile.

When in a .cake file, hitting tab does not insert spaces, even though this is how my C# text editor is configured. I can't seem to find any way to configure the cake extension independently.

I've run the bootstrapper. And those tasks are the only ones from my file that appear. I downloaded the example repo and all it shows is "Build" "Clean" and "Default" even though there is also "Restore-Nuget-Packages" and "Run-Unit-Tests." Am I missing something or did I misunderstand how it works?

What You Are Seeing?

Im seeing this:

it can't find any cake addins but thay are downloaded and getting installed, this goes for all addins.
if i manually copy the dll file from addins folder to cake.exe folder it works.

im using a custom configuration that looks like this (cake.config):

; The configuration file for Cake.

[Paths]
Tools=./../.tools
Addins=./../.tools/Addins
Modules=./../.tools/Modules

What is Expected?

That cake can load all addins and possible tools if this also affects it while im debugging.

What version of Cake are you using?

0.19.4.0

Are you running on a 32 or 64 bit system?

64

What environment are you running on? Windows? Linux? Mac?

Windows

Are you running on a CI Server? If so, which one?

No

How Did You Get This To Happen? (Steps to Reproduce)

Im using -Experimental and -Debug flags with -Verbosity diagnostic
also tested with -Mono

Output Log

Runing: D:\Workspaces\BlueLeet\BlueLeet.UCodeFirst\Build\build.cake[0]
Preparing to run build script...
Running build script...
Module directory does not exist.
Performing debug...
Attach debugger to process 39348 to continue
Debugger attached
Analyzing build script...
Analyzing D:/Workspaces/BlueLeet/BlueLeet.UCodeFirst/Build/build.cake...
Package BlueLeet.Build has already been installed.
Analyzing D:/Workspaces/BlueLeet/BlueLeet.UCodeFirst/.tools/BlueLeet.Build/content/base.cake...
Processing build script...
Installing tools...
Package docfx.msbuild has already been installed.
Package xunit.runner.console has already been installed.
Package GitVersion.CommandLine has already been installed.
Package Cake.CoreCLR has already been installed.
Installing addins...
Package NuGet.Core has already been installed.
The addin NuGet.Core will reference NuGet.Core.dll.
Package Cake.ExtendedNuGet has already been installed.
The addin Cake.ExtendedNuGet will reference Cake.ExtendedNuGet.dll.
Package Cake.Powershell has already been installed.
The addin Cake.Powershell will reference Cake.Powershell.dll.
The addin Cake.Powershell will reference System.Management.Automation.dll.
Package Cake.Git has already been installed.
The addin Cake.Git will reference Cake.Git.dll.
The addin Cake.Git will reference LibGit2Sharp.dll.
Package RestSharp has already been installed.
The addin RestSharp will reference RestSharp.dll.
Package Cake.Json has already been installed.
The addin Cake.Json will reference Cake.Json.dll.
The addin Cake.Json will reference Newtonsoft.Json.dll.
Package Cake.DocFx has already been installed.
The addin Cake.DocFx will reference Cake.DocFx.dll.
Package BlueLeet.Build has already been installed.
The addin BlueLeet.Build will reference BlueLeet.Build.dll.
Creating script session...
Using prerelease build of Roslyn.
Adding reference to Microsoft.CSharp.dll...
Adding reference to System.dll...
Adding reference to mscorlib.dll...
Adding reference to System.Core.dll...
Could not load D:\Workspaces\BlueLeet\BlueLeet.UCodeFirst\.tools\Addins\Cake.ExtendedNuGet\lib\net45\Cake.ExtendedNuGet.dll (missing NuGet.Core, Version=2.14.0.832, Culture=neutral, PublicKeyToken=31bf3856ad364e35))
Adding reference to mscorlib.dll...
Adding reference to System.Core.dll...
Adding reference to Cake.Core.dll...
Adding reference to Cake.Common.dll...
Adding reference to Cake.exe...
Adding reference to System.dll...
Adding reference to System.Xml.dll...
Adding reference to System.Xml.Linq.dll...
Adding reference to System.Data.dll...
Adding reference to NuGet.Core.dll...
Adding reference to Cake.ExtendedNuGet.dll...
Adding reference to Cake.Powershell.dll...
Adding reference to System.Management.Automation.dll...
Adding reference to Cake.Git.dll...
Adding reference to LibGit2Sharp.dll...
Adding reference to RestSharp.dll...
Adding reference to Cake.Json.dll...
Adding reference to Newtonsoft.Json.dll...
Adding reference to Cake.DocFx.dll...
Adding reference to BlueLeet.Build.dll...
Importing namespace BlueLeet.Build.Extensions...
Importing namespace Cake.Common...
Importing namespace Cake.Common.Build...
Importing namespace Cake.Common.Build.AppVeyor...
Importing namespace Cake.Common.Build.AppVeyor.Data...
Importing namespace Cake.Common.Build.Bamboo...
Importing namespace Cake.Common.Build.Bamboo.Data...
Importing namespace Cake.Common.Build.BitbucketPipelines...
Importing namespace Cake.Common.Build.BitbucketPipelines.Data...
Importing namespace Cake.Common.Build.Bitrise...
Importing namespace Cake.Common.Build.Bitrise.Data...
Importing namespace Cake.Common.Build.ContinuaCI...
Importing namespace Cake.Common.Build.ContinuaCI.Data...
Importing namespace Cake.Common.Build.GitLabCI...
Importing namespace Cake.Common.Build.GitLabCI.Data...
Importing namespace Cake.Common.Build.GoCD...
Importing namespace Cake.Common.Build.GoCD.Data...
Importing namespace Cake.Common.Build.Jenkins...
Importing namespace Cake.Common.Build.Jenkins.Data...
Importing namespace Cake.Common.Build.MyGet...
Importing namespace Cake.Common.Build.TeamCity...
Importing namespace Cake.Common.Build.TFBuild...
Importing namespace Cake.Common.Build.TFBuild.Data...
Importing namespace Cake.Common.Build.TravisCI...
Importing namespace Cake.Common.Build.TravisCI.Data...
Importing namespace Cake.Common.Diagnostics...
Importing namespace Cake.Common.IO...
Importing namespace Cake.Common.IO.Paths...
Importing namespace Cake.Common.Net...
Importing namespace Cake.Common.Security...
Importing namespace Cake.Common.Solution...
Importing namespace Cake.Common.Solution.Project...
Importing namespace Cake.Common.Solution.Project.Properties...
Importing namespace Cake.Common.Solution.Project.XmlDoc...
Importing namespace Cake.Common.Text...
Importing namespace Cake.Common.Tools...
Importing namespace Cake.Common.Tools.Cake...
Importing namespace Cake.Common.Tools.Chocolatey...
Importing namespace Cake.Common.Tools.Chocolatey.ApiKey...
Importing namespace Cake.Common.Tools.Chocolatey.Config...
Importing namespace Cake.Common.Tools.Chocolatey.Features...
Importing namespace Cake.Common.Tools.Chocolatey.Install...
Importing namespace Cake.Common.Tools.Chocolatey.New...
Importing namespace Cake.Common.Tools.Chocolatey.Pack...
Importing namespace Cake.Common.Tools.Chocolatey.Pin...
Importing namespace Cake.Common.Tools.Chocolatey.Push...
Importing namespace Cake.Common.Tools.Chocolatey.Sources...
Importing namespace Cake.Common.Tools.Chocolatey.Uninstall...
Importing namespace Cake.Common.Tools.Chocolatey.Upgrade...
Importing namespace Cake.Common.Tools.DotCover...
Importing namespace Cake.Common.Tools.DotCover.Analyse...
Importing namespace Cake.Common.Tools.DotCover.Cover...
Importing namespace Cake.Common.Tools.DotCover.Merge...
Importing namespace Cake.Common.Tools.DotCover.Report...
Importing namespace Cake.Common.Tools.DotNetCore...
Importing namespace Cake.Common.Tools.DotNetCore.Build...
Importing namespace Cake.Common.Tools.DotNetCore.Execute...
Importing namespace Cake.Common.Tools.DotNetCore.Pack...
Importing namespace Cake.Common.Tools.DotNetCore.Publish...
Importing namespace Cake.Common.Tools.DotNetCore.Restore...
Importing namespace Cake.Common.Tools.DotNetCore.Run...
Importing namespace Cake.Common.Tools.DotNetCore.Test...
Importing namespace Cake.Common.Tools.DupFinder...
Importing namespace Cake.Common.Tools.Fixie...
Importing namespace Cake.Common.Tools.GitLink...
Importing namespace Cake.Common.Tools.GitReleaseManager...
Importing namespace Cake.Common.Tools.GitReleaseManager.AddAssets...
Importing namespace Cake.Common.Tools.GitReleaseManager.Close...
Importing namespace Cake.Common.Tools.GitReleaseManager.Create...
Importing namespace Cake.Common.Tools.GitReleaseManager.Export...
Importing namespace Cake.Common.Tools.GitReleaseManager.Publish...
Importing namespace Cake.Common.Tools.GitReleaseNotes...
Importing namespace Cake.Common.Tools.GitVersion...
Importing namespace Cake.Common.Tools.ILMerge...
Importing namespace Cake.Common.Tools.ILRepack...
Importing namespace Cake.Common.Tools.InnoSetup...
Importing namespace Cake.Common.Tools.InspectCode...
Importing namespace Cake.Common.Tools.MSBuild...
Importing namespace Cake.Common.Tools.MSTest...
Importing namespace Cake.Common.Tools.NSIS...
Importing namespace Cake.Common.Tools.NuGet...
Importing namespace Cake.Common.Tools.NuGet.Add...
Importing namespace Cake.Common.Tools.NuGet.Init...
Importing namespace Cake.Common.Tools.NuGet.Install...
Importing namespace Cake.Common.Tools.NuGet.Pack...
Importing namespace Cake.Common.Tools.NuGet.Push...
Importing namespace Cake.Common.Tools.NuGet.Restore...
Importing namespace Cake.Common.Tools.NuGet.SetApiKey...
Importing namespace Cake.Common.Tools.NuGet.SetProxy...
Importing namespace Cake.Common.Tools.NuGet.Sources...
Importing namespace Cake.Common.Tools.NuGet.Update...
Importing namespace Cake.Common.Tools.NUnit...
Importing namespace Cake.Common.Tools.OctopusDeploy...
Importing namespace Cake.Common.Tools.OpenCover...
Importing namespace Cake.Common.Tools.ReportGenerator...
Importing namespace Cake.Common.Tools.ReportUnit...
Importing namespace Cake.Common.Tools.Roundhouse...
Importing namespace Cake.Common.Tools.SignTool...
Importing namespace Cake.Common.Tools.SpecFlow...
Importing namespace Cake.Common.Tools.SpecFlow.StepDefinitionReport...
Importing namespace Cake.Common.Tools.SpecFlow.TestExecutionReport...
Importing namespace Cake.Common.Tools.TextTransform...
Importing namespace Cake.Common.Tools.WiX...
Importing namespace Cake.Common.Tools.WiX.Heat...
Importing namespace Cake.Common.Tools.VSTest...
Importing namespace Cake.Common.Tools.VSWhere...
Importing namespace Cake.Common.Tools.VSWhere.All...
Importing namespace Cake.Common.Tools.VSWhere.Latest...
Importing namespace Cake.Common.Tools.VSWhere.Legacy...
Importing namespace Cake.Common.Tools.VSWhere.Product...
Importing namespace Cake.Common.Tools.XBuild...
Importing namespace Cake.Common.Tools.XUnit...
Importing namespace Cake.Common.Xml...
Importing namespace Cake.Core...
Importing namespace Cake.Core.Diagnostics...
Importing namespace Cake.Core.IO...
Importing namespace Cake.Core.Scripting...
Importing namespace Cake.DocFx...
Importing namespace Cake.DocFx.Build...
Importing namespace Cake.DocFx.Metadata...
Importing namespace Cake.ExtendedNuGet...
Importing namespace Cake.Git...
Importing namespace Cake.Json...
Importing namespace Cake.Powershell...
Importing namespace Newtonsoft.Json.Linq...
Importing namespace NuGet...
Importing namespace RestSharp...
Importing namespace RestSharp.Authenticators...
Importing namespace System...
Importing namespace System.Collections...
Importing namespace System.Collections.Generic...
Importing namespace System.Diagnostics...
Importing namespace System.IO...
Importing namespace System.Linq...
Importing namespace System.Management.Automation...
Importing namespace System.Reflection...
Importing namespace System.Text...
Importing namespace System.Threading.Tasks...
Compiling build script for debugging...
Compilation successful
Error: System.Reflection.TargetInvocationException: Ett undantagsfel har inträffat i målet för en aktivering. ---> System.IO.FileNotFoundException: Det går inte att läsa in filen eller sammansättningen Cake.Git, Version=0.14.0.0, Culture=neutral, PublicKeyToken=null eller ett av dess beroenden. Det går inte att hitta filen.
   vid Submission#0.GitFindRootFromPath(DirectoryPath path)
   vid Submission#0..ctor(Object[] submissionArray, Object& submissionResult) i D:\Workspaces\BlueLeet\BlueLeet.UCodeFirst\.tools\BlueLeet.Build\content\base.cake:rad 102
   vid Submission#0.<Factory>(Object[] submissionArray)
   --- Slut på stackspårning för interna undantag ---
   vid System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   vid System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   vid System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   vid System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
   vid Cake.Scripting.Roslyn.Nightly.DebugRoslynNightlyScriptSession.Execute(Script script)
   vid Cake.Core.Scripting.ScriptRunner.Run(IScriptHost host, FilePath scriptPath, IDictionary`2 arguments)
   vid Cake.Commands.DebugCommand.Execute(CakeOptions options)
   vid Cake.CakeApplication.Run(CakeOptions options)
   vid Cake.Program.Main()
Press Enter to continue...:

Since we are already in Visual Studio instance, can we skip this step: