Dotnet says "It was not possible to find any compatible framework version"
See original GitHub issueSteps to reproduce
Install VS2017. Create a command-line project. Compile, move to ARM Linux, launch using dotnet xxx.dll
Expected behavior
Should run
Actual behavior
It was not possible to find any compatible framework version The specified framework ‘Microsoft.NETCore.App’, version ‘2.0.0’ was not found.
- Check application dependencies and target a framework version installed at: /
- Alternatively, install the framework version ‘2.0.0’.
Environment data
dotnet --info
output:
Microsoft .NET Core Shared Framework Host
Version : 2.0.1-servicing-25615-03 Build : 715604ad09b5fda1445436977e7032e6d29aa8f5
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
It was not possible to find any compatible framework ...
It was not possible to find any compatible framework version. The specified framework 'Microsoft.NETCore.App', version '2.2.0' was not found.
Read more >Not possible to find any compatible framework version ...
I have a fix for this issue out with a new 3.1.5 and 5.0.2 package out. Use dotnet tool update dotnet-aspnet-codegenerator -g --version...
Read more >Fix : It was not possible to find any compatible framework version
App', version '2.0.0' was not found. - The following frameworks were found : 3.1.3 at [C:\Program Files\ dotnet \shared\Microsoft.NETCore.
Read more >It was not possible to find any compatible framework version
It was not possible to find any compatible framework version The framework 'Microsoft.NETCore.App', version '2.1.0' was not found. The following frameworks were ...
Read more >It was not possible to find any compatible framework version
I am seeing the same problem when using Microsoft.NET.Test.Sdk 16.4.0 or 16.3.0. If I go back to 16.2.0, it works again. I have ......
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 Free
Top 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
Alright, this is such BS! Why the H can’t Microsoft get a rollout right. Roll it out right or roll it back!
Anyways - here’s what I had to do to fix this garbage.
1: I had to uninstall all of the .net Core items in the “Programs” section of the control panel. 2: I went to https://github.com/dotnet/core/blob/master/release-notes/download-archive.md and got “2.0 sdk and 2.0 runtime” and installed that. 3: I ran my migration and got the same error as above but the version it was complaining about was “2.0” - SO, I added “<RuntimeFrameworkVersion>2.0.0</RuntimeFrameworkVersion>” to my project and the stupid thing worked.
I hope this works for any one of you - I worked hard enough on this project just to have a “Botched Rollout” reduce it to smoke!
Oh, and another thing - my “data” project borked because the file “<prjName>.EntityFrameworkCore.targets” was not cleared before it was overwritten. I had 2 ending nodes at the bottom of the file. I hope they fix THAT too.
(Sorry all, I wasted WAY too much time on this SNAFU and it didn’t have to happen.)
For anyone stumbling on this today, I had this issue on build.
It was complaining of missing 2.2.5. It listed the installed frameworks which was indeed missing 2.2.5. So I installed the SDK which is 2.2.107 according to its MSI filename and that includes 2.2.5 of the runtime and it builds and no errors in the test output now.
I don’t get the version numbers.
I assume Testhost is a process and it wants to run on 2.2.5. Not sure which package the Testhost comes from but I had these referenced. I guess maybe I updated to 2.2.5 package reference but didn’t install the SDK (didn’t know I had to?)