3 ms·
> Frameworks like WebForms and WCF not be ported WebForms is terrible and I see no reason for anyone to pull that monstrosity of a "I wish we had a VB/Windows
by josteink 6y ago
> Frameworks like WebForms and WCF not be ported
WebForms is terrible and I see no reason for anyone to pull that monstrosity of a "I wish we had a VB/Windows WYSIWYG app-editor for the web" impedance-mismatch into a new codebase.
Applications which haven't migrated off WebForms yet, probably have little to gain by moving to .NET Core anyway.
WCF has been open-sourced[1] and ported (at least the client libraries) and you have separate community-projects[2] working on porting the rest of the stack to be compatible and usable with .NET Core.
If the community really want's to go full WCF on the new stack, they are empowered to do so.
[1] https://github.com/dotnet/wcf https://github.com/dotnet/wcf
[2] https://github.com/CoreWCF/CoreWCF https://github.com/CoreWCF/CoreWCF
- goto11 6y ago> WebForms is terrible Sure, but that is beside the point. You don't make legacy code disappear just by wishing it away.