3 ms·
"dotnet tool exec" is not that feature; you're thinking of https://devblogs.microsoft.com/dotnet/announcing-dotnet-run-app/ https://devblogs.microsoft.com/dotne
by electroly 1y ago
"dotnet tool exec" is not that feature; you're thinking of https://devblogs.microsoft.com/dotnet/announcing-dotnet-run-app/ https://devblogs.microsoft.com/dotnet/announcing-dotnet-run-... which they added to "dotnet run". "dotnet run my-cool-thing.cs"
"dotnet tool exec" is so you can run third party command line tools like csharpier that previously required "dotnet tool install" before you could use them. For example, in https://csharpier.com/docs/Installation https://csharpier.com/docs/Installation you can now simply do "dotnet tool exec csharpier". This is like "npx" in the JavaScript world.
- Salgat 1y agodotnet run *.cs is my favorite new feature for scripting. It has basically replaced powershell for me. It's trivial to script powerful operations now.
- SeriousM 1y agoI guess LinqPad will lose some users to this feature.
- teh_klev 1y agoThis isn't LinqPad's selling point. All that dotnet run *.cs has done is remove the need to have a project file for each "script" you write. LinqPad maybe has this feature but it's selling point is as a scratch pad to experiment with working with data and general futzing around.
- Salgat 1y agoThe .NET team said they're working on VS Code integration. LinqPad still has some unique features (mostly database related), but at least for me, VS Code + dotnet run will be sufficient for my needs. Worst case, I can just throw a breakpoint on my database IQueryable result.
- jug 1y agoAh yes, that's the one I was thinking of. Got confused by this article.