Bruce,
This is an interesting topic.
It would seem that
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/gngrfCodeBase.asp
implies that the codebase *can* be used by
web applications, since that page specifies that:
"If the assembly has a strong name, the codebase setting
can be anywhere on the local intranet or the Internet.
If the assembly is a private assembly, the codebase
setting must be a path relative to the application's directory."
and, it also specifies that :
"This element can be used in the application configuration file,
machine configuration file (machine.config), and the publisher
policy file."
I don't see any restrictions regarding usage only in Winforms.
Also, the info in
http://msdn.microsoft.com/library/d...guide/html/cpconconfiguringieapplications.asp
states that:
"The administrator can use the <probing> element in the configuration
file to specify that the runtime should search for assemblies in
subdirectories of the application base.
Suppose that
www.adventure-works.com/webApp/StockCalc
maps to C:\Inetpub\Wwwroot\Webapps\StockCalc.
Putting <probing privatePath="bin"/> in the configuration file
causes the runtime to search for assemblies in
C:\Inetpub\Wwwroot\Webapps\StockCalc\Bin
as well as C:\Inetpub\Wwwroot\Webapps\StockCalc."
The path "C:\Inetpub\Wwwroot\Webapps\StockCalc\Bin"
strongly suggests that a web application is using the <probing>
element to locate an assembly.
I confess I'm not an expert in this field, but the implications
of the statements in that page are very strong in favor of
web applications being able to use the <runtime>
configuration section of web.config.
If I'm being misled by these documents,
I'm ready to hear otherwise, though.
Juan T. Llibre
ASP.NET MVP
===========