Sure, since my list wasn't exaustive.
Those of us that had a go at ASP, ASP.NET, ATLServer, ActiveX, Silverlight, WebForms, AJAX Control Toolkit, WebAPI, WebAPI 2, MVC, Core MVC, Razor Pages.
Those of us that had a go at ASP, ASP.NET, ATLServer, ActiveX, Silverlight, WebForms, AJAX Control Toolkit, WebAPI, WebAPI 2, MVC, Core MVC, Razor Pages.
Same thing with most of Windows GUI frameworks MS built. They all use same rendering language/interface (xaml).
Doesn't matter how long they have been supported.
If by "They all use same rendering language/interface (xaml)." you mean a XML based file format to describe the GUI layout, you are right.
If on the other hand you mean a GUI description language that is compatible with zero code changes, then not really.
I'm not even sure why you're counting WebAPI in there since it's for writing REST APIs.
The graveyard of Node and JS technologies is orthogonal to the current burnout feeling in many Windows circles regarding Microsoft technologies.
To the point that, as I already mentioned a few times, I happened to do .NET Framework to something else ports, instead of the more rational migration to modern .NET.
You see the same in long time well known Microsoft partners like Sitecore, moving away from .NET.
Technologies change all the time in every stack; flavors come and go.
By the standard of the web JS ecosystem, .NET has been relatively stable.
I don't care what others do.
It is like kids on the kindergarten playground, arguing for who behaves better.