[srb24]

If you have a great product that you can get live quickly and works then it won't matter if you even write it in COBOL (don't write it in COBOL though) - ASP.Net & SQl Server (even the free version) also work very well together and have great performance.

There are of course licensing costs if you run on Windows and don't use MONO but these shouldn't really be an issue in comparison to all your other costs

Also there are a lot of ASP.Net/C# developers around (just look at odesk) which will help you build your team faster (unlike Ruby or Scala developers, which are great languages, just harder to recruit and also attract higher wages).

My advice... build a proof on concept as quickly as possible - if .net is your thing then use that vs. wasting time learning something else. The chances are that your concept may need to be reworked so why waste time...

Good luck!

[allegory]

I'd caution against the performance claims. Yes its very good and can take a serious beating but there's a brick wall that requires a pile of tuning and tool purchasing to get over.

Oh and the instrumentation and debugging past the bits of code you wrote and the .Net runtime core libraries is utterly horrible.

See some of my earlier comments about this matter.

I'd rather build on the JVM now thanks to tools like VisualVM and profilers that can be deployed across the team for free.

[mattmanser]

99% of startups simply will never hit the performance problems you seem to be talking about.

[JoeAltmaier]

Yeah but its the ones that matter, that do? The successful ones with traction.

[allegory]

Indeed. We thought it was the same and nearly lost two big clients because we didn't see it coming.