EnsureNETCoreAppRuntime validation failed on 16.8 Preview 4
See original GitHub issueWhen an ASP .Net Core web project has RID <RuntimeIdentifier>win7-x64</RuntimeIdentifier>
, then project load shows the following error
Project is targeting runtime ‘win7-x64’ but did not resolve any runtime-specific packages for the ‘Microsoft.NETCore.App’ package. This runtime may not be supported by .NET Core.
and the above error is from "C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.netcore.app\2.1.0\build\netcoreapp2.1\Microsoft.NETCore.App.targets"
I notice this error happening only on 16.8 Preview 4 build. (Version 16.8.0 Preview 4.0 [30509.233.main]) and the Dependencies tree shows some warning
Repro Steps:
- Create a ASP .Net Core project and then add win7-x64 as runtime identifier.
- unload and reload the project.
Issue Analytics
- State:
- Created 3 years ago
- Comments:38 (24 by maintainers)
Top Results From Across the Web
Visual Studio 2019 version 16.8 Release Notes
Fixed an error where Visual Studio may become unresponsive for several seconds while checking for updates. DeploymentAppRecipe.exe tool now supports running ...
Read more >Visual Studio 2019 Update version 16.8.6 is missing ...
A fix for this issue has been released! Install the most recent release from https://visualstudio.microsoft.com/downloads/.
Read more >Visual Studio 2019 v16.8 Ships with Git Turned On by Default
This is done via a new XAML Binding failure indicator icon that will show a red indicator if at least one binding failure...
Read more >App manifest validation error after update to visual studio ...
After update to visual studio 2019 16.8.0 I get the error while project build. (I use lottie animation in my app. I did...
Read more >Visual Studio 2019 Community 16.11.28.0
Overview. Free, full-featured and extensible tool for students, open-source and individual developers. To find out what's new or to see the known issues, ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This will be fixed in .NET SDK 5.0.101, which I believe will go out together with VS 16.8.3. So no need for a binlog or anything at this point.
I’m seeing this issue since upgrading to VS 16.8.2 for all projects on
netcoreapp3.1
. Currently not seeing any runtime issues; workaround provided above does hide the error - I would like to remove<EnsureNETCoreAppRuntime>false</EnsureNETCoreAppRuntime>
sooner rather than later