question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Tools built with imports fail

See original GitHub issue

I have a tool (dotnet-ef) that depends on Ix-Async (a portable-windows8+net45+wp8 library). Its project.json looks like this.

{
  "compilationOptions": {
    "emitEntryPoint": true
  },
  "dependencies": {
    "Ix-Async": "1.2.5",
    "NETStandard.Library": "1.0.0-*"
  },
  "frameworks": {
    "dnxcore50": {
      "imports": "portable-net452+win81"
    }
  }
}

I’m trying to use that tool in a project with the following.

{
  "tools": {
    "dotnet-ef": "1.0.0-*"
  },
  "dependencies": {
    "NETStandard.Library": "1.0.0-*"
  },
  "frameworks": {
    "dotnet54": { }
  }
}

However running dotnet restore fails because the imports information used when building the tool is lost.

Restoring Tool 'dotnet-ef' for 'MyApp\obj\cb47a3d7-fd7d-48de-bda3-f29662e98d51\bin\project.json' in 'MyApp\obj\cb47a3d7-fd7d-48de-bda3-f29662e98d51\bin'
info : Restoring packages for MyApp\obj\cb47a3d7-fd7d-48de-bda3-f29662e98d51\bin\project.json...
error: Ix-Async 1.2.5 is not compatible with DNXCore,Version=v5.0.
error: Some packages are not compatible with DNXCore,Version=v5.0.
error: Ix-Async 1.2.5 is not compatible with DNXCore,Version=v5.0 (win7-x64).
error: Some packages are not compatible with DNXCore,Version=v5.0 (win7-x64).
error: Ix-Async 1.2.5 is not compatible with DNXCore,Version=v5.0 (win7-x86).
error: Some packages are not compatible with DNXCore,Version=v5.0 (win7-x86).
info : Committing restore...
info : Restore failed in 9329ms.

Note, this is also happening for Remotion.Linq (a portable-net45+win+wpa81+wp80 library).

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:18 (13 by maintainers)

github_iconTop GitHub Comments

2reactions
joshcomleycommented, Mar 22, 2016

In case anybody needs it, I bodged a console app to use the latest sources to generate migrations anyway. Details here:

http://overengineer.net/generating-new-entity-framework-migrations-when-dotnet-ef-is-broken

0reactions
bricelamcommented, Apr 5, 2016

BTW, I’ve mitigated EF’s need to use imports for tools in aspnet/EntityFramework#4977 by removing nearly all of our tool’s dependencies.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Failed to import new Gradle project: failed to find Build ...
Whenever you will try to run a project with build tool version not present in studio, You will face this error.
Read more >
Are there any diagnostics for when user tool import fails?
I have an issue importing my book notes into Accordance. The notes are in html format, but when I go to import the...
Read more >
x/tools/cmd/gopls: fails to detect local package in import
With GOPATH built version (version v0.1.0-cmd.gopls, built in $GOPATH ... x/tools/cmd/gopls: fails to detect local package in import #32733.
Read more >
cmd/go: go mod tidy error when importing std package in ...
I recently hit this issue when I made a shim to support io/fs for another project that will be unable to upgrade to...
Read more >
Cannot launch User Import Tool, error crashes the app.
We have started receiving an error a few days ago when the User Import Tool program starts. The app closes after the user...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found