>Hi All,
>
>I was just wondering about the option or not to have the website updateable when you publish it. I typically leave it as updateable because there is so fewer files to push up. I tried to update an aspx file with this and it really doesn't work as I got all kinds of errors. If I set it to not updateable it appears to compile all the aspx files so then why does it also publish the actual aspx files also.
>Tim

I typically publish them as updatable so I can make minor changes in the ASPX/ASCX files if necessary. You can't do things like remove controls, but if you want to move something around or add something minor (that doesn't effect the code in the codebehind) you're OK.

If they're non-updatable ASP.NET generates a placekeeper file that it uses to determine how to map incoming requests to the correct assembly. The ASPX/ASCX pages aren't required, but the .compiled version is.