Tips and Tricks

• Set the FallBackTimeout property to a large value during debugging
  The FallBackTimeout property defines the timeout period in seconds. Once it expires, the Ajaxium client-side code assumes that the AJAX request has failed and a fallback to the ASP.NET must be performed. The property is set at 20 by default so the fallback occurs after 20 seconds of debugging and the AJAX request results are lost. To avoid the fallback, set the FallBackTimeout property to a large value (for example 20000) in the Ajaxium configuration sections of the web.config file.
• Move all scripts registered by controls to an external JavaScript file
  Most of web-browsers are unable to dynamically load and parse JavaScripts. So if the page content changes and additional scripts must be loaded (especially with Page.RegisterClientScriptBlock methods), Ajaxium initiates rewriting of the entire document to force the browser to renew scripts and avoid scripting errors. Rewriting is a resource-consuming process and may cause flickering in some browsers (e.g. FireFox, Netscape). To avoid rewriting it is recommended to extract all the scripts from the controls and pages source code and move them to an external JavaScript file. After that you can load the JavaScript file using the following html code:
  <script src="file.js" type="text/javascript"></script>
• Verify that your website is accessible with Ajaxium disabled
  Before testing the website in an AJAX mode to make sure that it is accessible and rendered correctly by all target browsers in a classic ASP.NET mode. To switch to an ASP.NET mode set the AjaxiumEnabled property to "false" in the Ajaxium configuration sections of the web.config file.