29

I am trying to reference a nuget package which is clearly .NetStandard2.0. We own the source code for this package and written it to target .netstandard. We do have a CI pipeline so that when we push this code, it builds and releases the nuget package. When I try to reference the resulting nuget package into my current .netCore application, i get following error:

was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.1'. This package may not be fully compatible with your project.

That does not make any sense to me. So far I have tried following debugging steps:

  • Referenced the source code directly as a project reference to my project. Which did work all fine.
  • Analyzing resulting nuget package in dotpeek to make sure that it in fact is a .netstandard package and it is.

Not sure what makes it think that it was targeting at any point. below is how my .csproj configuration looks like

<TargetFramework>netstandard2.0</TargetFramework>

Not sure if any other config block matters here but let me know if you need more info on this. Any ideas?

Lost
  • 12,007
  • 32
  • 121
  • 193
  • 1
    Hi @Lost, did you ever get to the bottom of this? I am having the same problem ... – cedd Sep 19 '20 at 11:05
  • @cedd don’t remember unfortunately, but one did you try what TomP mentioned below? Making sure your package name is actually unique? Sometimes it can end up resolving a package from central nuget feed before it resolves yours. – Lost Sep 19 '20 at 14:27
  • Thanks @lost, I have checked that, and it is unique already sadly. I'm currently using dotnet pack with a .nuspec file, so am going to try it with a .csproj file instead to see if that helps. – cedd Sep 19 '20 at 17:12

4 Answers4

6

I ran into this issue as well. In my case, when the DLL was packaged and placed in the lib/ folder, the import warning occurred. It was solved by placing the packaged DLL in the lib/netstandard2.0 folder.

Chronogeran
  • 61
  • 1
  • 1
  • I would like to confirm this fixed my issue when i upgraded my package from .net 4.6 to .net standard 2.0! – LlamaNL Nov 19 '21 at 11:29
  • I confirm this fixed my issue too. I built and published a .net6.0 nuget package. – Naweap Nov 13 '22 at 17:50
4

I ran in to a similar issue where I was publishing my own NetStandard2.0 package via Azure Artifacts and then attempting to consume it in a netcore application.

It turned out that the problem was that I had named my package the same as an existing NuGet package. My Azure Artifacts nuget feed was configured correctly in Visual Studio, but when it attempts to install the package it tries the default NuGet feed first and picks up the other one (which happened to be NetFramework only) rather than mine.

Once I renamed my package to be unique (I just added my own namespace) and re-published it all worked properly.

I guess that might not be the issue for everyone but it was for me.

TomP
  • 89
  • 4
3

You have to use every packages in your project compatible with .NETCoreApp,Version=v2.0.

There should be some package name before "was" in your error message. For ex:

Package 'Microsoft.AspNet.WebApi.Client 5.2.2' was restored
Package 'EntityFramework 6.2.0' was restored
cdev
  • 5,043
  • 2
  • 33
  • 32
  • The package is produced for .NetStandard 2.0. We have the code and we built it against `NetStandard2.0` – Lost Feb 22 '19 at 17:10
2

I had the same problem. To fix this

  1. Look in VS2019 under dependencies / Packages.
  2. Then look for the packages with the warning sign next to them.
  3. Goto your windows profile directory and delete the corresponding folder under .nuget
  4. Delete the reference under dependencies / Packages
  5. Add the Nuget package via Manage Nuget Packages for solution
Nigel Findlater
  • 1,684
  • 14
  • 34