App Offline – Nice feature to bring down Microsoft SharePoint based sites

the “”App_Offline.htm”” feature in ASP.NET 2.0 provides a super convenient way to bring down an ASP.NET application while you make changes to it (for example: updating a lot of content or making big changes to the site where you want to ensure that no users are accessing the application until all changes are done).
The way app_offline.htm works is that you place this file in the root of the application.  When ASP.NET sees it, it will shut-down the app-domain for the application (and not restart it for requests) and instead send back the contents of the app_offline.htm file in response to all new dynamic requests for the application.  When you are done updating the site, just delete the file and it will come back online.

Creating an iGoogle style experience in SharePoint 2007

SharePoint 2007 does not provide this experience OOB. You will have to customize this requirement via programming.

I found a similar post on ASP.NET forum, you might be interested in: http://forums.asp.net/p/838714/838714.aspx

 Among the replies, Fredrik Normén(MVP) provides the general idea on how to implement this feature in SharePoint: override CatalogPartChrome, CatalogZone and WebPartZone.

Basically, you’ll have to override most of the web part base classes. For more information on these classes, please visit: http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.webparts.aspx

Nice feature to bring SharePoint 2007 Portal sites down

 

The “App_Offline.htm” feature in ASP.NET 2.0 provides a super convenient way to bring down an ASP.NET application while you make changes to it (for example: updating a lot of content or making big changes to the site where you want to ensure that no users are accessing the application until all changes are done).
The way app_offline.htm can be used with SharePoint 2007 and the way it works is that you place this file in the root of the application.  When ASP.NET sees it, it will shut-down the app-domain for the application (and not restart it for requests) and instead send back the contents of the app_offline.htm file in response to all new dynamic requests for the application.
When you are done updating the site, just delete the file and it will come back online.