Geek Answers Handbook

Mix Ajax and ASP.NET MasterPages?

Has anyone had experience using these two technologies in tandem? What are (if any) major difficulties for the two to work together? How will a site using these technologies differ from a regular ASP.NET web application with Ajax?

Thanks!

+4
source share
4 answers

Yes, they work well together.

The only thing you need to pay attention to is that if you have a ScriptManager on the Wizard, you cannot declare another on the content pages.

If you want to register scripts and services using the ScriptManager on Content pages, you need to use ScriptManagerProxy instead. This is a control specifically designed for the Master / Content scenario.

+11
source

I used the master pages and ASP.NET AJAX together without any problems. You can either use the script manager on your content placeholders, or use one script on the main page, but then you must remember that ScriptManagerProxy in the content areas should get the correct functionality.

+2
source

IT depends on what you are talking about in the Ajax Framework, for ASP.NET AJAX you need to mess with ScriptManager (Proxy), which complicates it a bit, but not so much that it is very difficult ...

samples Ra-Ajax basically, everyone uses MasterPages, without having to work with ScriptManager or ScriptManagerProxy. But Ra-Ajax is based on a completely different architecture than ASP.NET AJAX ...

By the way, I work with Ra-Ajax and can hardly be called "neutral" ...

+1
source

In addition to declaring ScriptManager on the main page and ScriptManagerProxy on the content pages, it is good practice to put all the JavaScript files in a separate dll so that you have all your resources separate from the rest of the project. Having separate versions of debugging and releasing (with spaces removed) Javascript files, you get a good performance boost.

0
source

More articles:


All Articles