After reading Scott Guthrie\'s blog entry about the new Razor view engine for ASP.NET MVC and reading this question comparing the available view engines.
Razor seems to
Obviously I haven't evaluated it in practice yet, but the fact that it is terser than the ASPX engine is the most compelling feature to induce a switch. I only hope that it also auto-formats more nicely. The fact that it will be supported with intellisense and delivered with MVC makes it a natural choice for starting new projects. I'm going to give it a fair shot on a small project before I make the switch. Just from reading the article I didn't see anything that I wouldn't be able to do with it that I'm currently doing with the ASPX engine.
Update: I've been using Razor for well over a year now and would never go back to the ASPX engine. The syntax seems very natural and expressive.