I want to be able to run a script anytime ANY page is loaded in the application. Is there somewhere I can simply add this? Or do I have to add the code in every page load?
views:
200answers:
5You can do one of three things:
Use a base page in your application, and have all the pages in your application inherit from it. In the page_load event in the base page, do what you have to do. Make sure that the inheriting pages in your app call the base page's page_load event if they override page_load (they usually do). And because page_load is over-used, I'll give the related advice to look at all the page events (especially especially page_prerender) in case another is more appropriate.
Use the events that fire in the global.asax page, which happen whenever a request is received. Check out the Application_BeginRequest event. But, there's a bunch of events there, so check them all out in case another event is more applicable to your situation. (Just like the regular page events, don't get in the bad habit of always using the same event.)
There's a chance that what you want to have happen each time should go into a master page, especially if it's layout related. Master pages seem cutesy but have proved themselves in good designs. If you use a master page's page_load event for common functionality, you don't have to call it from each content page's page_load; it fires every time after the called-page's page_load event. (I mention this because it's easy to confuse master pages and base pages at first.)
You could create a common base class for your pages, descended from System.Web.UI.Page and add the code in an OnLoad handler there.
You can use BeginRequest event in the Global.asax
file.
http://msdn.microsoft.com/en-us/library/system.web.httpapplication.beginrequest.aspx
You can use PageAdapters to inject Code on every aspx page request by intercepting any method of ASP.Net Page life cycle.
This article can help you understand its working: http://dotnet.org.za/hiltong/archive/2008/01/06/injecting-a-page-base-class-in-asp-net.aspx
Regards.
You could also create and register an HTTP Module. The advantage of that is that they are registered in the web.config, so you can add and remove them at runtime if you want... and have more than one.