According to this blog post, the mere presence of app_offline.htm in the root of the site will stop the entire application, so while it's there no one would be able to run setup either. I guess you could put this file in place, ftp your new version mojoPortal files to the server, then remove/rename this file and run Setup. That way you would minimize the chances of someone hitting a page that contains an upgraded feature that needs schema database upgrades before you have had a chance to run setup. If that situation were to happen they would probably get a 500 error.

Jamie

Hi Andria,

It is safe to run the setup page at any time, it will not ever hurt anything by visiting the setup page in between upgrades. When upgrading though you do need to be careful to make sure you upload all the new files especially the ones under /Setup before you visit the setup page which is why I usually upload that folder first. Taking it offline while you do the uploading is not a bad idea because then you can be sure setup doesn't run with just some of the new files.

Also it is good to disable setup from user.config so that only admin users can run the page, then make sure you do login before you upgrade because it will run for admins even when it is "disabled" but if you are not logged in you would have to enable it again.

<add key="DisableSetup" value="true" />

Best,

Joe