Git Product home page Git Product logo

Comments (5)

wojciechrak avatar wojciechrak commented on May 20, 2024

I am voting for this, too. In our case, we already had a path /tools in our repository, so we put Cake in /cake/tools instead.

from cake-vs.

sbakharev avatar sbakharev commented on May 20, 2024

Hello! The problem is still in place and we're interested in this feature too.

We renamed the Cake's tools folders to ".build-tools" in build.ps1 for it to be alphabetically standing before the solution projects' folders instead of appearing somewhere in the middle.

So the script placed all tools to ./.build-tools/ and Cake itself to ./.build-tools/Cake/Cake.exe. With this setup in place Cake extension for Visual Studio cannot find Cake.exe and thus cannot show build.cake tasks in task runner explorer.

What I see using Process Monitor is that Visual Studio tries to find Cake.exe at:

  • ./tools/Cake/Cake.exe
  • ./Cake/Cake.exe
  • ./Cake.exe
  • all directories listed on PATH environment variable

So the first path it uses means that "tools" directory name is hardcoded and thus required for the extension to function properly. We definitely need an option to control this.

P.S. Modifying cake.config file to use ./.build-tools as tools path does not change anything.

from cake-vs.

agc93 avatar agc93 commented on May 20, 2024

Thanks everyone for all the feedback. I know this has been a very long time coming, but I've been revisiting a few of these long-term pain points of late and wanted to let you know what's happening.

I understand that this is frustrating behaviour but a lot of our options are either difficult to achieve in the VS environment or have other issues that we would then need to fix again.

My current intention is to at least have the extension respect the "Tools Path" from cake.config and search that path for cake.exe. We might be able to improve on that in future though, so I'll keep looking into this.

Thanks for your patience!

from cake-vs.

agc93 avatar agc93 commented on May 20, 2024

I've now added experimental support for using cake.config for this. The extension will now try to resolve cake.exe from the following locations (in this order):

  • The directory set by the Tools Path configuration value in cake.config
  • The value of the CAKE_PATHS_TOOLS environment variable (if set)
  • The ./tools/Cake and ./Cake folder (the existing behaviour)
  • Your PATH

If you're using the prerelease version of the extension, it should automatically pick up cake.exe from any of the locations above. We'll look into improving this behaviour even more going forward.

If anyone is still facing this issue, can you please try out the prerelease version and let me know if it solves your issue.

from cake-vs.

gep13 avatar gep13 commented on May 20, 2024

I believe that this now works as expected, so going to go ahead and close this out.

from cake-vs.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.