For future reference, I've now solved the problem. Although I don't know what was originally causing it.
There were three parts of the web.config that were causing problems. So, I cut out '<httpHandlers>', '<httpModules>' and '<system.webServer>'. After this, I compiled it via F5 and it worked in debug mode.
Obviously the AJAX wouldn't work. So, I stopped the App, and pasted back in the '<system.webServer>' section and F5'd again. Compiled with debug!
Then I put back in '<httpModules>', F5'd again. Compiled with debug!
Finally I put back in '<httpHandlers>' and it all now compiles with debugging enabled.
I don't know enough about these new entries in the web.config to understand why removing and re-inserting them would cause everything to start to wrk, but it has, so I'm happy!
For future reference, I've now solved the problem. Although I don't know what was originally causing it.
There were three parts of the web.config that were causing problems. So, I cut out '<httpHandlers>', '<httpModules>' and '<system.webServer>'. After this, I compiled it via F5 and it worked in debug mode.
Obviously the AJAX wouldn't work. So, I stopped the App, and pasted back in the '<system.webServer>' section and F5'd again. Compiled with debug!
Then I put back in '<httpModules>', F5'd again. Compiled with debug!
Finally I put back in '<httpHandlers>' and it all now compiles with debugging enabled.
I don't know enough about these new entries in the web.config to understand why removing and re-inserting them would cause everything to start to work, but it has, so I'm happy!
Flipping weird! I had the exact same problem, and this procedure worked for me, too. Now I wished I'd kept ProcessMonitor running to see what was different.
->A
No comments:
Post a Comment