3 ms·
I think everyone needs to do `dotnet tool install -g dotnet-script` before running them. This is the most annoying part where .NET 10 announcement would be real
by smarx007 1y ago
I think everyone needs to do `dotnet tool install -g dotnet-script` before running them. This is the most annoying part where .NET 10 announcement would be really appreciated.
But then each script has an individual list of dependencies so there should be no need for further scoping like in npm (as in, the compilation of the script is always scoped behind the scenes). In this regard, both should be similar to https://docs.astral.sh/uv/guides/scripts/#declaring-script-dependencies https://docs.astral.sh/uv/guides/scripts/#declaring-script-d... which I absolutely love.
- bladeee 1y agoYou can use project-scoped tool manifests. Then you can call dotnet tool restore to load all tools specified in the manifest. https://learn.microsoft.com/en-us/dotnet/core/tools/global-tools https://learn.microsoft.com/en-us/dotnet/core/tools/global-t...
- smarx007 1y agoTIL, thank you!
- andix 1y agoSure, but I think you still need to provide the full path of the script. If you're inside a source folder very deep it will lead to something like: dotnet script ../../../../../scrips/scaffold-something.cs With npm run it works from any subdirectory: npm run scaffold-something