Make the task detection independent of build.cake position about cake-vs HOT 9 CLOSED

Unfortunately, this is a limitation in Visual Studio.

VS looks for the "config file" for Task Runners (in our case, that's your build.cake file), in the project root folder, then traverses upwards to find it. Scripts in subfolders, or folders outside that "chain" won't be found, but we unfortunately can't change this.

One workaround is that, when 0.2.0 is released, the task runner will support nested Cake files (using the #load directive), so you could put a single build.cake file in \git\MyProject\build.cake (to use your example), and #load in any scripts from the BuildScripts folder, and they should still appear and be usable from the task runner.

from cake-vs.

@nnyegaard I can see the tasks showing up when I open that repo. For the tasks to be loaded, you either a) need to have run the bootstrapper at least once or b) have Cake.exe available on your PATH.

Do you have your tools/addins installed in a custom directory for that solution?

from cake-vs.

I had yet to run the bootstrapper (build.ps1), but after I did, I got the tasks.

Thanks a lot guys!

from cake-vs.

Conversation where this was discussed: https://gitter.im/Microsoft/extendvs?at=57f52e3729403a416fcb7cbe

from cake-vs.

I understand. That's sad though.
As far as I am concerned, you can close this when 0.2.0 is released

from cake-vs.

It seems that the task runner can't detect the task in the cake file even though it is in root.

I have a ASP.NET Core app with paths:
root\src
root\test
root\Api.sln
\root\build.cake

And the task runner detects the cake file, but it does not show any tasks

from cake-vs.

@nnyegaard is this a public repo that we can take a look at? If so, where is it?

Also, is that a typo in your comment? You have cake.build rather than build.cake.

from cake-vs.

Yes sorry build.cake.

I have published the repo here: https://github.com/nnyegaard/cakebuild

from cake-vs.

I have just read through the discussion here, and I believe that this issue can now be closed.

If this isn't the case, then please comment again.

from cake-vs.