>I am pre-compiling the web, but it isn't a single dll. I get several odd name dlls in the bin folder and optionally I can keep the aspx files outside. I think the big advantage to web app project is the single dll file with a real name rather than several with random names. Plus some project organizational advantages. Do you see more than this? I am using MM and there isn't a template for the web app project yet, so didn't do that, but I am going to figure out what is needed to make my own template as I would prefer to use that method.

Yes, there are a lot of advantages. First of all, to compare with in-place compilation, the day the client will want the source out of the server, a compile project would be needed. Then, I only want to deal with one DLL for the application and another one for the framework. So, usually, I do not update the framework. The updates are pretty much at the application level. I have found that this is usually working better when a new version is sent. It usually works pretty much all the time but sometimes, I still have a jam on the server and a IISRESET /RESTART is required unless I wait a few minutes and it does it starts responding back to the hits.