We used BizSpark and a MSFT stack for our first iteration of the MVP (C#, ASP.NET MVC3, ServiceStack, etc.). It always raised eye-brows in a negative way when

We used BizSpark and a MSFT stack for our first iteration of the MVP (C#, ASP.NET MVC3, ServiceStack, etc.). It always raised eye-brows in a negative way when taking meetings with VCs and Angel investors. I'm not sure why, but they almost always asked a question "why MSFT? stack" and not XYZ that all their other companies were building in. I always felt like we should leave the tech stack off our slides... And they almostnever liked the answer I gave which was something along the lines "because I could build it fastest this way" We've since transitioned into a Python/Java/Postrgres stack. With no real complaints. I wonder, though, if there's any stats on companies not liking to aquire tech built on MSFT vs companies built with Java. I did a project once for one of the biggest names in enterprise software security, mostly a Java shop, and they had acquired a C#-based product, and I heard nothing but gripes from the tech team about that... At the time, one thing annoying was licensing Bizspark to run SQL server on AWS. From what I understand, this is fixed now, but back then we had to pay for a SQL Server instance, despite being part of Bizspark plan. Another thing that I wonder, if anti-MSFT bias is a regional thing. LIke if we were based in Seattle, would it be beneficial? For the record, I still like a lot of the MSFT stack, and it's great to see them embracing some other technologies, like say Node.JS on Azure and feel they'll do a lot to promote some of these newer OSS technologies into the enterprise world. EDIT: one other thing, we didn't have access to Azure at the time (it was just starting out, and I don't think it was part of the program). But Azure as a hosting option for managing the MSFT server licenses and such is a pretty enticing option.