Xhtmlconformance mode = "Legacy" Node causes ajax.net to fail

ExpertsArticle: Http://www.cnblogs.com/huangbaixun/archive/2008/11/28/1342944.html

Thanks to this article, I accidentally solved my problem.

Because my web. config file is very clean and there is no useless configuration, I did not expect it to be a problem with the configuration file. I tried a variety of methods that I could think of: upgrade. net, reinstall aspajaxex, and restart the server. It took me nearly a workday to put it down and felt unwilling. The search of various keywords is changing. It is also a dead horse, and maybe it will catch up with the problem.

The same is true for it. The root cause of the error may be the location that is stuck, which causes a big problem.

Sure enough, I am sorry for it. When I follow the instructions in this article. after a node <xhtmlconformance mode = "Transitional"/> is added to the config file, the long-awaited partial refresh effect is finally available.

The problem is solved, but I am still not clear? As mentioned above, when upgrading .. the node is automatically added to the configuration file during net1.1. However, although my project was upgraded from 1.1, I have re-created the configuration file and have no such node. In a flash, I thought about the home directory of the website. Is there a problem? Because it has been upgraded recently, and Ajax is not used in the home directory. The current project is under the virtual directory. Immediately open the configuration file of the main directory, and find the <xhtmlconformance mode = "Legacy"/> node, and angrily delete it, at the same time, the node added to the configuration file of the current project is also deleted, open the browser for a try, and only click partial.

This is really a tough problem!