DEV Community

Discussion on: Referencing a Specific Assembly from a NuGet Package

Collapse
 
jayjeckel profile image
Jay Jeckel

Very interesting! This trick may be on the edge of what is proper, but that's fine considering it seems that everyone else involved in this situation has jumped the shark of good practices.

A dotnet core frontend running over a dotnet framework backend is bad enough on its own, but even worse, instead of using 4.8 or at worse 4.7.2, they're using an outdated 4.6.1 version of the framework that goes out of support in literally 15 days from the time of this posting.

Piling bad decisions on top of bad decisions, it's again bad enough that a package is still targeting dotnet core app 3.1, which even though it is LTS is still losing support in December of this year, but to include a dotnet standard 2.0 assembly in that package instead of it being in its own dotnet standard 2.0 package... that's just gross.

Makes me glad I don't have to deal with any of jetbrains ecosystem and its related nonsense, but at least it resulted in this article and me learning a new trick for my toolbox. Thanks again for the great article.