As an outsider (the last time I developed on a Windows platform was 2001) I feel like I see different acronyms all the time in the Windows app-building world, each with a lifetime of about three years.
If I'm in a bookstore, the cover of the latest Windows related magazines always seems to be about some dramatically new way to do some relatively boring thing, and how you should abandon everything you're doing and use this stuff instead.
But perhaps it is not fair to judge the entire MS platform by these more frothy aspects.
Microsoft (like any other major software vendor) has popular products and not so popular products. The popular ones survive, the unpopular ones don't die off, they end up still being supported just not in such a way.
See MSFT's data access libaries, you ado, ado.net, entity framework, linq to sql and zeus knows what else now.
You also have COM+. While it's an overcomplicated mess, and not as popular as it once was, it's still supported.
Our company's codebase is written in C#. Some domain specific language parsers were implemented using F# (with Fparsec) and the framework can be extended using IronPython. At some points, we have IronPython code being called from F# code built on a framework written in C#. And it works without specifically having to handle it.
Visual Studio's debugger can seamless step between code written in C# and F#.
There are lots of things I miss about Unix dev tools but the Microsoft technology stack is not an unreasonable choice to make.