You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 11, 2020. It is now read-only.
We should add guidance to help users when a newer .NET CLI is on the path that does not support project.json. I expect that project.json and I will be with us for a long while as not everyone will upgrade overnight.
Clearly, this would require servicing VS 2015 tooling which we likely wouldn't do just for this issue. However, if we do choose to service VS 2015 tooling, we should consider doing this at the same time.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Moving from https://github.com/dotnet/cli/issues/5375 on behalf of @DustinCampbell
We should add guidance to help users when a newer .NET CLI is on the path that does not support project.json. I expect that project.json and I will be with us for a long while as not everyone will upgrade overnight.
Clearly, this would require servicing VS 2015 tooling which we likely wouldn't do just for this issue. However, if we do choose to service VS 2015 tooling, we should consider doing this at the same time.
The text was updated successfully, but these errors were encountered: