ASP. NET Ajax 1.0 resource connection and answers to some frequently asked questions

[Original article] links to ASP. NET Ajax 1.0 resources, and answers to some common questions
[Original article published on] Thursday, January 25,200 AM

Below are several ASP. NET Ajax 1.0 resource connections and my answers to several Frequently Asked Questions Related to ASP. NET Ajax 1.0 product release:

Wonderful free resources: ASP. NET Ajax memo table in PDF Format

Milan updated his wonderful ASP. Net Ajax memo table in pdf format for the final release of ASP. NET Ajax 1.0.

You can download the updated version here. Confirm that you have subscribed to his blog so that you will receive the new memo.

FAQ: restart IIS after installation and clear your browser cache

I have seen several situations. After upgrading to ASP. NET Ajax 1.0, I still see that the old version of ASP. NET Ajax script is used. This usually occurs in the form of a client JavaScript error "SYS. debug not being found (SYS. debug cannot be found. If you encounter this situation, check two things:

1) confirm that you have restarted IIS after installing ASP. NET Ajax (you can run the iisreset command on the command line to restart IIS ). If the new ASP. NET AjaxProgramWhen IIS is installed with the ASP. NET Ajax assembly of the earlier version, it will continue to use the old version that has been installed until the next worker process restarts. Restarting a working process causes it to start using the new Assembly.

2) If your browser is set to permanently store cached files, confirm that you have cleared your browser cache. This will avoid the problem caused by the fact that your browser keeps the. js files of the old version in the cache and does not go to the server to obtain the new version but still use the old version.

Common intractable diseases: pagemethods requires that the enablepagemethods attribute on the <asp: scriptmanager> control be set to true.

I have seen several people have encountered a problem. After upgrading from ASP. NET Ajax RC to the final V1 version, their static Ajax webpage method (page methods) seems to be no longer working. The reason is that by default, the ASP. NET Ajax webpage method is no longer exposed unless you set the enablepagemethods attribute to true on the <asp: scriptmanager> control. For example:

<Asp: scriptmanager id = "S1" enablepagemethods = "true" runat = "server"/>

Once you set this property to true, everything else will work as usual. You can further learn how to use pagemethods in ASP. NET Ajax 1.0.

FAQ: <asp: updatepanel> verification control used in the control

I have seen several people have encountered a problem. After upgrading to the RTM version, the verification control in <asp: updatepanel> is no longer working.

In beta1, beta2, and RC versions, Asp. net Ajax provides a set of "compatible" controls by Using ASP. net web. the <tagmapping> feature in config sets ASP. net built-in verification controls are replaced with Ajax-aware controls that can be used in <asp: updatepanel>. The result is that you are using standard ASP. NET verification controls on your website, but you are actually using a set of new controls that have added Ajax associations.

In ASP. in the final version of net Ajax, we decided to give up this practice, but for ASP. NET 2.0 released a patch to add the conscious features of Ajax directly to ASP.. Net authentication control. This ensures that these controls work normally in all circumstances, which is a more clean and reliable solution. Unfortunately, the patch was delayed for a few weeks, so the patch was not released through Windows Update in time when ASP. NET Ajax 1.0 was released.

As a temporary solution before the patch release, you can download the compatibility verification controls we provide in the RC (Release Candidate version), and then follow the practice in the RC version, in your web. use the <tagmapping> feature in the config file to set the built-in ASP. net control maps to those controls:

<Tagmapping>

<Add tagtype = "system. Web. UI. webcontrols. comparevalidator"
Mappedtagtype = "sample. Web. UI. Compatibility. comparevalidator, validators, version = 1.0.0.0"/>

<Add tagtype = "system. Web. UI. webcontrols. customvalidator"
Mappedtagtype = "sample. Web. UI. Compatibility. customvalidator, validators, version = 1.0.0.0"/>

<Add tagtype = "system. Web. UI. webcontrols. rangevalidator"
Mappedtagtype = "sample. Web. UI. Compatibility. rangevalidator, validators, version = 1.0.0.0"/>

<Add tagtype = "system. Web. UI. webcontrols. regularexpressionvalidator"
Mappedtagtype = "sample. Web. UI. Compatibility. regularexpressionvalidator, validators, version = 1.0.0.0"/>

<Add tagtype = "system. Web. UI. webcontrols. requiredfieldvalidator"
Mappedtagtype = "sample. Web. UI. Compatibility. requiredfieldvalidator, validators, version = 1.0.0.0"/>

<Add tagtype = "system. Web. UI. webcontrols. validationsummary"
Mappedtagtype = "sample. Web. UI. Compatibility. validationsummary, validators, version = 1.0.0.0"/>

</Tagmapping>

 

In this way, the verification control will work normally in the <asp: updatepanel> control, and its behavior should be exactly the same as that in the RC version. You can download these compatible controls here.

I hope this article will help you.