-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 January Update - 2.1.7 and 2.2.1 #2210
Comments
The links to the CVEs in the release notes of 2.2.1 are broken. Fix: #2214 |
@johnkors thanks for the fixes! |
When can we expect 2.2.1 packages to be available on NuGet? I can see 2.1.x packages had been updated to 2.1.7, but newest 2.2.x packages are still at version 2.2.0. |
@Ryszka - I just checked nuget.org and see the appropriate versions available for affected packages detailed in the release notes. Is there a specific package you're not seeing? |
@leecow I have checked again and they're in fact there. Must have been some caching issue or I just missed it before. |
I just installed dotnet-sdk-2.2.103-win-x64.exe. When I do a dotnet new mvc at the command line I get the error: C:\Program Files\dotnet\sdk\2.1.500\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.TargetFrameworkInference.targets(137,5): error NETSDK1045: The current .NET SDK does not support targeting .NET Core 2.2. Either target .NET Core 2.1 or lower, or use a version of the .NET SDK that supports .NET Core 2.2. When I do dotnet --version I get 2.2.103 Here is a complete output:
Help would be appreciated, Thanks. |
@murat / @bradygaster, can you have a look at @jsoques issue above? |
@jsoques You don't happen to have a global.json do you? @leecow This looks like a CLI/SDK question to me. @livarcocc any thoughts here? |
@jsoques what happens when you run dotnet --info on the project folder? |
@muratg No global.json
|
For some reason, when it restores the project it is using the 2.1.500 props/targets, as seen in the logs here:
Emphasis in |
@livarcocc Ah, now that you've mentioned it, yes I have a MSBuildSDKsPath pointing to that version. I had created it because of an issue I had with VS Code/Omnisharp. Thanks, |
I wonder if https://github.com/dotnet/core/blob/master/release-notes/2.2/2.2-known-issues.md#aspnet-core-module is fixed? Known Issues points to a non-existing file :( |
@Leon99 ANCM was deployed to Azure in late December. What's the exact issue you're having? |
@muratg I had a problem described on https://stackoverflow.com/questions/53811569/using-netcore-2-2-and-using-the-in-process-hosting-model last week, solved by switching to OutOfProcess. |
@Leon99 Ah, so you haven't deployed to Azure. Did you install the latest .NET Core SDK/runtime? ( |
I did deploy to Azure (App Service). |
@Leon99 could you please share your csproj file? |
I can't reproduce it now, InProcess seems to work fine once I put it back and re-deployed. There was nothing fancy about it when I encountered the issue, just a standard Core 2.2 API one generated by the latest VS. |
Closing this release discussion issue in favor of #2304 |
.NET Core January Update - 2.1.7 and 2.2.1
Included fixes address security issues detailed in the release notes.
Note: The 2.2 SDK was re-released on 1/16/2019 to address an issue (dotnet/source-build#942) where developers targeting the 2.1 Runtime (LTS) will not get the latest release when building self-contained applications.
.NET Core
.NET Core 2.1.7 and .NET Core SDK 2.1.503
Release Notes
Download 2.1
.NET Core 2.2.1 and .NET Core SDK 2.2.103
Release Notes
Download 2.2
Please report any issues you find with these releases, either responding to this issue, creating a new issue here or creating a new issue in one of the following repos:
.NET Support Policies
Microsoft support policies are defined in the following documents:
The text was updated successfully, but these errors were encountered: