.NET Core 3.1 Known Issues
This document lists known issues for .NET Core 3.1 Preview 1 and beyond releases which may be encountered during usage.
Visual Studio 16.4 Preview 2 may uninstall .NET Core 3.0 when installed with the .NET Core 3.1 SDK. We recommend you re-install or repair the .NET Core 3.0 SDK if this happens.
.NET Core 3.1.1 SDK (3.1.101 SDK)
ASP.NET Core runtime issue on systems other than Windows x-64 (aspnet/Announcements/401)
When using the 3.1.101 SDK to build an application and then deploying to a runtime environment other than 64-bit Windows, people may see a runtime exception failing to load certain dependencies. This can be worked around by adding a
PackageReferencedirectly to the package that fails to load.
More information can be found in the referenced issue.
.NET Core 3.1.0 SDK (3.1.100 SDK)
ASP.NET Core workloads may use older dependencies for libraries that are present in the Targeting Pack (aspnet/Announcements/398)
When using the 3.1.100 SDK, people who are building ASP.NET Core workloads may encounter an error where lower versioned dependencies that are referenced by the application aren't removed correctly. The most common occurrence of this issue is when hosting with IIS, where there is mismatch between two libraries causing a
Workarounds and more information are in the referenced issue.
.NET Core installation on macOS Catalina (10.15)
macOS Catalina introduced new security features which affect the .NET Core installers. If you run the installer after downloading using a web browser, a warning dialog will open stating the package
"...can't be opened because Apple cannot check it for malicious software.", and the installation will be stopped.
To override this behavior, go to Settings : Security & Privacy and choose "Open Anyway" next to the dotnet installer text.
We are working to update our installers for the new Catalina requirements. These will be released during an upcoming monthly update.
.NET Core 3.1 SDK, all releases
- [RESOLVED] The 3.1.0 Hosting Bundle for Windows installs a .NET Core Runtime incorrectly branded "3.1.0 Preview 3".
This is a cosmetic bug: the hosting bundle is expected to function normally.
This is fixed with 3.1.1. More information at dotnet/core#3962.
The Hosting Bundle briefly shows that it is installing "Microsoft .NET Core Runtime - 3.1.0 Preview 3". That string is also visible in Add/Remove Programs after the install completes. This is not the old November 2019 3.1.0 Preview 3 Runtime. The Hosting Bundle is installing a more recent build of 3.1.0 that has incorrect branding.
- [RESOLVED] If the 3.1.0 SDK and Hosting Bundle were previously installed on Windows, installing the 3.1.0 .NET Core Runtime directly may remove important files such as
To fix this, repair the .NET Core Runtime installation. (Execute the installer again and click Repair, or find the .NET Core Runtime 3.1.0 installation in Add/Remove Programs, select Modify, then click Repair.)
Missing this file can cause errors like the following, for example when running
A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.0'.
- [RESOLVED] Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation package is missing MSBuild targets to correctly enable runtime compilation
Due to an package authoring error, the
Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation is missing build targets that are required to for runtime compilation to work.
Users of this package will see errors along the lines of
"System.InvalidOperationException: Cannot find reference assembly '...' file for package '...'*
To resolve this issue, add the following contents to the your project file:
<PropertyGroup> <PreserveCompilationContext>true</PreserveCompilationContext> <PreserveCompilationReferences>true</PreserveCompilationReferences> <GenerateRazorHostingAssemblyInfo>true</GenerateRazorHostingAssemblyInfo> <RazorUpToDateReloadFileTypes>$(RazorUpToDateReloadFileTypes.Replace('.cshtml', ''))</RazorUpToDateReloadFileTypes> <AddCshtmlFilesToDotNetWatchList>false</AddCshtmlFilesToDotNetWatchList> </PropertyGroup>
This issue has been resolved in 3.1 Preview 2.