[Suggest] Multi-targeting support for netfx
hcoona opened this issue · 5 comments
I think this is a topic related to all aspnet common libraries (Microsoft.Extensions.*) but I didn't found a suitable place for it.
I want the libraries enable multi-targeting feature to decouple netfx with netstandards. There are 2 main benefits for it:
- Get rid of whole net standard libraries for netfx projects.
- Support net45 or somehow earlier version of netfx.
A pure netfx project would not like to involve whole net standard libraries for no gain. This would increase the complexity of maintaining & deploying.
We didn't use most new features in net standard 2.0, especially for the features not appears in net45. However, we dropped the support to net45 for the reason we want to target to net standard. Surely we can target to net standard. There's no reason we couldn't target to netfx also with the help of multi-targeting.
I noticed that there is a 3rd party works on it https://www.nuget.org/packages?q=NetFx.Extensions but I think it better to be provided by official.
We have no plans to support cross targeting to net45 (it's not even a supported framework anymore net452 is the minimum). That 3rd party fork seems like the way to go, it even supports targeting net40 which we're never going to do.
By saying net45, I'm not stick to it but just use net45 for an example just because the 3rd party fork supported it. I think supporting net462 is also a meanful work. (Yes I know net462 works with net standard 2.0)
The answer is the same though, we don't cross compile because netstandard2.0 does run everywhere we need these libraries to run. I understand the experience is less than ideal but it's being improved.
Well, it's acceptable but not so good. I really cannot understand why because it could become better for almost no cost by merging the forked version back.
This issue was moved to dotnet/aspnetcore#2535