search

rychlym / dotnet-tools-outdated

A simple command line utility to find out / check, whether any of installed .NET Core global tools are outdated
MIT License
20 stars 3 forks source link

Work with .NET local tools #7

Closed menees closed 9 months ago

menees commented 9 months ago

Is there a way to make this work with .NET local tools, which were added in .NET Core 3.0?

I've tried specifying --toolPath .\.config\dotnet-tools.json to point to my solution's local tools configuration, but that doesn't work. I've also tried using the --name option to pass in each local tool name one at a time, and that doesn't work. It seems to only try to lookup tool names if they're in the global tools.

rychlym commented 9 months ago

I am sorry, but the .NET local tools aren't implemented yet. To be honest, nobody needed that yet and I was quite lazy to even read the doc about that :) From that all, it might be also confusing that –toolPath which is still for checking globally installed dotnet tools (but somehow manually moved to a custom location – really hardly to be used)

So after a little checking, I can see, it is really worth to add such a functionality. Well, I will need some time to implement and test it. (the --toolPath will be probably changed to --globalToolsPath (or --globalToolsStoreLocation)

rychlym commented 9 months ago

Hopefully a good message - the new version 0.7.0 supporting the local .NET tools is out. I needed quite a bunch of extra time to work out (probably less used) xml and json format output types and some breaking changes there (the release notes can be found at the https://www.nuget.org/packages/dotnet-tools-outdated/0.7.0)

btw. I must take back my previous comment "(but somehow manually moved to a custom location – really hardly to be used)" - that is related to a real documented scenario

menees commented 9 months ago

Thanks for the quick support! I'll try it out on Monday when I get back to the office.

menees commented 9 months ago

Thanks! This works great for me, and I really appreciate the quick resolution.

I noticed one minor change that seems like a typo. The --output option was changed to --otput in this diff.