The specified framework version '2.0' could not be parsed...
See original GitHub issueThe global.json with 2.1.4 does not help when using dotnet ef commands in a classlib. You still have to manually add the RuntimeFrameworkVersion to the CSPROJ file on all projects in the solution. If you only add to one NUGET wants to consolidate because some projects are using 2.0.0 and only the ones specified with RuntimeFrameworkVersion use 2.0.5. I only have SDK 2.1.4 installed why does it just not use Runtime 2.0.5 by default?
Why do I have to specify this in ever CSPROJ, what good is the global.json then?
<RuntimeFrameworkVersion>2.0.5</RuntimeFrameworkVersion>
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
The specified framework version '2.0' could not be parsed - ...
I finally found the answer after going through some issues on GitHub. It looks like it is an issue with dotnet CLI itself,...
Read more >The specified framework version '2.1' could not be parsed ...
Just now seeing this error when trying to run update-database from PM console. I have the latest SDK installed. I've tried repairing VS2017 ......
Read more >The specified framework version '2.0' could not be parsed
After upgrading to Visual Studio 15.4.4 I started receiving the following error from the dotnet cli: The specified framework version '2.0' ...
Read more >[NETCore][Issue]The specified framework version '2.0' ...
When using dotnet ef migration, the following occurred: The specified framework version '2.0' could not be parsed. The specified framework 'Microsoft.
Read more >C# – Cannot use 'dotnet ef…' – The specified framework version ' ...
The specified framework version '2.0' could not be parsed The specified framework 'Microsoft.NETCore.App', version '2.0' was not found.
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
The fix will be in EF Core 2.0.2. We’re hoping it finally ships this month. 🤞 You can use the patch preview feed to try it out now.
Yep. Ok, given that you have a workaround and that the bug is being fixed in EF, I am going to close this issue.
@cgountanis Glad to see you are unblocked.