One of our applications has a mechanism for emailing our Helpdesk automatically should it encounter a certain level of exception. One particular exception, a NullReferenceEx
If you need to avoid PrecompiledApp file and publish Global.asax, please go to Publish and move to setting tab at bottom and uncheck the precompile during publishing.
Belove image will be help you
If you are publishing the app, then do check for PrecompiledApp.config file. If you remove that file from the published site folder, the events would stop firing.
I would make sure that the logging logic is not running into some sort of a permission issue while logging null reference exceptions. Do you have the approprite permissions to access where the log is being written?
We had this problem and a missing PrecompiledApp.config file was the solution. Without it global.asax events did not fire under IIS6 using an ISAPI filter and the rewritten.aspx approach documented e.g. on blog.codeville.net. We use msbuild to precompile the site before deploying.
We scratched our heads over this one for a couple of hours when our builds stopped working. Turns out while in obsessive house-keeping mode I had removed this file from source control as I thought it was redundant. Adding it back in fixed the problem.
We tried a lot of things.
We also tried putting the below files in root
and bin
directories.
None of it worked!
We had to put raw Global.asax
instead of pre-compiled
dll, in order to fire the global events, for our asp .net 2.0 website.
Hope this helps someone! Cheers! Happy coding! :D