Web.Config and debugging
-
I have created a web service, and a coworker has created an installation package for it using InstallShield. I have just realized that I forgot to change the Web.config file to set debug to false before he made the installation package. It is currently set to
compilation defaultLanguage="c#" debug="true"/
My question is, if I manually edit the Web.config file for this web service to set it to the following value after it has already been deployed, will it still execute with all the debugging overhead and resources?
compilation defaultLanguage="c#" debug="false"/
Do I have to bother my coworker to put another build together after I change the Web.config file? Thanks for your time.
-
I have created a web service, and a coworker has created an installation package for it using InstallShield. I have just realized that I forgot to change the Web.config file to set debug to false before he made the installation package. It is currently set to
compilation defaultLanguage="c#" debug="true"/
My question is, if I manually edit the Web.config file for this web service to set it to the following value after it has already been deployed, will it still execute with all the debugging overhead and resources?
compilation defaultLanguage="c#" debug="false"/
Do I have to bother my coworker to put another build together after I change the Web.config file? Thanks for your time.
No, the point of config files is that you can deploy an exe and change things about it, by just changing the config file. The exe reads the config files.
Christian Graus Driven to the arms of OSX by Vista.
-
No, the point of config files is that you can deploy an exe and change things about it, by just changing the config file. The exe reads the config files.
Christian Graus Driven to the arms of OSX by Vista.