Unless the tools/languages are tremendously better than what is available for free/cheaper, I don't particularly understand the value in:
- Risking Microsoft's ire by breaking the licenses
- Locking yourself in to long-term Microsoft licensing
This was a pattern I saw in many, many startups in the 90s -- organizations that relied first on UNIX systems for their servers (often times Solaris, Linux, and in the early-to-mid 90s, IRIX), would eventually adopt Microsoft products for some component of their infrastructure -- usually Exchange, based on heavy political pushes from the growing number of business users.
This always to the same effect -- the Microsoft products spread due to lock-in network effects until it began to near 100% MS on the desktop, e-mail, and corporate servers. Production servers generally remained UNIX due to the costs involved. The IT organization shifted to MS, costs went up as the staffing necessarily increased to support administering Windows systems, expensive political maneuvering arose between engineering and business as they both fought to move to systems that they thought better aligned with business priorities.
At the end of the day, everyone wound up locked to MS with heavily entrenched political interests in keeping the status quo (and the job security that went with it).
Having seen the fall-out from migrations to MS products in corporate IT, I can't imagine voluntarily implementing MS as the primary production and developer system at a startup. You're locking yourself out of alternative solutions, you're signing up for significantly increased capital and operational expenditures, and perhaps most importantly, you're excluding an entire class of software engineers that primarily work on UNIX-based (including Mac OS X and Linux) systems.