Here is what I plan to do (the question follows the description):\n\nMy intent is to have a custom HTTP module dynamically determine which \nclasses should handle various pipeline events. We'll call this the "loader \nmodule". The loader module then (1) loads the assemblies that house the \nother classes, instantiating the requisite object; then (2) wires up the \nrequisite pipeline event to the corresponding event handling method of the \nclass instantiated from the dynamically loaded assembly.\n\nThe idea here is that I can, for example, have a few different classes (each \nin its own assembly) that can handle specific HTTP pipeline events (like \nBeginRequest or AuthenticateRequest) - and then have one of those classes \nprocess that event during all future requests. This would allow me to have, \nfor example, multiple custom authentication mechanisms - each implemented in \nits own class and assembly, one of which is then plugged into the \napplication by my custom HTTP module.\n\nMy question:\nWill this even work? FWIW: I know how to dynamically load assemblies and \ninstantiate classes from them. I'm just not understanding the mechanism in \nASP.NET that would call my custom HTTP module (the "loader module") - which \nneeds to be called only once; yet call the dynamically loaded Request \nprocessing module(s) for every single request (to handle, for example, the \nAuthenticateRequest event).\n\nThanks.