> It is not a perfect solution as library maintainers need to put effort into migrating to NET Standard. But if library authors have not done it by now, then pe

> It is not a perfect solution as library maintainers need to put effort into migrating to NET Standard. But if library authors have not done it by now, then perhaps you should use a different library The effort isn't very difficult in my experience; switch CSPROJ formats, edit the file to be multi-framework, rinse repeat. Your build scripts and/or CI pipeline will probably be where more of the work is. That said... >>have one dependency that hasn't been updated to support Core and you can't upgrade and then you can't use anything new. >Can you give any examples? WCF.