We have a project that has had a scriptManager added to each page. We were thinking of switching to one scriptManager in our MasterPage. Is there any reason to do this, besided the obvious one scriptManager in one place?

As long as it's necessary on every page, the Master page is the logical place to put it. If there are a lot of pages that don't need it, you'll incur some overhead on those pages that is really unnecessary.

You could also create two master pages in that scenario. One with a ScriptManager for the pages that need it and one without for those that don't.

Jackxxx:

We have a project that has had a scriptManager added to each page. We were thinking of switching to one scriptManager in our MasterPage. Is there any reason to do this, besided the obvious one scriptManager in one place?

Yes, it does matters. You need to have ScriptManager on each page wherever you are using Ajax controls throughout your application.

I m not aware of an alternative way to set ScriptManger at project level.

Let me know if you come to know.

Thanks,

 My reason for asking is that I have read recently that if you put a scriptmanager in your masterpage you don't need them on any other page that accesses the masterpage.

This is correct.

 But you're saying there is a performance hit for the pages that don't need the scriptManager? This project has AJAX used in almost every page. So would it be better to remove the scriptManagers from the individual pages and only have the one in the MasterPage?

Jackxxx:

This project has AJAX used in almost every page. So would it be better to remove the scriptManagers from the individual pages and only have the one in the MasterPage?

Absolutey. You can do that.

As long as you are using Ajax control throughout your web app, it is better to keep ScriptManager in Master page, which is called on each and every page.

I can't see any performance overhead in doing so.