Closed OpResCodes closed 3 years ago
I guess the easiest way would be to migrate it completely to .NET 5.0 call it version 2 and cut all dependencies to earlier .NET versions. This would mean, that we are not backwards compatible but it would be far easier to handle in the future.
Oops? Im little out of .NET development because i switched to Java in my job. Was there a breaking change to the NETStandard? ObjectFiller uses .NET Standard 1.0 which is also implemented by .NET 5. So why should it be necessary to upgrade?
I added target framework moniker for NETStandard1.3 and NETStandard2.0. If you now reference ObjectFiller.NET in an .NET 5 project it does not ask for one million dependencies anymore :). I hope this is the reason you ask for migration to latest .net version. If you have any other problems, feel free to reopen this issue
Could you migrate it to the latest .net version? :)