Thanks for the response Steven,
What do you mean by "not recommended to modify it manually"?
Since it can't be set at runtime, isn't modifying the web.config before
runtime, setting it manually?
The article you referenced states:
"This section can be declared at the machine, site, application, and
subdirectory levels."
Does this mean that I can leave the executionTimeout at default in the
app's web.config file, put my upload form in a subfolder with its own
web.config and set the executionTimeout for the subfolder to a greater value
to allow for upload time without affecting the rest of the app?
--
Alphonse Giambrone
Email: a-giam at customdatasolutions dot us
"Steven Cheng[MSFT]" <v-******@online.microsoft.com> wrote in message
news:nX**************@cpmsftngxa06.phx.gbl...
Hi Alphonse,
As for the "executionTimeout" setting in the ASP.NET 's cofiguration, this
setting is only configurable before runtime in machine.config or
web.config file. In fact, the <httpRuntime> settings such as "executionTimeout" is
not only for fileupload scenarios , but all the http web requests will reply
on this setting, so this setting must be definite before runtime(any web
request occurs). And any modify(manually modify the confige file) on the
configuration(machine.config or web.config) will cause all the web
application or the certain web application recycle. So we're not able to
set it at runtime in code , also not recommended to modify it manually on
the config file. Do you think so? In addition, below is the reference on
the <httpRuntime> element in MSDN:
#<httpRuntime> Element
http://msdn.microsoft.com/library/en...pruntimesectio n.asp?frame=true
Hope also helps. Thanks.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx