-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project.json no longer works #411
Comments
It was not a minor release, it was the first non-preview release of the SDK. The last version of the SDK that supported project.json was Preview 2. csproj is fully supported since SDK 1.0.
Sorry, that's just not going to happen. If there ever was a possibility to convince Microsoft of this, we're way past that point now. Especially considering that doing it now would actually be a breaking change in released product. Do you have any specific suggestions about how csproj could be improved? |
Well thanks for replying. I think it's a little cheeky to say that 1.0.3 was not a production release when you flagged it as a stable long term support release. Anyway. How about making .csproj support both xml and json equivalents ? |
.Net Core 1.0.3 was a stable release, but that's just the runtime, it doesn't contain the project.json tools. .Net Core SDK Preview 2, which actually let you use project.json, was not a stable release. It is kind of confusing that there is a difference between the two, but that's the way it is.
Does that mean you want JSON, but not necessarily project.json? Then you might be interested in these two issues: dotnet/msbuild#16, dotnet/msbuild#613. Though the former one was closed with:
|
Okay thanks for that |
You created a breaking change and pushed it out as minor release.
Bring back the project.json, down with the csproj
The text was updated successfully, but these errors were encountered: