There is a strong perception (whether accurate or not--and I honestly don't know the answer) that it's the same old story with Microsoft: if you go the .NET route, you've gotta buy into the entire Microsoft ecosystem. It's not just .NET that you're choosing; you're also choosing Windows servers, IIS, Visual Studio, etc. If that perception is accurate, it's entirely reasonable to say, "Despite liking a lot of what .NE…
Currently the same applies to every known service. You have developed using AWS or App Engine and try to migrate to other systems without changing a line of code?
"We're tied to AWS and we need to edit some code to deploy on Rackspace Cloud or into our new DC"
vs.
"We're tied to MS so our options of where we're going to go are severely limited by the fact that we can ONLY move to providers who work with MS."