I am having dificulty debugging an ASP.NET Ajax (Novemver CTP) app on windows
vista RTM.
I have found the following interesting facts but cannot join the dots . .
If my application is configured to run in the Classic .NET App pool, when I
hit F5 in visual Studio 2005 I can successfully debug my application, however
partial rendering using an update panel does not work (I have discovered that
the script resource handler is causing a 500 server error when being
requested - presumably it has not been registered successfully in
web.config?).
If my Application is configured to run in the DefaultAppPool (integrated
pipeline mode), when I hit F5 Visual studio 2005 fails to attach with a
security dialog being displayed: "Unable to start debugging on web server. An
authentication error occurred while communicating with the web server. Please
see help for assistance".
Furthermore, if I subsequently attach to the w3wp process (integrated mode)
by hand, I can successfully debug the web site and Ajax functionality works.
(This is presumably because the Ajax handlers are registered in the iis7
config GUI).
So my 2 questions are:
1) Why do the Ajax handlers not work in Classic Pipeline mode when using the
Web.Config generated by the New ASP.NET Ajax Enabled Web Site project
template in VS2005?
2) Why does Visual Studio 2005 not automatically attach to an otherwise
functioning web site running in Integrated Mode?
Many thanks,
Dave Prentice
