Today, encountered a very XX problem, depressed to death ....
I wanted to add an updatepanel in the project today and refresh it in some places. I thought it was very simple to get it. The previous demo can be implemented... However, moving to the project won't work...
It turned out to be <xhtmlconformance mode = "Legacy"/>.
Summary:
See http://www.microsoft.com/china/msdn/library/webservices/asp.net/ASPNETusStan.mspx
To meet everyone's requirements, Microsoft has created a new configuration option named xhtmlconformance. You can set this option in the configuration file of the web site. The new configuration options enable you to specify the XHTML consistency level for Web pages. Its content is as follows.
<Configuration>
<System. Web>
<Xhtmlconformance
Mode = "Transitional"/>
</System. Web>
</Configuration>
By default, xhtmlconformance is set to transitional. However, you can set this option to strict or legacy.
If you set the xhtmlconformance option to strict The standard ASP. Net Control will no longer render certain attributes. For example, the ASP. NET <form> control no longer presents the name attribute. Unless the ASP. NET page contains (non-compliant) client scripts, no changes are noticed when switching from transitional mode to strict mode.
If you set the xhtmlconformance option to legacy The ASP. NET Framework restores some elements and attributes (but not all) to ASP. NET 1.1. In this case, the ASP. NET Framework will present content that is not compatible with any XHTML standard and the page will no longer pass the XHTML standard verification. For example, in legacy mode, when a <br> tag is displayed, the expected XHTML end slash (<br/>) is not displayed ).
Only when you apply existing ASP. NET 1.1ProgramIt makes sense to set xhtmlconformance to legacy mode when you encounter problems during migration to ASP. NET 2.0.
/Files/kingjiong/testajax.rar