The specified framework 'Microsoft.NETCore.App', version '2.0' was not found #8826

redowl3 · 2017-10-25T10:08:31Z

Not sure if this is a cli issue or VS so happy to move to another area if not correct

Steps to reproduce

Update to Visual Studio Professional Preview (v 15.5.0 Preview 2)

Try to add data migration (using IDesignTimeDbContextFactory)

dotnet ef migrations add [MigrationName]

Expected behavior

Migration created

Actual behavior

Error message

The specified framework version '2.0' could not be parsed
The specified framework 'Microsoft.NETCore.App', version '2.0' was not found.

Check application dependencies and target a framework version installed at:
\
Alternatively, install the framework version '2.0'.

Environment data

Product Information:
Version: 2.1.1-preview-007094
Commit SHA-1 hash: f657648

Runtime Environment:
OS Name: Windows
OS Version: 10.0.15063
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.1-preview-007094\

Microsoft .NET Core Shared Framework Host

Version : 2.0.0
Build : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d

The text was updated successfully, but these errors were encountered:

livarcocc · 2017-10-25T16:31:36Z

Can you share your project or a repro of this issue?

redowl3 · 2017-10-26T14:07:12Z

Hi,

Thanks for getting back to me.

The project is pretty big so not practical to share, but since updating to 15.5.0 Preview 2.0, as well as not being able to create migrations due to what looks like core versioning issues, I can no longer publish anything to Azure as the build fails although it builds fine in VS?

Whatever was changed with 15.5.0 Preview 2.0 looks to be creating a few issues.

As the issue appears to be with a project built with the previous version of the Preview, then updating to 15.5.0 Preview 2.0 I'm now unable to repro.

livarcocc · 2017-10-26T16:41:08Z

You can add a global.json pinning your SDK version to version 2.0.2 (the last release we did with VS 15.4) or 2.0.0.

Just add the global.json file to the root of your repo with contents like this:

{
  "sdk": {
    "version": "2.0.2"
  }
}

This should unblock you. But notice that your SDK will be pinned to whatever version you put there. Let us know if this unblocks you.

It would also be super helpful if you could at least find a minimal repro for this problem. Is this happening on multiple machines?
Can you tell us what are the folders you have under C:\Program Files\dotnet\shared\microsoft.netcore.app? This will tell us which runtimes you have in the box.

redowl3 · 2017-10-26T16:59:05Z

Thanks for the suggestion, I'll try that. I've only tried this on a single machine.

Folder structure below.

livarcocc · 2017-10-26T19:39:18Z

Could you share the contents of runtimeconfig.json file for your tool? And are you packaging it in your tool nupkg?

netbidev · 2017-10-27T16:52:44Z

Hello everyone. I have this problem too.

livarcocc · 2017-10-27T16:58:46Z

@netbidev any chance you have a small repro for us?

netbidev · 2017-10-28T04:33:53Z

@livarcocc here
TestDB.DBModel.zip

The command here
dotnet ef dbcontext scaffold "Server=.;Database=TestDB;Trusted_Connection=True;" Microsoft.EntityFrameworkCore.SqlServer

dls314 · 2017-10-30T16:45:54Z

@netbidev That project replicates the error for me as well

dls314 · 2017-10-30T16:57:14Z

@livarcocc The workaround of adding a global.json file specifying 2.0.2 works for me.

Does anyone know if/how the --fx-version argument could be used instead? global.json is tacky.

livarcocc · 2017-10-30T16:58:39Z

the --fx-version argument is a host argument that can be used to indicate which runtime framework to use when running an application.

Like this: dotnet --fx-version 2.0.0 <app.dll>.

dls314 · 2017-10-30T17:25:08Z

I guess that the dotnet ef command can't be used with host arguments? I've tried putting --fx-version in various places in a command like dotnet ef migrations list without success.

jeremymeng · 2017-11-09T23:17:09Z

Hit this issue in an xunit test project too. Repro:

dotnet new xunit
Upgrade to latest xunit 2.3.1, and add dotnet-xunit tool

  <ItemGroup>
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.5.0-preview-20170810-02" />
    <PackageReference Include="xunit" Version="2.3.1" />
    <PackageReference Include="xunit.runner.visualstudio" Version="2.3.1" />
    <DotNetCliToolReference Include="dotnet-xunit" Version="2.3.1" />
  </ItemGroup>

dotnet build
dotnet xunit

Actual:

Detecting target frameworks in test2.csproj...
Building for framework netcoreapp2.0...
  test2 -> e:\temp\test2\bin\Debug\netcoreapp2.0\test2.dll
Running .NET Core 2.0 tests for framework netcoreapp2.0...
The specified framework version '2.0' could not be parsed
The specified framework 'Microsoft.NETCore.App', version '2.0' was not found.
  - Check application dependencies and target a framework version installed at:
      \
  - Alternatively, install the framework version '2.0'.

Notes:
dotnet test works.
dotnet xunit --fx-version 2.0.0 works too.

Kurtbaby · 2017-11-15T20:16:17Z

I am having the same issue after upgrading to v15.4.4. The only solution I've found so far to fix the CLI tools issue it to add the RuntimeFrameworkVersion inside the property group as such:

<PropertyGroup>
   <TargetFramework>netcoreapp2.0</TargetFramework>
   <RuntimeFrameworkVersion>2.0.3</RuntimeFrameworkVersion>
</PropertyGroup>

livarcocc · 2017-11-15T21:56:10Z

I can't repro this using SDK 2.1.1-preview-007139 on a Mac or 2.1.1-preview-007165 on Windows. For those that are reproing this, is it always reproing on Windows? If so, can you make sure that you don't have two different dotnet versions installed, one x86 and one x64? And that the one being used by the tool is not being the wrong one? I mean, make sure that the right dotnet installation is coming before the other one in the path environment variable.

jeremymeng · 2017-11-15T22:58:21Z

I found that I had some preview versions of dotnet sdk installed, including 2.0.3. The latest on dot.net seems 2.0.2. After uninstalling those and only keeping 2.0.0, 2.0.2, and 2.1.1-preview-007118, the issue no longer reproduces for me

haidelber · 2017-11-16T08:56:12Z

I'm having the same issue ever since I upgraded to Visual Studio 15.4.4 which obviously included the sdk 2.0.3

jorgeyanesdiez · 2017-11-16T11:54:30Z

Same issue here as @jeremymeng
I have cleaned up my system, and only have the 2.0.3 SDK, runtime (x64 and x86) and windows server hosting packs, therefore, @livarcocc 's solution doesn't work for me, but @Kurtbaby 's does.

Kurtbaby · 2017-11-16T15:36:34Z

Microsoft recognized some of the errors of their ways and released new versions of the runtime and server hosting for 2.0.3 since my last post, and this has solved our deployment issue (not discussed this thread), but sadly, we still have to use the RunTImeFrameworkVersion tag in the project in order to use dotnet ef ... commands. We are also using a "Data project" and have isolated the context, etc. into this class lib, which uses a DesignTimeFactory for the context. I have not yet tested this behavior against a standard, template-generated web project, but will do so and report the results back here.

Kurtbaby · 2017-11-16T16:08:31Z

Here's an update. If we leave the context and models in the same aspnet web core project generated by the template, we are able to run the CLI tools without the error. As soon as we extract the context and models into their own class lib, we are forced to use the RunTimeFrameworkVersion tag in order to use the CLI tools. Not sure why as this class lib code/technique was working fine until we upgraded to v15.4.4.

livarcocc · 2017-11-16T17:36:26Z

@Kurtbaby any chance you can provide a repro project? On github or a zip? I would love to debug this issue.

livarcocc · 2017-11-16T19:05:10Z

We have gotten a repro for this issue and understand it now. We are working on a fix for it. The best work around available to it right now is setting RuntimeFrameworkVersion in your library project targeting netcoreapp2.0. I will explain why this happens in a next comment when I get a chance.

livarcocc · 2017-11-16T19:19:18Z

So, the issue here is that the SDK was setting the implicit version of the Microsoft.NETCore.App to 2.0 instead of 2.0.0. NuGet was then restoring using that and finding the closest available package. We then used that version to write the rutimeconfig.json file.

In the cases where this repros, the libraries target netcoreapp2.0, but because they are libraries, no runtimeconfig.json is generated and EF ends up evaluating the RuntimeFrameworkVersion from the project and sees it as 2.0, which the host then does not understand, which leads to the failure here.

This works for apps because in that case we do generate a runtimeconfig.json and use that to run EF.

The real fix here is really just changing the implicit version from 2.0 to 2.0.0.

jorgeyanesdiez · 2017-11-16T19:25:43Z

@livarcocc can that be done without waiting for fixed packages? eg: using global.json?

nathannis · 2017-11-16T21:55:31Z

I have this issue as well after upgrading to VS 15.4.4
dotnet --version is printing as 2.0.3

The property group fix by @Kurtbaby fixes it for me as well.

<PropertyGroup>
   <TargetFramework>netcoreapp2.0</TargetFramework>
   <RuntimeFrameworkVersion>2.0.3</RuntimeFrameworkVersion>
</PropertyGroup>

I am adding it before running dotnet ef migrations add ... and then removing it before committing to source control since this seems like a bug that will be fixed soon.
Thanks!

bricelam · 2017-11-16T22:22:49Z

Workaround (EF Tools)

Adding the following to the project should also make it work.

<PropertyGroup>
  <GenerateRuntimeConfigurationFiles>true</GenerateRuntimeConfigurationFiles>
</PropertyGroup>

bgrainger · 2017-11-17T17:13:52Z

<GenerateRuntimeConfigurationFiles>true</GenerateRuntimeConfigurationFiles> didn't fix the problem for me with xunit (e.g., as in this comment).

The <RuntimeFrameworkVersion> and --fx-version workarounds did; this isn't ideal because (I would assume) it now requires all contributors and CI environments to have exactly that SDK version installled.

bricelam · 2017-11-17T23:27:37Z

Sorry, can't speak for xUnit.net... Updated.

livarcocc · 2017-11-17T23:35:10Z

@bgrainger I would suggest filling an issue under xunit itself for this. They may have to do the same fix there that we are doing in EF. The fix that we can make on the SDK side won't really fix the problem for tools if they are using the --fx-version option of the host to specify a runtime.

livarcocc · 2018-01-29T18:28:33Z

dotnet --version gives you the SDK version that is being resolved.

DouglasMarsh · 2018-01-31T17:41:00Z

The issue is closed but the bug seems to still exist.

I'm experiencing this issue with latest Visual Studio 2017 (15.5.6)
adding RuntimeFrameworkVersion to csproj does not fix the issue of dotnet test not discovering tests
colleagues that are using VS version 15.5.1 are not experiencing this issue.

note: dotnet xunit will discover and run tests after RuntimeFrameworkVersion is added

A sample project that repos this issue with just an xUnit and UnitTest project is attached.
vs2017_15.5.6_UnitTestIssues.zip

.NET Command Line Tools (2.1.4)

Product Information:
Version: 2.1.4
Commit SHA-1 hash: 5e8add2

Runtime Environment:
OS Name: Windows
OS Version: 10.0.15063
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.4\

Microsoft .NET Core Shared Framework Host

Version : 2.0.5
Build : 17373eb129b3b05aa18ece963f8795d65ef8ea54

Sotam · 2018-02-04T13:23:18Z

Currently have 2.1.0-preview2-26131-06 installed, but VS2017 doesn't detect the framework. Do I need to install something else? Currently I can only select up to dotnet core 2.0.

livarcocc · 2018-02-04T18:34:09Z

@mlorbetske for the template question.

mlorbetske · 2018-02-04T18:44:50Z

@phenning I’m case he has any thoughts here.

@Sotam if you run “dotnet new console” at the command line, does a 2.1 project get created?

Sotam · 2018-02-04T21:19:54Z

@mlorbetske First I must apologize, replied to the wrong issue. But nonetheless, you made my day! I was able to create a new project using the console and then build it in VS2017 :)

DiginessForever · 2018-02-09T16:49:50Z

I'm having this problem as well. "dotnet --version" is 2.1.4. I am using Visual Studio Enterprise 2017.

Sotam · 2018-02-09T16:51:30Z

@DiginessForever which version do you have? (dotnet --info)

DiginessForever · 2018-02-09T16:51:56Z

2.1.4 (updated my comment above).

Sotam · 2018-02-09T16:58:08Z

@DiginessForever I'm running a preview build .NET Command Line Tools (2.1.300-preview1-008019) . If I remember correctly, gotten from here

DiginessForever · 2018-02-09T17:17:12Z

One of my issues is that I have my data layer in a separate project (all the layers, App, Domain, Repository, and Data are in separate projects). The data layer is a class library.

redowl3 · 2018-02-09T17:31:40Z

Have you tried adding a global.json file to you data project?
{
"sdk": {
"version": "2.1.4"
}
}

tiwilson7 · 2018-02-12T18:45:00Z

We had this same problem for developers who only had the "Microsoft .NET Core SDK - 2.1.x" installed but did not have a 2.0.x version of the SDK installed.

The solution (work-around, really) was to go the the archive downloads and install the latest 2.0.x SDK version (which can live side by side with 2.1.x).

.NET Core 2.0.3 SDK

See dotnet/cli#7901

* Fix Gui project on travis * Fix xUnit on travis * Fix xUnit errors * Use fixed runtime version See dotnet/cli#7901

rfuhrer · 2018-02-16T23:29:42Z

@tiwilson7 Thanks for that. I just built a new machine (only has the latest SDK installed) and got everything up and running except xunit CLR. It doesn't work even with dotnet xunit -fxversion 2.1.4. After installing the 2.0.3 SDK and running dotnet xunit -fxversion 2.0.3 it was working again.

jlanng · 2018-02-23T22:18:56Z

@rfuhrer did you find a solution? same problem here

rfuhrer · 2018-02-23T23:02:11Z

@jlanng install the old 2.0.3 SDK and then force it to run that sdk using the command dotnet xunit -fxversion 2.0.3. It's just your unit tests running that version so it's not like you're forcing your production copies to use an old version of dotnet core or anything.

I actually ended up not really using dotnet xunit since it didn't seem to play as nice with the dotnet CLI plugin for TeamCity (couldn't figure out how to make it know that it could run dotnet xunit and expect the results coming out to be digested the same way as dotnet test). Shaving a few seconds off my build time wasn't worth the hours i was going to spend trying to figure that out

cgountanis · 2018-03-07T15:39:55Z

The 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?

<RuntimeFrameworkVersion>2.0.5</RuntimeFrameworkVersion>

jg11jg · 2018-03-13T13:28:42Z

Note that it is the Microsoft .NET Core Shared Framework Host framework version not the .NET Command Line Tools version that you need to use in the -fx argument (2.0.5 in the below, NOT 2.1.4)

`PS G:\MyFirstUnitTests> dotnet xunit
Detecting target frameworks in MyFirstUnitTests.csproj...
Building for framework netcoreapp2.0...
MyFirstUnitTests -> G:\MyFirstUnitTests\bin\Debug\netcoreapp2.0\MyFirstUnitTests.dll
Running .NET Core 2.0 tests for framework netcoreapp2.0...
The specified framework version '2.0' could not be parsed
The specified framework 'Microsoft.NETCore.App', version '2.0' was not found.

Check application dependencies and target a framework version installed at:
\
Alternatively, install the framework version '2.0'.
PS G:\MyFirstUnitTests> dotnet --version
2.1.4
PS G:\MyFirstUnitTests> dotnet xunit -fxversion 2.1.4
Detecting target frameworks in MyFirstUnitTests.csproj...
Building for framework netcoreapp2.0...
MyFirstUnitTests -> G:\MyFirstUnitTests\bin\Debug\netcoreapp2.0\MyFirstUnitTests.dll
Running .NET Core 2.1.4 tests for framework netcoreapp2.0...
It was not possible to find any compatible framework version
The specified framework 'Microsoft.NETCore.App', version '2.1.4' was not found.
Check application dependencies and target a framework version installed at:
\
Alternatively, install the framework version '2.1.4'.
PS G:\MyFirstUnitTests> dotnet --info
.NET Command Line Tools (2.1.4)

Product Information:
Version: 2.1.4
Commit SHA-1 hash: 5e8add2

Runtime Environment:
OS Name: Windows
OS Version: 10.0.16299
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.4\

Microsoft .NET Core Shared Framework Host

Version : 2.0.5
Build : 17373eb129b3b05aa18ece963f8795d65ef8ea54

PS G:\MyFirstUnitTests> dotnet xunit -fxversion 2.0.5
Detecting target frameworks in MyFirstUnitTests.csproj...
Building for framework netcoreapp2.0...
MyFirstUnitTests -> G:\MyFirstUnitTests\bin\Debug\netcoreapp2.0\MyFirstUnitTests.dll
Running .NET Core 2.0.5 tests for framework netcoreapp2.0...
xUnit.net Console Runner (64-bit .NET Core 4.6.26020.03)
Discovering: MyFirstUnitTests
Discovered: MyFirstUnitTests
=== TEST EXECUTION SUMMARY ===
MyFirstUnitTests.dll Total: 0
PS G:\MyFirstUnitTests>`

andreacassioli · 2018-04-09T11:22:59Z

Any clear solution to this issue? I am running on OSX using dotnet from the CLI:

13:20 $ dotnet --version 2.1.4

`
13:20 $ dotnet xunit
Detecting target frameworks in PreplanningApiTests.csproj...
Building for framework netcoreapp2.0...
PreplanningApiTests -> /Users/aca286/workspace/deacon/preplanning-api/PreplanningApiTests/bin/Debug/netcoreapp2.0/PreplanningApiTests.dll
Running .NET Core 2.0 tests for framework netcoreapp2.0...
The specified framework version '2.0' could not be parsed
The specified framework 'Microsoft.NETCore.App', version '2.0' was not found.

Check application dependencies and target a framework version installed at:
/
Alternatively, install the framework version '2.0'.

`

I have tried some of the proposed workaround but no way.

replaysMike · 2018-04-14T23:48:09Z

I too have this issue. I think it was caused either when uninstalling preview-2 and installing preview-3. I no longer have a 2.1.0-preview2-final directory in C:\Program Files\dotnet only 2.1.0-preview1-26216-03 and launch using IIS Express anymore because of this issue.

DiginessForever · 2018-04-18T05:27:15Z

All, I've figured something out regarding transactions on the latest preview nuget package (preview2). I could not get the TransactionScope working, but have successfully gotten CommittableTransaction working. Here's a doc link: https://docs.microsoft.com/en-us/ef/core/saving/transactions (look near the bottom for the code sample I used to get going) They are still working on TransactionScope apparently (System.Transactions is not fully supported the best I can tell in the sqlclient package yet). Regards, Jacob

…

On Sat, Apr 14, 2018 at 5:48 PM, Michael Brown ***@***.***> wrote: I too have this issue. I think it was caused either when uninstalling preview-2 and installing preview-3. I no longer have a 2.1.0-preview2-final directory in C:\Program Files\dotnet only 2.1.0-preview1-26216-03 and launch using IIS Express anymore because of this issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/dotnet/cli/issues/7901#issuecomment-381368788>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AOIMLAt42A7lc_k4Nf1TwLQVM75bNp2Fks5toorIgaJpZM4QFwFD> .

DiginessForever · 2018-06-03T16:37:49Z

Hey guys, You might try this: Try changing the targeted framework to .net standard manually in the project file. https://docs.microsoft.com/en-us/dotnet/standard/frameworks I don't know if that will work, but in our projects we have some .NET 4.7 projects and some .NET Core 2.0 ones. T The only way to have a .NET 4.7 dependency is to change the .NET Core 2.0 project files manually to target .NET Standard. Regards.

…

On Tue, May 29, 2018 at 5:14 AM, Radenko Pavlovic ***@***.***> wrote: Error It was not possible to find any compatible framework version The specified framework 'Microsoft.NETCore.App', version '1.0.0' was not found. - Check application dependencies and target a framework version installed at: \ - Alternatively, install the framework version '1.0.0'. Dotnet tools .NET Command Line Tools (2.0.3) Product Information: Version: 2.0.3 Commit SHA-1 hash: 12f0c7e <dotnet/cli@12f0c7e> Runtime Environment: OS Name: Windows OS Version: 10.0.17134 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\2.0.3\ Microsoft .NET Core Shared Framework Host Version : 2.0.7 Build : 2d61d0b043915bc948ebf98836fefe9ba942be11 Problem Hey guys, I have similiar problem, I can not publish my .net core application because dotnet bundle fails. I have followed advices from this issue and I downgraded my SDK to 2.0.3 as it was pointed out. I added <RuntimeFrameworkVersion>2.0.3</RuntimeFrameworkVersion> to my project files too. But still I am not able to publish as the error keeps occurring. Some help would be great. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/dotnet/cli/issues/7901#issuecomment-392725918>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AOIMLBFOnyQOVRJxdGOjk-Z9VhkxfVaUks5t3R-FgaJpZM4QFwFD> .

mistrykam · 2018-07-08T14:03:30Z

First determine which run time version you are using: dotnet --info

Then edit each .csproj and add the tag:

You will have to close and open Visual Studio.

TheAifam5 · 2018-07-17T09:16:40Z

Wow guys,
I have the newest version of dotnet and I still have this issue..... 👏
Just fresh projects and added Api as a reference to Tests. 👏 👏

dotnet --info:

.NET Core SDK (reflecting any global.json):
 Version:   2.1.302
 Commit:    9048955601

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17134
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.1.302\

Host (useful for support):
  Version: 2.1.2
  Commit:  811c3ce6c0

.NET Core SDKs installed:
  2.1.302 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

dotnet xunit:

Detecting target frameworks in X.Tests.csproj...
Building for framework netcoreapp2.1...
  X.Api -> D:\Projects\Private Repositories\X.Api\bin\Debug\netcoreapp2.1\X.Api.dll
  X.Api.Tests -> D:\Projects\Private Repositories\X.Api.Tests\bin\Debug\netcoreapp2.1\X.Api.Tests.dll
Running .NET Core 2.1.0 tests for framework netcoreapp2.1...
It was not possible to find any compatible framework version
The specified framework 'Microsoft.NETCore.App', version '2.1.0' was not found.
  - Check application dependencies and target a framework version installed at:
      C:\Program Files\dotnet\
  - Installing .NET Core prerequisites might help resolve this problem:
      http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409
  - The .NET Core framework and SDK can be installed from:
      https://aka.ms/dotnet-download
  - The following versions are installed:
      2.1.2 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

bloritsch · 2018-08-23T00:33:18Z

NOTE: the XUnit libraries have another dependency runtime dependency that is not called out specifically: System.Text.Encoding.CodePages

I had to add that to my test project and use dotnet xunit -fxversion 2.1.2 to get Xunit to work.

yatli · 2018-11-08T12:11:30Z

dotnet xunit is now deprecated:

xunit/xunit#1767

livarcocc self-assigned this Nov 15, 2017

riQQ referenced this issue in riQQ/SabberStone Feb 15, 2018

Use fixed runtime version

c888529

See dotnet/cli#7901

rnilva referenced this issue in HearthSim/SabberStone Feb 16, 2018

Fix CI (#110)

5f646d2

* Fix Gui project on travis * Fix xUnit on travis * Fix xUnit errors * Use fixed runtime version See dotnet/cli#7901

msftgits transferred this issue from dotnet/cli Jan 31, 2020

msftgits added this to the 2.1.3xx milestone Jan 31, 2020

The specified framework 'Microsoft.NETCore.App', version '2.0' was not found #8826

The specified framework 'Microsoft.NETCore.App', version '2.0' was not found #8826

Comments

redowl3 commented Oct 25, 2017

Steps to reproduce

Expected behavior

Actual behavior

Environment data

livarcocc commented Oct 25, 2017

redowl3 commented Oct 26, 2017 • edited Loading

livarcocc commented Oct 26, 2017

redowl3 commented Oct 26, 2017

livarcocc commented Oct 26, 2017

netbidev commented Oct 27, 2017

livarcocc commented Oct 27, 2017

netbidev commented Oct 28, 2017 • edited Loading

dls314 commented Oct 30, 2017

dls314 commented Oct 30, 2017

livarcocc commented Oct 30, 2017

dls314 commented Oct 30, 2017

jeremymeng commented Nov 9, 2017 • edited Loading

Kurtbaby commented Nov 15, 2017 • edited Loading

livarcocc commented Nov 15, 2017

jeremymeng commented Nov 15, 2017 • edited Loading

haidelber commented Nov 16, 2017

jorgeyanesdiez commented Nov 16, 2017

Kurtbaby commented Nov 16, 2017

Kurtbaby commented Nov 16, 2017

livarcocc commented Nov 16, 2017

livarcocc commented Nov 16, 2017

livarcocc commented Nov 16, 2017

jorgeyanesdiez commented Nov 16, 2017

nathannis commented Nov 16, 2017 • edited Loading

bricelam commented Nov 16, 2017 • edited Loading

Workaround (EF Tools)

bgrainger commented Nov 17, 2017

bricelam commented Nov 17, 2017

livarcocc commented Nov 17, 2017

livarcocc commented Jan 29, 2018

DouglasMarsh commented Jan 31, 2018 • edited Loading

Sotam commented Feb 4, 2018

livarcocc commented Feb 4, 2018

mlorbetske commented Feb 4, 2018

Sotam commented Feb 4, 2018

DiginessForever commented Feb 9, 2018 • edited Loading

Sotam commented Feb 9, 2018

DiginessForever commented Feb 9, 2018

Sotam commented Feb 9, 2018

DiginessForever commented Feb 9, 2018

redowl3 commented Feb 9, 2018

tiwilson7 commented Feb 12, 2018

rfuhrer commented Feb 16, 2018

jlanng commented Feb 23, 2018

rfuhrer commented Feb 23, 2018 • edited Loading

cgountanis commented Mar 7, 2018 • edited Loading

jg11jg commented Mar 13, 2018

andreacassioli commented Apr 9, 2018

replaysMike commented Apr 14, 2018

DiginessForever commented Apr 18, 2018 via email

DiginessForever commented Jun 3, 2018 via email

mistrykam commented Jul 8, 2018 • edited Loading

TheAifam5 commented Jul 17, 2018 • edited Loading

bloritsch commented Aug 23, 2018

yatli commented Nov 8, 2018

redowl3 commented Oct 26, 2017 •

edited

Loading

netbidev commented Oct 28, 2017 •

edited

Loading

jeremymeng commented Nov 9, 2017 •

edited

Loading

Kurtbaby commented Nov 15, 2017 •

edited

Loading

jeremymeng commented Nov 15, 2017 •

edited

Loading

nathannis commented Nov 16, 2017 •

edited

Loading

bricelam commented Nov 16, 2017 •

edited

Loading

DouglasMarsh commented Jan 31, 2018 •

edited

Loading

DiginessForever commented Feb 9, 2018 •

edited

Loading

rfuhrer commented Feb 23, 2018 •

edited

Loading

cgountanis commented Mar 7, 2018 •

edited

Loading

mistrykam commented Jul 8, 2018 •

edited

Loading

TheAifam5 commented Jul 17, 2018 •

edited

Loading