Exactly this. It's what they've always done: support other platforms right up until they hold a sizeable market share; then monopolise that technology on their own platform.
Since it's more trouble porting code to a new language than it is porting web servers to a new host OS, it makes total sense to encourage more developers towards .NET via open source platforms.
"It's what they've always done: support other platforms right up until they hold a sizeable market share; then monopolise that technology on their own platform."
I'm curious: what are these "other platforms" that Microsoft have briefly supported?
Internet Explorer on Macs back in the days of the IE / Navigator wars. Lotus document formats back before MS Office was the de facto standard.
And even just talking about .NET, that was only created to compete with Java after Sun to Microsoft to court over MS's own Java implementation (though granted it's since evolved into something much more). .NET was originally sold as but MS quickly lost interest in pushing it on non-Windows platforms. And then came Silverlight to compete with Flash; and the cross platform hopes for that followed a similar fate once it became obvious that Flash was no longer a competition.
Windows Media Player for Solaris during media wars. When they ended, support was dropped.
Internet Explorer for UNIX (Solaris, HPUX) during browser wars. When they ended, support was dropped.
Does leopard change its spots? If they are successful with ASP.NET as The Web Framework (not much realistic, I know), expect them to drop support for anything but Windows.
Since it's more trouble porting code to a new language than it is porting web servers to a new host OS, it makes total sense to encourage more developers towards .NET via open source platforms.