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.
.NET Core SDK 2.1.2
See original GitHub issueVisual Studio 2017 15.5 has been released, and along with the .NET Command Line Tools (2.1.2) , however what I want to known where can we download the standalone .NET Command Line Tools (2.1.2) ?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:9
- Comments:13 (4 by maintainers)
Top Results From Across the Web
Download .NET Core 2.1 (Linux, macOS, and Windows)
The software development kit (SDK) includes everything you need to build and run .NET applications, using command-line tools and any editor (like Visual...
Read more >NET Core 2.1.2
Released on 2018-07-10; Runtime 2.1.2; SDK 2.1.302; ASP.NET Runtime 2.1.2 ... NET Core 2.1.2 is available for download and usage in your environment....
Read more >How do we download SDK 2.1.2? · Issue #1131 · dotnet/core
Visual Studio 2017 15.5 came with dotnet 2.1.2. How do we download that version on other systems such as Mac? There is no...
Read more >Exploring the .NET Core 2.1 Docker files (updated): dotnet ...
In this post, I look at the various Docker base images available for .NET Core 2.1 development, how they differ, and when you...
Read more >Cannot build projects using .NET Core 2.1.2's MSBuild
NET Core SDK's one (usually C:\Program Files\dotnet\sdk\2.1.2\MSBuild.dll ), builds systematically fail with the following error:.
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
I still don’t see how this ‘advantage’ makes up for the complexity/confusion when talking about versioning, I see that only as trying to be puristic about semantic versioning. I always need to draw a table when doing various investigations where different versions of SDK/Runtime contain certain bugs. Taking that aside, Microsoft needs to ensure that it is clear what is in a package. The download page is absolutely not helpful in showing me what is in the package. I have to go to the GitHub releases and the only additonal information is the Runtime version. The re-design of the website has made it so much worse. What developers want is a nice table in a central location containing the details of what is in each package and not having to bring all that information together by going to various release noes of sdk, cli, corefx, etc.
@markusschaber great, thank you for explaining me. Cannot wait for NET Core 2.1, exciting stuff.