J
John Spiegel
Hi all,
I'm working through examples on configuring ASP.NET (all on local machine).
The first exercise deals with the customErrors in the config files. The
machine.config file has a customErrors mode set to RemoteOnly and the
application's web.config has it set to On with a redirect for a 404 error.
This works fine.
However, when I add a subfolder to the application and place a web.config
file in there (from the IDE so I'm not just manually introducing typos) then
run, I get the error:
Error while trying to run project: Unable to start debugging on the web
server. Server side-error occurred on sending debug HTTP request.
It continues to happen whether I leave the subfolder's web.config alone or
change the customErrors setting. The <CustomErrors> element of the
machine.config's <configSection> does not specify any allowDefinition
restrictions (which I'm told would default to allowing "sub-configs"
anywhere).
Any idea where to look next?
TIA,
John
I'm working through examples on configuring ASP.NET (all on local machine).
The first exercise deals with the customErrors in the config files. The
machine.config file has a customErrors mode set to RemoteOnly and the
application's web.config has it set to On with a redirect for a 404 error.
This works fine.
However, when I add a subfolder to the application and place a web.config
file in there (from the IDE so I'm not just manually introducing typos) then
run, I get the error:
Error while trying to run project: Unable to start debugging on the web
server. Server side-error occurred on sending debug HTTP request.
It continues to happen whether I leave the subfolder's web.config alone or
change the customErrors setting. The <CustomErrors> element of the
machine.config's <configSection> does not specify any allowDefinition
restrictions (which I'm told would default to allowing "sub-configs"
anywhere).
Any idea where to look next?
TIA,
John