4 ms·

This schism cuts from both sides: have one dependency that hasn't been updated to support Core and you can't upgrade and then you can't use anything new. Many

by fowl2 7y ago

This schism cuts from both sides: have one dependency that hasn't been updated to support Core and you can't upgrade and then you can't use anything new. Many of Microsoft's own libraries such as Sharepoint and Dynamics don't support Core and many don't even have clear signalled intention to do so. Classic "big bang flag day, break compatibility" problems.

rk06 7y ago
>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? Generally, .NET Standard aims to fix the problem. If you upgrade to .NET 4.8(or atleast .NET 4.7.2), you can use libraries targetting .NET Standard v2.0(and below) So, new libraries can support both NET Framework. (Unless the authors don't want to Or can't) 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
- to11mtm 7y ago
  > 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.
- fowl2 7y ago
  > Can you give any examples? Sharepoint, Dynamics... ;) > So, new libraries can support both NET Framework. (Unless the authors don't want to Or can't) It's possible, yes. The more "active", smaller, newer libraries are already starting to get sick of this and remove support for Framework. ASP.NET for example. Further compounding the situation is when libraries take it as an opportunity to make compatibility breaks themselves. Some MS examples include Powershell, ASP.NET and Entity Framework.

by fowl2 7y ago

rk06 7y ago

>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? Generally, .NET Standard aims to fix the problem. If you upgrade to .NET 4.8(or atleast .NET 4.7.2), you can use libraries targetting .NET Standard v2.0(and below) So, new libraries can support both NET Framework. (Unless the authors don't want to Or can't) 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

to11mtm 7y ago
> 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.
fowl2 7y ago
> Can you give any examples? Sharepoint, Dynamics... ;) > So, new libraries can support both NET Framework. (Unless the authors don't want to Or can't) It's possible, yes. The more "active", smaller, newer libraries are already starting to get sick of this and remove support for Framework. ASP.NET for example. Further compounding the situation is when libraries take it as an opportunity to make compatibility breaks themselves. Some MS examples include Powershell, ASP.NET and Entity Framework.