Stuck on an issue?
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.
Add ability to list .NET Framework info with `dotnet` CLI
See original GitHub issue.NET CLI has the great ability to list runtimes installed (dotnet --list-runtimes) but the process for finding the list of installed .NET Frameworks is much more cumbersome (checking registry is likely the best way, but that is cumbersome for the average user and the “verification” via the registry is different for different versions of .NET Framework). Could this be added into the .NET CLI? Something like dotnet --list-framework-runtimes?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
dotnet command - .NET CLI
The dotnet command has two functions: It provides commands for working with .NET projects. For example, dotnet build builds a project.
Read more >Select which .NET version to use
The .NET CLI must choose an SDK version for every dotnet command. It uses the latest SDK installed on the machine by default,...
Read more >dotnet list package command - .NET CLI
The 'dotnet list package' command provides a convenient option to list the package references for a project or solution.
Read more >NET default templates for dotnet new - .NET CLI
The information about dotnet new templates shipped with dotnet SDK. ... To list the built-in templates, run the dotnet new list command:.
Read more >dotnet-counters diagnostic tool - .NET CLI
Learn how to install and use the dotnet-counter CLI tool for ad-hoc health monitoring and first-level performance investigation.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Perhaps that could be a good .NET tool. As you say, the registry keys and values are documented; if someone writes such a tool, it would be easy to acquire and run through
dotnet.Oh I can avoid the CA1416 by checking OperatingSystem.IsWindows() in code, or by adding
[assembly: SupportedOSPlatform("windows")]. All right then.