3 ms·

I think they prepare already a while the shift to .NET Core as the primary .NET platform (also on Windows). - .NET Core will soon run all three UI technologies

by oaiey 8y ago

I think they prepare already a while the shift to .NET Core as the primary .NET platform (also on Windows). - .NET Core will soon run all three UI technologies of modern Windows UWP, WinForms and WPF (.NET Core 3). - The Windows Compatability Pack for .NET Core shifted some popular .NET Framework libraries to .NET Core (some only on Windows). There are one thing, Microsoft is really bad with: Telling the world that something is deprecated. There is a set of technologies in the .NET Framework which have no future: AppDomains, WCF, Code Access Security, Workflow Foundation, Cardspace, ... (just to name a few). They are all already dead for some years, but no one tells. They are supported in the .NET Framework but no progress happens. And .NET Core will never see them.

cptskippy 8y ago
> Microsoft is really bad with: Telling the world that something is deprecated. There is a set of technologies in the .NET Framework which have no future: AppDomains, WCF, Code Access Security, Workflow Foundation, Cardspace, ... (just to name a few). There's no reason to deprecate a mature product if there's need for it, it has sufficient test coverage, and there's low/no maintenance. There is however a risk involved with deprecating them that users will migrate to another technology stack entirely. WCF is one of those technologies that was deployed heavily in Enterprise and is deeply ingrained in applications and systems going on a decade old. WFC has better support for SOAP than anything I've seen in the open source world and with a minor configuration tweak it can simultaneously support JSON from the same endpoint. Workflow Foundation is in a similar state to WCF, though I wouldn't shed a tear if it vanished off the face of the planet.
- oaiey 8y ago
  I agree. With everything. However, a not evolving platform is a dead platform. New code should not target this platform. Even for Enterprise environments it not a joy to see the world evolve while you are stuck with a toolset a decade old. It is already now painful to see the difference in tooling between Core and Framework.
- skrowl 8y ago
  I agree. Don't deprecate just to clean house. Only deprecate when you have a mature / table replacement.
elorant 8y ago
We live in a world where Cobol mainframes are still around and in use. Microsoft can not depreciate ten year old technologies when the vast majority of their clientele in this sector are enterprises.
- oaiey 8y ago
  Oh it will be supported. But it will be a dead platform like Cobol where no one wants to put new code to. With a bit of luck they will continue to support the latest C# for a while.
manigandham 8y ago
A lack of new features does not mean something is deprecated. That would mean actively discouraging its use, something that doesn't make sense given the sheer amount of code written and the fact that support will continue for years, if not decades.
benaadams 8y ago
https://docs.microsoft.com/en-us/dotnet/core/porting/libraries#net-framework-technologies-unavailable-on-net-core https://docs.microsoft.com/en-us/dotnet/core/porting/librari... Code Access Security and Security Transparency aren't supported on .NET Framework either

by oaiey 8y ago

cptskippy 8y ago

> Microsoft is really bad with: Telling the world that something is deprecated. There is a set of technologies in the .NET Framework which have no future: AppDomains, WCF, Code Access Security, Workflow Foundation, Cardspace, ... (just to name a few). There's no reason to deprecate a mature product if there's need for it, it has sufficient test coverage, and there's low/no maintenance. There is however a risk involved with deprecating them that users will migrate to another technology stack entirely. WCF is one of those technologies that was deployed heavily in Enterprise and is deeply ingrained in applications and systems going on a decade old. WFC has better support for SOAP than anything I've seen in the open source world and with a minor configuration tweak it can simultaneously support JSON from the same endpoint. Workflow Foundation is in a similar state to WCF, though I wouldn't shed a tear if it vanished off the face of the planet.

oaiey 8y ago
I agree. With everything. However, a not evolving platform is a dead platform. New code should not target this platform. Even for Enterprise environments it not a joy to see the world evolve while you are stuck with a toolset a decade old. It is already now painful to see the difference in tooling between Core and Framework.
skrowl 8y ago
I agree. Don't deprecate just to clean house. Only deprecate when you have a mature / table replacement.

elorant 8y ago

We live in a world where Cobol mainframes are still around and in use. Microsoft can not depreciate ten year old technologies when the vast majority of their clientele in this sector are enterprises.

oaiey 8y ago
Oh it will be supported. But it will be a dead platform like Cobol where no one wants to put new code to. With a bit of luck they will continue to support the latest C# for a while.

manigandham 8y ago

A lack of new features does not mean something is deprecated. That would mean actively discouraging its use, something that doesn't make sense given the sheer amount of code written and the fact that support will continue for years, if not decades.

benaadams 8y ago

https://docs.microsoft.com/en-us/dotnet/core/porting/libraries#net-framework-technologies-unavailable-on-net-core https://docs.microsoft.com/en-us/dotnet/core/porting/librari... Code Access Security and Security Transparency aren't supported on .NET Framework either