.NET 4.5.1 and .NET Core 5
We want to use the "vNext" technology in our next project.
To me it looks like we can only use framework 4.5.1 when we rely on libraries like Serilog or mongoDB which have dependencies on older versions of the Framework. Is this really the case or is there a way to have dependencies that depend on the full old version of the framework and the project itself depends on .NET Core 5.0?
source to share
(Answering only the first of your questions as the second seems too broad and / or vague ...)
Is this really the case or is there a way to have dependencies that depend on the full version of the old framework and the project itself depends on .NET Core 5.0?
Yes it does - and makes sense, IMO. You say, "I want my application to be able to run on .NET Core." How would this work if some of the libraries you depend on try to use features that don't exist in .NET Core?
I suspect this will get much better soon - once things stabilize a bit and it's easier for open source projects to create .NET Core-enabled NuGet packages, I would expect most projects to focus on portability doing my best to support his.
(Some of this will depend on the toolkit, although - I realize that right now the only way to create a package that works with .NET Core is to use a project like vNext rather than a "normal" VS Class Library project with a specific PCL profile. Hopefully this is will change, but we'll see.)
source to share