-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
.net core SDK 2.1.4 generates projects that can't build #9053
Comments
It looks like you have a |
Is this a one-off issue where 2.2.0 was renamed to 2.1.300? If not, I'm trying to figure out how did my system end up in this configuration:
|
unfortunately, all 2.2.0 preview versions have to be uninstalled because the version downgrade is a breaking change. this affects everyone who downloaded and installed a CI build. I'm not sure but I don't think any preview VS installed a 2.2.0-preview CLI version.. SDK installs are side-by-side so it will always choose the latest one, even preview versions, unless there is a Personally I don't know why it stopped working. maybe the templates emitted specific versions and not relied on the bundled version properties or your local nuget cache / fallback folder have been deleted. |
I just noticed that building [Roslyn[(http://github.com/dotnet/roslyn) makes you install 2.2.0 SDK - I guess that's how I ended up with this version:
Should Roslyn update their requirement to |
@dasMulli is correct in his comments above! Thanks for getting to this issue. @AmadeusW we do not have the 2.2.0 not 2.1.300 previews going out with any version of VS. So, the Roslyn build is your asnwer above as to how you got that version of the SDK in your system. I can't answer as to when Roslyn will update their SDK. cc @jaredpar for that. Also, if fails to restore because while working with the preview, we recommend adding nuget feeds to the created projects pointing to locations in myget where the preview nuget packages can be found. We have a bug tracking updating our preview documentation to document which feeds to add. Hope this helps. If there is still anything wrong, just comment and we can help/re-activate this issue. |
The hard link points to a specific version of .NET SDK installer which causes user's machine to end up in a bad state: see [dotnet/cli/issues/8531] and [this](dotnet/designs#29 (comment)) This PR changes the link to the general download page, where user will get a correct and supported version of the SDK
I've been unsuccessfully trying to create a new project. The newly created project fails to restore and build. This happens both through VS 15.5.6 and through the command line. For simplicity, let's focus on the command line:
BTW, I repaired, uninstalled and installed both
dotnet-sdk-2.1.4-win-x64.exe
anddotnet-sdk-2.1.4-win-gs-x64.exe
, all to no help.It looks like the generated .csproj has incorrect versions:
Steps to reproduce
dotnet new console
Expected behavior
New project is created, restored and ready to build
Actual behavior
Environment data
dotnet --info
output:Workaround
The project restores, builds and runs if I follow the warning and set both
RuntimeFrameworkVersion
andNETStandardImplicitPackageVersion
to2.0.5
.The text was updated successfully, but these errors were encountered: