Package Remotion.Linq 2.0.2 is not compatible with netcoreapp1.0

.net .net-core .net-core-rc2 entity-framework-core

Question

This one is driving me crazy.

If I create a .NET Core Console App in VS2015, making no changes it builds and runs as expected.

When I add Entity Framework RC2 by adding a dependency in project.json

{
  "version": "1.0.0-*",
  "buildOptions": {
    "emitEntryPoint": true
  },
  "dependencies": {
    "Microsoft.NETCore.App": {
      "type": "platform",
      "version": "1.0.0-rc2-3002702"
    },
    "Microsoft.EntityFrameworkCore": "1.0.0-rc2-final"
  },

  "frameworks": {
    "netcoreapp1.0": {
      "imports": [ "dnxcore50" ]
    }
  }
}

then restoring packages gives the following errors:

Package Ix-Async 1.2.5 is not compatible with netcoreapp1.0

Package Remotion.Linq 2.0.2 is not compatible with netcoreapp1.0

This is expected as a work around is required as per the article here: https://docs.efproject.net/en/latest/miscellaneous/rc1-rc2-upgrade.html#using-imports-in-project-json

Where it describes adding a portable profile as an import:

  "frameworks": {
    "netcoreapp1.0": {
      "imports": [ "dnxcore50", "portable-net45+win8" ]
    }
  }

This resolves the issue with the Ix-Async but does not fix the issue with Remotion.Linq i.e. I am still seeing this error.

Package Remotion.Linq 2.0.2 is not compatible with netcoreapp1.0

I tried everything I can think of (different profiles, different project types, clearing caches) and even uninstalled, reinstalled everything several times. Short of re-building my PC I've run of ideas...

1
0
6/5/2016 5:59:50 PM

Accepted Answer

I created a VM and installed tools etc as before. I opened and built the solution successfully. So it was not my project or installs.

So on my PC I created a new Windows account. I opened and built the solution successfully on that account.

Assumption is that something is configured or cached against my other account. I deleted as much cache data as I could (in AppData etc) and yet the solution would still not build.

So the answer is, don't waste hours of your time trying to find out what the problem is, but use a fresh windows account! Not ideal obviously....

0
6/7/2016 4:53:26 PM


Related Questions





Related

Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow