Or you could always read my blog on Simulating Application_Start event.

John,

  It is not clear from the above links how one would go about hooking up code to run on EVERY application start.  It looks like the config file could handle this, but that is not clear.  Also, is this still the correct method given the re-architecting that was done for the eventqueue?

BTW.  The way that isComplete flag is set after processing the message now causes a problem if the code that is called does not return successfully. If this happens the message will keep trying to process the upgrade or whatever every time the application starts. There have been several reports of people saying their event log is filling with errors because of this.

Now one argument may be that the code needs to keep trying to execute on every application start, but I personally don't think that is a good idea since it is usually an error in the module code that will not go away. Plus, if the end user removes the module then they'll get new errors from the EventQueue trying to process a message for a module that is not there anymore.