Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Publish TSQLLint.Console as a .NET Core tool
See original GitHub issueWe’d like to use TSQLLint without the dependency on npm, and it seems well-suited to use as a .NET Core tool.
Configuring the csproj would be as simple as this commit, and then just dotnet pack .\source\TSQLLint.Console\TSQLLint.Console.csproj -c Tool and push the package up to NuGet.org. .NET Core tools are also cross-platform, so it wouldn’t require any multi-platform builds like the current build/package process.
Usage would be something like this:
dotnet tool install TSQLLint.Console
dotnet tsqllint
Let me know if you’d like a pull request to update the csproj. I could update the build and publish scripts too, but I’d need some guidance on how you want that handled.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:11 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’ve added support for
dotnet toolinstallation. Instructions here. Keep in mind this is the latest version of the tool which include async processing and some other improvements, but have not be heavily tested outside of the unit test suite.closing this as implemented in cfa67dadfc7820c5c77ea73a8b622ada8b0e5dc9