1. Use app_offline.htm
in asp.net 2.0. If you want to COPY the site, perform site maintenance, deployment, and make a lot of modifications, you may have to stop your WEB application and prompt the user in a friendly way. , such as "This website is being updated" and other information, in ASP. NET 2.0, you can create a static HTM page file called app_offline.htm (case does not matter), modify it to the content you want to display temporarily, and place it in the root directory of your application. In this way, any external requests will be immediately transferred to this page. At this time, your website can still be accessed, but your application cannot be accessed. Haha, in that case, a lot of troubles in updating the website can be avoided.
Of course, another method is to make your site offline in the asp.net configuration management tool under the website menu of vs.net 2005.
It should be noted that the size of the app_offline.htm page must be greater than 512 bytes. , in the words of SCOTT, the father of asp.net, it is "
Make sure the app_offline.htm file is large enough (512 bytes) to disable the IE “friendly http errors” feature
2 Use the MaintainScrollPositionOnPostback property
Considering a very long page, if every time after POSTBACK, the IE scroll bar may return to the beginning (top) without retaining its original position, which will be more troublesome for the user, and To move the scroll bar to its original position, in asp.net 2.0, you can set the MaintainScrollPositionOnPostback property to TRUE, that is
<%@ Page Language="VB" AutoEventWireup="false" MaintainScrollPositionOnPostback="true" CodeFile="MaintainScrollPosition.aspx.vb" Inherits="MaintainScrollPosition" %>
http://www.cnblogs.com/jackyrong/archive/2006 /08/26/486826.html