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.
End of life for .NET Core 1.0 / 1.1 (project.json)
See original GitHub issue.NET Core 1.0/1.1 reached end of life and went out of support on 27 June 2019.
Support for project.json should be removed.
We would like to remove it from OmniSharp
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
.NET and .NET Core official support policy - Microsoft
NET and .NET Core release lifecycle. Supported versions. The following table tracks release and end of support dates for .NET and .NET Core...
Read more >Microsoft .NET - endoflife.date
Release Released Support Status
7.0 1 month and 2 weeks ago. (08 Nov 2022) Ends in 1 year and 4 months. (14 May...
6.0 (...
Read more >R.I.P project.json - Out with the new, in with the old
An early look at the new csproj project format which replaces project.json in Visual Studio 2017 for .NET Core projects.
Read more >NET Core 1.0.4 and 1.1.1 · Issue #532 · dotnet/core - GitHub
When can we expect 1.1.1 to be pushed to the repositories? I upgraded my project to 1.1.1 but Ubuntu 10.4 is still on...
Read more >Setting the version number for .NET Core projects - CSPROJ
NET Core at the time of writing (1.1) and VS2017, .NET Core has switched from JSON based project files to CSPROJ files. So...
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
This is done.
Could you guys look at the telemetry to determine how much project.json is used?
An alternative approach would be to extract it from OmniSharp and make it a plugin (ala Razor) that users can opt into.