I have a new portal module project in which I need to run some processes on the “application start event”.

I have spent 3  days trying different tricks and workarounds to trapping the application start event from a portal module project to no avail. I have just discovered that my workarounds and tests were flawed because the “Application_Start” event in the DNN core project file  Global.asax.vb does not appear to be trapped/raised.

This is happening in both  my  DNN5.5.0 and 5.5.1 installs

I tried running my DNN5.5.0. in .NET 4.0 framework  (Integrated Pipeline Mode) and DNN5.5.1 in classic Pipeline .Net 2.0 mode and when running in debug (VS2010 IIS7) in either site, my breakpoint on the Application_Start event in the Global.asax.vb is never triggered.

Am I doing something wrong. Is anyone else seeing this behavior.

Many thanks,  Les

I am trying to put these processes I only want run on "application_start" into my own project. I am not putting them into the global.asax.vb (core project) because it would require a circular project reference.

So I have two problems:
1) It appears the appllication_start event in the global.asax (DNN Core code) is not being fired which I assume is a problem as there are important processing related to loding componentfactorys attached to it.

2) Once I have fixed problem #1,  I need trap the application start event in my own WAP project to perform my own processing related to my custom portal module project/application.
  tried the suggestion in post http://www.dotnetnuke.com/Community/B... 
However, in IIS7/.Net 4.0 apparently multiple instances of a HttpModule can be triggered so relying on the init event within the htpmodule only being run once for the life of the application is no longer the case.  I tried some tricks related to "inherits" the core global.asax, but if the event it not being trapped in the DNN core project then my inherits workaround is also not going to work.

It turns out that the Application_Start event is being run, but something about the VS2010 debugger is preventing our ability to debug it with a breakpoint.
I tried commenting out the whole applciation_start event and the site would not run.
The workaroung to trapping the event for debugging only was to add:
        System.Diagnostics.Debugger.Break()
into the Application_Start sub

Now I still have to figure out a way for my own project to run some stuff on the application_start event.

Les