Nuget Warning for canopy in .NET Core 2 Project
See original GitHub issueNU1701
Package 'canopy 2.0.0' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.0'. This package may not be fully compatible with your project.
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (10 by maintainers)
Top Results From Across the Web
c# - .NET Core - Nuget Pack of UniTest Project shows ...
.NET Core - Nuget Pack of UniTest Project shows warning "The assembly is not inside the 'lib' folder" · Your screenshot is still...
Read more >PackageReference in project files - NuGet
Package references, using <PackageReference> MSBuild items, specify NuGet package dependencies directly within project files, as opposed to ...
Read more >After VS 17.8 update, Yellow triangle on all nuget ...
1) Working project ASP.NET CORE 2.1 2) Update VS 17.8 3) Nuget dependences all in YELLOW without warning. 4) Nuget packet says no...
Read more >Install AWSSDK packages with NuGet - AWS SDK for .NET
NuGet is aware of dependencies between packages and installs all required packages automatically. Warning. The list of NuGet packages might include one named ......
Read more >Nuget warning NU1605 | TypeSpec Azure
This article helps you to solve the nuget warning NU1065 which can occur when including the Microsoft.TypeSpec.ProviderHub.Controller package in a solution ...
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
@zbigniew-gajewski Thanks for the lead. I used paket pack to make these packages and it may have caused a difference. I am on vacation now but when I get home I will see if I can make a new package like you did that does not cause the warning.
Thanks again!
Later today I have some free time and I will try switching to
.NETStandard2.0
to see if that fixes it. Thanks!