Including NETStandard.Library for exclusively net461-projects
See original GitHub issueWhen doing a paket update
for a .Net 4.6.1 project that only has net461 references, paket includes a .Net Core-related artifact that breaks the toolchains – ProjectCracker, FSAutoComplete, xbuild and FSharp.Compiler.Service.
Paket version: 5.92.1, 5.92.3.
Issue Analytics
- State:
- Created 6 years ago
- Comments:42 (39 by maintainers)
Top Results From Across the Web
NET Standard
NET Standard allows a library to use more APIs but means it can only be used on more recent versions of .NET. Targeting...
Read more >Referencing a .NET Standard library from a Windows Class ...
NET Core project from a Windows Class Library should be possible. However—the .NET Standard library is not "directly compatible" with previous ...
Read more >Understanding the .NET ecosystem: The introduction of . ...
In this post I'll discuss the history of sharing code between .NET platforms using Portable Class Libraries. I'll then introduce .NET Standard ......
Read more >What is .Net Standard? How it is different from .Net Core ...
It is a re-usable library project where we specify the .Net Platforms we are planning to target during creation of library. This project...
Read more >.NET Core vs .NET Framework vs .NET Standard: A Guided ...
A guide for understanding the differences between .NET, .NET Core, .NET Framework, .NET Standard, etc. by exploring the history of the platform.
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
@haf we are deeply sorry for all the trouble, but we’re really only trying to do the right thing here 😉
I released a new Suave, too https://www.nuget.org/packages/Suave/2.3.0-beta
Thanks @matthid