Question

I am trying to deploy my first MVC3 application to a server running IIS-7.5. I’ve got the thing up and running, but I’m having some trouble with my debugging methods. I use a proprietary debugging construct that works just fine when I run the application locally (using the built in “IIS Express” module and Visual Studio) – but when I deploy to the server, I don’t even get my debug file created, much less printed to.

The debugging file is created in the Application_Start event, so I put an event log stamping in the Application_Start event and ran the application locally and on the server, just to see if the event is getting fired. My event logs locally were stamped to as intended, but the event logs on the server are bare of any new stamping. What’s going on here?

protected void Application_Start()
  {
     AreaRegistration.RegisterAllAreas();

//This is just some code that calls to another module I wrote to easily stamp to the Event logs - it works, trust me
     EventLogging.Initialize();
     EventLogging.WriteEventLog("Application Start Called Successfully");
  }

Answer 1

IIS 7.5 uses virtual accounts for the application pools.

See App Pool Identities. Make sure the specific app pool identity has access to the appropriate folder to read/write.