using <runtime> section in web.config file

[Subra Mallampalli]

Hi,

I am trying to use <runtime> section within the web.config file. However,
the contents of the <runtime> section seem to be ignored. What am i missing
here? Is <runtime> section not used by web apps?

Any help is greatly appreciated.

Thanks,

Subra

[Juan T. Llibre]

Re: using &lt;runtime& gt; section in web.config file

Do you mean <httpRuntime> ?



Juan T. Llibre
ASP.NET MVP
===========
"Subra Mallampalli" <subra_nospam_m allampalli@news groups.nospam> wrote in
message news:%233asbgz$ EHA.3336@TK2MSF TNGP11.phx.gbl. ..[color=blue]
> Hi,
>
> I am trying to use <runtime> section within the web.config file. However,
> the contents of the <runtime> section seem to be ignored. What am i
> missing
> here? Is <runtime> section not used by web apps?
>
> Any help is greatly appreciated.
>
> Thanks,
>
> Subra
>
>[/color]

[Subra Mallampalli]

Re: using &lt;runtime& gt; section in web.config file

No. <runtime> section is used to specify the binding policies for the .NET
run time.
For example:
<configuratio n>
<runtime>
<assemblyBindin g xmlns="urn:sche mas-microsoft-com:asm.v1">
<probing privatePath="my BinFolder"/>
<dependentAssem bly>
<assemblyIdenti ty name="myAssembl yName" />
<codeBase href="myBinFold er2"/>
</dependentAssemb ly>
</assemblyBinding >
</runtime>
</configuration>

Basically, I am looking for a mechanism to not use the standard bin folder
for my web apps but instead use a common folder to store common dlls for a
group of web apps w/o using the GAC.

Thanks,

Subra

"Juan T. Llibre" <nomailreplies@ nowhere.com> wrote in message
news:OXq8Unz$EH A.2552@TK2MSFTN GP09.phx.gbl...[color=blue]
> Do you mean <httpRuntime> ?
>
>
>
> Juan T. Llibre
> ASP.NET MVP
> ===========
> "Subra Mallampalli" <subra_nospam_m allampalli@news groups.nospam> wrote in
> message news:%233asbgz$ EHA.3336@TK2MSF TNGP11.phx.gbl. ..[color=green]
> > Hi,
> >
> > I am trying to use <runtime> section within the web.config file.[/color][/color]
However,[color=blue][color=green]
> > the contents of the <runtime> section seem to be ignored. What am i
> > missing
> > here? Is <runtime> section not used by web apps?
> >
> > Any help is greatly appreciated.
> >
> > Thanks,
> >
> > Subra
> >
> >[/color]
>
>[/color]

[Juan T. Llibre]

Re: using &lt;runtime& gt; section in web.config file

re:[color=blue]
> "No. <runtime> section is used to specify..."[/color]

Hi, Subra.

It looks like <codebase href=" needs a web address :

<configuratio n>
<runtime>
<assemblyBindin g xmlns="urn:sche mas-microsoft-com:asm.v1">
<dependentAssem bly>
<assemblyIdenti ty name="myAssembl y"
publicKeyToken= "32ab4ba45e0a69 a1"
culture="neutra l" />
<codeBase version="2.0.0. 0"
href="http://www.litwareinc. com/myAssembly.dll"/>
</dependentAssemb ly>
</assemblyBinding >
</runtime>
</configuration>

See

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/gngrfCodeBase.asp

Juan T. Llibre
ASP.NET MVP
===========
"Subra Mallampalli" <subra_nospam_m allampalli@news groups.nospam> wrote in
message news:OBMe3N1$EH A.3472@TK2MSFTN GP14.phx.gbl...[color=blue]
> No. <runtime> section is used to specify the binding policies for the .NET
> run time.
> For example:
> <configuratio n>
> <runtime>
> <assemblyBindin g xmlns="urn:sche mas-microsoft-com:asm.v1">
> <probing privatePath="my BinFolder"/>
> <dependentAssem bly>
> <assemblyIdenti ty name="myAssembl yName" />
> <codeBase href="myBinFold er2"/>
> </dependentAssemb ly>
> </assemblyBinding >
> </runtime>
> </configuration>
>
> Basically, I am looking for a mechanism to not use the standard bin folder
> for my web apps but instead use a common folder to store common dlls for a
> group of web apps w/o using the GAC.
>
> Thanks,
>
> Subra
>
> "Juan T. Llibre" <nomailreplies@ nowhere.com> wrote in message
> news:OXq8Unz$EH A.2552@TK2MSFTN GP09.phx.gbl...[color=green]
>> Do you mean <httpRuntime> ?
>>
>>
>>
>> Juan T. Llibre
>> ASP.NET MVP
>> ===========
>> "Subra Mallampalli" <subra_nospam_m allampalli@news groups.nospam> wrote in
>> message news:%233asbgz$ EHA.3336@TK2MSF TNGP11.phx.gbl. ..[color=darkred]
>> > Hi,
>> >
>> > I am trying to use <runtime> section within the web.config file.[/color][/color]
> However,[color=green][color=darkred]
>> > the contents of the <runtime> section seem to be ignored. What am i
>> > missing
>> > here? Is <runtime> section not used by web apps?
>> >
>> > Any help is greatly appreciated.
>> >
>> > Thanks,
>> >
>> > Subra
>> >
>> >[/color]
>>
>>[/color]
>
>[/color]

[bruce barker]

Re: using &lt;runtime& gt; section in web.config file

no its not.

this is probably because the dll's are needed for the page compile first.
the compiler references are specified in the <assemblies> section (which
asp.net passes to the compiler thru switches when it spawns it).
unfortunately you can only specify the name in the <assemblies> section, not
the path, as this is specified with the compiler lib switch.

-- bruce (sqlwork.com)


"Subra Mallampalli" <subra_nospam_m allampalli@news groups.nospam> wrote in
message news:%233asbgz$ EHA.3336@TK2MSF TNGP11.phx.gbl. ..
| Hi,
|
| I am trying to use <runtime> section within the web.config file. However,
| the contents of the <runtime> section seem to be ignored. What am i
missing
| here? Is <runtime> section not used by web apps?
|
| Any help is greatly appreciated.
|
| Thanks,
|
| Subra
|
|

[Juan T. Llibre]

Re: using &lt;runtime& gt; section in web.config file

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/default.asp?url=/library/en-us/cpguide/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\Wwwr oot\Webapps\Sto ckCalc.

Putting <probing privatePath="bi n"/> in the configuration file
causes the runtime to search for assemblies in
C:\Inetpub\Wwwr oot\Webapps\Sto ckCalc\Bin
as well as C:\Inetpub\Wwwr oot\Webapps\Sto ckCalc."

The path "C:\Inetpub\Www root\Webapps\St ockCalc\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
===========
"bruce barker" <nospam_brubar@ safeco.com> wrote in message
news:%23zAc3u1$ EHA.3824@TK2MSF TNGP10.phx.gbl. ..[color=blue]
> no its not.
>
> this is probably because the dll's are needed for the page compile first.
> the compiler references are specified in the <assemblies> section (which
> asp.net passes to the compiler thru switches when it spawns it).
> unfortunately you can only specify the name in the <assemblies> section,
> not
> the path, as this is specified with the compiler lib switch.
>
> -- bruce (sqlwork.com)
>
>
> "Subra Mallampalli" <subra_nospam_m allampalli@news groups.nospam> wrote in
> message news:%233asbgz$ EHA.3336@TK2MSF TNGP11.phx.gbl. ..
> | Hi,
> |
> | I am trying to use <runtime> section within the web.config file.
> However,
> | the contents of the <runtime> section seem to be ignored. What am i
> missing
> | here? Is <runtime> section not used by web apps?
> |
> | Any help is greatly appreciated.
> |
> | Thanks,
> |
> | Subra
> |
> |
>
>[/color]

[Scott Allen]

Re: using &lt;runtime& gt; section in web.config file

Yes, what you can do is specify another subdir to probe for assemblies, ie:

<configuratio n>
<runtime>
<assemblyBindin g xmlns="urn:sche mas-microsoft-com:asm.v1">
<probing privatePath="Fo o/bin" />
</assemblyBinding >
</runtime>
<configuratio n>

If the codebehind for an ASPX file is compiled into the assembly in Foo/bin,
the @ Assembly directive can be used to link the two:

<%@ Assembly Name="Foo" %>
<%@ Import Namespace="FooN amespace" %>
<%@ Page language="c#" Codebehind="Foo .aspx.cs" AutoEventWireup ="false" Inherits="FooNa mespace.FooWebF orm"
"%>

--
Scott

http://www.OdeToCode.com/blogs/scott/

[color=blue]
> Bruce,
>
> This is an interesting topic.
>
> It would seem that
> http://msdn.microsoft.com/library/de...ry/en-us/cpgen
> ref/html/gngrfCodeBase.a sp
> 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/de...ry/en-us/cpgui
> de/html/cpconconfigurin gieapplications .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\Wwwr oot\Webapps\Sto ckCalc.
>
> Putting <probing privatePath="bi n"/> in the configuration file
> causes the runtime to search for assemblies in
> C:\Inetpub\Wwwr oot\Webapps\Sto ckCalc\Bin
> as well as C:\Inetpub\Wwwr oot\Webapps\Sto ckCalc."
> The path "C:\Inetpub\Www root\Webapps\St ockCalc\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
> ===========
> "bruce barker" <nospam_brubar@ safeco.com> wrote in message
> news:%23zAc3u1$ EHA.3824@TK2MSF TNGP10.phx.gbl. ..[color=green]
>> no its not.
>>
>> this is probably because the dll's are needed for the page compile
>> first.
>> the compiler references are specified in the <assemblies> section
>> (which
>> asp.net passes to the compiler thru switches when it spawns it).
>> unfortunately you can only specify the name in the <assemblies>
>> section,
>> not
>> the path, as this is specified with the compiler lib switch.
>> -- bruce (sqlwork.com)
>>
>> "Subra Mallampalli" <subra_nospam_m allampalli@news groups.nospam>
>> wrote in
>> message news:%233asbgz$ EHA.3336@TK2MSF TNGP11.phx.gbl. ..
>> | Hi,
>> |
>> | I am trying to use <runtime> section within the web.config file.
>> However,
>> | the contents of the <runtime> section seem to be ignored. What am i
>> missing
>> | here? Is <runtime> section not used by web apps?
>> |
>> | Any help is greatly appreciated.
>> |
>> | Thanks,
>> |
>> | Subra
>> |
>> |[/color][/color]

[Subra Mallampalli]

Re: using &lt;runtime& gt; section in web.config file

Scott,

Thanks! the Assembly directive was the piece I was missing. I was thinking
that the framework would automatically probe all the folders specified in
<probing> and try to load the type, but it seems that it doesn't do that.

If I were to specify the full type for the inherits attribute of the page
directive (Inhertis="FooN amespace.FooWeb Form, FooAssemblyName "), it works
like a charm. With this change, I dont need the assembly or the imports
directives (we use XSL transforms and our aspx pages have no code).

However the <runtime> tag is effective only in the web.config file in the
application folder (and not in the subfolders). So, if i want to maintain
sub applications in subfolders with their own bin folders, I will have to
modify the root web.config file to include details about every subfolder.

Also, it is not clear to me if a dll change in one of the probing folders
would automatically reload the entire web application.

Thanks, again!

Subra

"Scott Allen" <scott@nospam.O deToCode.com> wrote in message
news:5552863241 8949601122800@m snews.microsoft .com...[color=blue]
> Yes, what you can do is specify another subdir to probe for assemblies,[/color]
ie:[color=blue]
>
> <configuratio n>
> <runtime>
> <assemblyBindin g xmlns="urn:sche mas-microsoft-com:asm.v1">
> <probing privatePath="Fo o/bin" />
> </assemblyBinding >
> </runtime>
> <configuratio n>
>
> If the codebehind for an ASPX file is compiled into the assembly in[/color]
Foo/bin,[color=blue]
> the @ Assembly directive can be used to link the two:
>
> <%@ Assembly Name="Foo" %>
> <%@ Import Namespace="FooN amespace" %>
> <%@ Page language="c#" Codebehind="Foo .aspx.cs" AutoEventWireup ="false"[/color]
Inherits="FooNa mespace.FooWebF orm"[color=blue]
> "%>
>
> --
> Scott
> http://www.OdeToCode.com/blogs/scott/
>[color=green]
> > Bruce,
> >
> > This is an interesting topic.
> >
> > It would seem that
> > http://msdn.microsoft.com/library/de...ry/en-us/cpgen
> > ref/html/gngrfCodeBase.a sp
> > 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/de...ry/en-us/cpgui
> > de/html/cpconconfigurin gieapplications .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\Wwwr oot\Webapps\Sto ckCalc.
> >
> > Putting <probing privatePath="bi n"/> in the configuration file
> > causes the runtime to search for assemblies in
> > C:\Inetpub\Wwwr oot\Webapps\Sto ckCalc\Bin
> > as well as C:\Inetpub\Wwwr oot\Webapps\Sto ckCalc."
> > The path "C:\Inetpub\Www root\Webapps\St ockCalc\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
> > ===========
> > "bruce barker" <nospam_brubar@ safeco.com> wrote in message
> > news:%23zAc3u1$ EHA.3824@TK2MSF TNGP10.phx.gbl. ..[color=darkred]
> >> no its not.
> >>
> >> this is probably because the dll's are needed for the page compile
> >> first.
> >> the compiler references are specified in the <assemblies> section
> >> (which
> >> asp.net passes to the compiler thru switches when it spawns it).
> >> unfortunately you can only specify the name in the <assemblies>
> >> section,
> >> not
> >> the path, as this is specified with the compiler lib switch.
> >> -- bruce (sqlwork.com)
> >>
> >> "Subra Mallampalli" <subra_nospam_m allampalli@news groups.nospam>
> >> wrote in
> >> message news:%233asbgz$ EHA.3336@TK2MSF TNGP11.phx.gbl. ..
> >> | Hi,
> >> |
> >> | I am trying to use <runtime> section within the web.config file.
> >> However,
> >> | the contents of the <runtime> section seem to be ignored. What am i
> >> missing
> >> | here? Is <runtime> section not used by web apps?
> >> |
> >> | Any help is greatly appreciated.
> >> |
> >> | Thanks,
> >> |
> >> | Subra
> >> |
> >> |[/color][/color]
>
>[/color]

[Scott Allen]

Re: using &lt;runtime& gt; section in web.config file

Hi Subra:

Glad to help out.

As for the last question (does a overwriting an assembly in the probing folder
reload the app?) - I'm not sure. My guess is no.

I'm pretty sure the runtime won't even shadow copy these assemblies because
only the bin directory is setup for shadow copy. You might not be able to
overwrite those assemblies without an iisreset. Not 100% sure on this however
- would need to verify with an experiment.

--
Scott

http://www.OdeToCode.com/blogs/scott/

[color=blue]
> Scott,
>
> Thanks! the Assembly directive was the piece I was missing. I was
> thinking that the framework would automatically probe all the folders
> specified in <probing> and try to load the type, but it seems that it
> doesn't do that.
>
> If I were to specify the full type for the inherits attribute of the
> page directive (Inhertis="FooN amespace.FooWeb Form, FooAssemblyName "),
> it works like a charm. With this change, I dont need the assembly or
> the imports directives (we use XSL transforms and our aspx pages have
> no code).
>
> However the <runtime> tag is effective only in the web.config file in
> the application folder (and not in the subfolders). So, if i want to
> maintain sub applications in subfolders with their own bin folders, I
> will have to modify the root web.config file to include details about
> every subfolder.
>
> Also, it is not clear to me if a dll change in one of the probing
> folders would automatically reload the entire web application.
>
> Thanks, again!
>
> Subra
>
> "Scott Allen" <scott@nospam.O deToCode.com> wrote in message
> news:5552863241 8949601122800@m snews.microsoft .com...
>[color=green]
>> Yes, what you can do is specify another subdir to probe for
>> assemblies,
>>[/color]
> ie:
>[color=green]
>> <configuratio n>
>> <runtime>
>> <assemblyBindin g xmlns="urn:sche mas-microsoft-com:asm.v1">
>> <probing privatePath="Fo o/bin" />
>> </assemblyBinding >
>> </runtime>
>> <configuratio n>
>> If the codebehind for an ASPX file is compiled into the assembly in
>>[/color]
> Foo/bin,
>[color=green]
>> the @ Assembly directive can be used to link the two:
>>
>> <%@ Assembly Name="Foo" %>
>> <%@ Import Namespace="FooN amespace" %>
>> <%@ Page language="c#" Codebehind="Foo .aspx.cs"
>> AutoEventWireup ="false"[/color]
> Inherits="FooNa mespace.FooWebF orm"
>[color=green]
>> "%>
>>
>> --
>> Scott
>> http://www.OdeToCode.com/blogs/scott/[color=darkred]
>>> Bruce,
>>>
>>> This is an interesting topic.
>>>
>>> It would seem that
>>> http://msdn.microsoft.com/library/de...rary/en-us/cpg
>>> en
>>> ref/html/gngrfCodeBase.a sp
>>> 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/de...rary/en-us/cpg
>>> ui de/html/cpconconfigurin gieapplications .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\Wwwr oot\Webapps\Sto ckCalc.
>>>
>>> Putting <probing privatePath="bi n"/> in the configuration file
>>> causes the runtime to search for assemblies in
>>> C:\Inetpub\Wwwr oot\Webapps\Sto ckCalc\Bin
>>> as well as C:\Inetpub\Wwwr oot\Webapps\Sto ckCalc."
>>> The path "C:\Inetpub\Www root\Webapps\St ockCalc\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
>>> ===========
>>> "bruce barker" <nospam_brubar@ safeco.com> wrote in message
>>> news:%23zAc3u1$ EHA.3824@TK2MSF TNGP10.phx.gbl. ..
>>>> no its not.
>>>>
>>>> this is probably because the dll's are needed for the page compile
>>>> first.
>>>> the compiler references are specified in the <assemblies> section
>>>> (which
>>>> asp.net passes to the compiler thru switches when it spawns it).
>>>> unfortunately you can only specify the name in the <assemblies>
>>>> section,
>>>> not
>>>> the path, as this is specified with the compiler lib switch.
>>>> -- bruce (sqlwork.com)
>>>> "Subra Mallampalli" <subra_nospam_m allampalli@news groups.nospam>
>>>> wrote in
>>>> message news:%233asbgz$ EHA.3336@TK2MSF TNGP11.phx.gbl. ..
>>>> | Hi,
>>>> |
>>>> | I am trying to use <runtime> section within the web.config file.
>>>> However,
>>>> | the contents of the <runtime> section seem to be ignored. What am
>>>> i
>>>> missing
>>>> | here? Is <runtime> section not used by web apps?
>>>> |
>>>> | Any help is greatly appreciated.
>>>> |
>>>> | Thanks,
>>>> |
>>>> | Subra
>>>> |
>>>> |[/color][/color][/color]