[Goosey]

This is extremely exciting. The lack of a 'No-compile developer experience' has been one of the biggest annoyances for me and my team. It actually has lead to influencing our coding patterns: since we can "refresh and see new code" for anything that is in the view templates (Razor *.cshtml in our case) we have become increasingly in favor of putting code there (or in javascript frontend 'thick client' code) to take advantage of not needing to recompile. It's not like recompiling is slow (maybe 5sec in our case), but it still breaks your flow and more importantly requires stopping the debugger if it is in use. In some ways the code has improved, in some ways it hasn't, but in either case it feels like the tail wagging the dog when you are changing how you structure code based on your tool's inadequacies.

I'm equally excited for the intentional mono support and "Side by side - deploy the runtime and framework with your application". ASP.NET MVC and Web API are really pleasant and mature frameworks, but configuring IIS has always been really unpleasant and clunky.

[roller]

From my experience, the initial compile is fast, it's the app pool recycle and JIT on first page load that leave you in the hallway playing chair mounted sword fights.

I'm hoping that with ahead of time compile option at least will give you some actual feedback as to what's happening. That'd at least be better than watching the browser sit there loading a page for while.

[edandersen]

You are putting increasing amounts of code in your Razor views?

[nickstinemates]

Just wait until they discover PHP :)

[Guillaume86]

Putting code in razor views is a very bad idea, have you tried .NET Demon for continuous compilation? If you write tests you might want to consider NCrunch?