I’ve been using ASP.NET AJAX 4.0 quite a bit lately in ASP.NET 3.5 applications. I encountered two issues tonight, and I hope this post saves someone some grief.
The first problem has to do with referencing the ASP.NET AJAX 4.0 library within an ASP.NET 3.5 application, and the second was a surprising data binding issue using the DataView.
If you are looking for more information on ASP.NET AJAX 4.0, be sure check out my other articles on the site.
Issue 1 – The ScriptManagerProxy and CompositeScripts
The first issue I encountered was a client side error when using the DataView on a content page in my ASP.NET 3.5 SP1 application. This site utilizes master pages, so I’m using a WebForm, otherwise I probably would have just gone with a plain old HTML page. Regardless, since this is an ASP.NET application and the ScriptManager is declared in the Master page, I added the ASP.NET 4.0 AJAX scripts to a ScriptManagerProxy (instead of the ScriptManager itself). The code for the ScriptManagerProxy looks very similar to that for the ScriptManger.
More...