PC Review


Reply
Thread Tools Rate Thread

ASP.NET and dll

 
 
Silvia
Guest
Posts: n/a
 
      15th Dec 2003
I have a ASP.NET web application in
c:\inetpub\wwwroot\webnet directory and I have de dll in
c:\program Files\filesdll, is posible that this
dll aren't into de \bin directory?? Can I configurate that
in de web.config file??

Please e-mail me at (E-Mail Removed)

Silvia
 
Reply With Quote
 
 
 
 
Jan Tielens
Guest
Posts: n/a
 
      15th Dec 2003
This can be done by altering the config file and using the <codebase/> node:

<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="myAssembly"
publicKeyToken="32ab4ba45e0a69a1"
culture="neutral" />
<codeBase version="2.0.0.0"
href="http://www.litwareinc.com/myAssembly.dll"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>

For the runtime to use the <codeBase> setting in a machine configuration
file or publisher policy file, the file must also redirect the assembly
version. Application configuration files can have a codebase setting without
redirecting the assembly version. After determining which assembly version
to use, the runtime applies the codebase setting from the file that
determines the version. If no codebase is indicated, the runtime probes for
the assembly in the usual way.

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.

For assemblies without a strong name, version is ignored and the loader uses
the first appearance of <codebase> inside <dependentAssembly>. If there is
an entry in the application configuration file that redirects binding to
another assembly, the redirection will take precedence even if the assembly
version doesn't match the binding request.

Source: MSDN

http://msdn.microsoft.com/library/de...rfcodebase.asp


--
Greetz,
Jan
__________________________________
Read my weblog: http://weblogs.asp.net/jan
"Silvia" <(E-Mail Removed)> schreef in bericht
news:07bd01c3c31b$2a0a0960$(E-Mail Removed)...
> I have a ASP.NET web application in
> c:\inetpub\wwwroot\webnet directory and I have de dll in
> c:\program Files\filesdll, is posible that this
> dll aren't into de \bin directory?? Can I configurate that
> in de web.config file??
>
> Please e-mail me at (E-Mail Removed)
>
> Silvia



 
Reply With Quote
 
Silvia
Guest
Posts: n/a
 
      16th Dec 2003
Hi, this is the solution to redirect to another dll that
isnt't in \bin folder, but what is publicKeyToken? and can
I obtain this value?

thanks
>-----Original Message-----
>This can be done by altering the config file and using

the <codebase/> node:
>
><configuration>
> <runtime>
> <assemblyBinding xmlns="urn:schemas-microsoft-

com:asm.v1">
> <dependentAssembly>
> <assemblyIdentity name="myAssembly"
>

publicKeyToken="32ab4ba45e0a69a1"
> culture="neutral" />
> <codeBase version="2.0.0.0"
>

href="http://www.litwareinc.com/myAssembly.dll"/>
> </dependentAssembly>
> </assemblyBinding>
> </runtime>
></configuration>
>
>For the runtime to use the <codeBase> setting in a

machine configuration
>file or publisher policy file, the file must also

redirect the assembly
>version. Application configuration files can have a

codebase setting without
>redirecting the assembly version. After determining which

assembly version
>to use, the runtime applies the codebase setting from the

file that
>determines the version. If no codebase is indicated, the

runtime probes for
>the assembly in the usual way.
>
>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.
>
>For assemblies without a strong name, version is ignored

and the loader uses
>the first appearance of <codebase> inside

<dependentAssembly>. If there is
>an entry in the application configuration file that

redirects binding to
>another assembly, the redirection will take precedence

even if the assembly
>version doesn't match the binding request.
>
>Source: MSDN
>
>http://msdn.microsoft.com/library/default.asp

url=/library/en-us/cpgenref/html/gngrfcodebase.asp
>
>
>--
>Greetz,
>Jan
>__________________________________
>Read my weblog: http://weblogs.asp.net/jan
>"Silvia" <(E-Mail Removed)> schreef in bericht
>news:07bd01c3c31b$2a0a0960$(E-Mail Removed)...
>> I have a ASP.NET web application in
>> c:\inetpub\wwwroot\webnet directory and I have de dll in
>> c:\program Files\filesdll, is posible that this
>> dll aren't into de \bin directory?? Can I configurate

that
>> in de web.config file??
>>
>> Please e-mail me at (E-Mail Removed)
>>
>> Silvia

>
>
>.
>

 
Reply With Quote
 
Guest
Posts: n/a
 
      17th Dec 2003
hi,

Whit this solution the dlls the bin directory not
disapear?? because if delete bin directory the application
not run.

thanks


>-----Original Message-----
>This can be done by altering the config file and using

the <codebase/> node:
>
><configuration>
> <runtime>
> <assemblyBinding xmlns="urn:schemas-microsoft-

com:asm.v1">
> <dependentAssembly>
> <assemblyIdentity name="myAssembly"
>

publicKeyToken="32ab4ba45e0a69a1"
> culture="neutral" />
> <codeBase version="2.0.0.0"
>

href="http://www.litwareinc.com/myAssembly.dll"/>
> </dependentAssembly>
> </assemblyBinding>
> </runtime>
></configuration>
>
>For the runtime to use the <codeBase> setting in a

machine configuration
>file or publisher policy file, the file must also

redirect the assembly
>version. Application configuration files can have a

codebase setting without
>redirecting the assembly version. After determining which

assembly version
>to use, the runtime applies the codebase setting from the

file that
>determines the version. If no codebase is indicated, the

runtime probes for
>the assembly in the usual way.
>
>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.
>
>For assemblies without a strong name, version is ignored

and the loader uses
>the first appearance of <codebase> inside

<dependentAssembly>. If there is
>an entry in the application configuration file that

redirects binding to
>another assembly, the redirection will take precedence

even if the assembly
>version doesn't match the binding request.
>
>Source: MSDN
>
>http://msdn.microsoft.com/library/default.asp?

url=/library/en-us/cpgenref/html/gngrfcodebase.asp
>
>
>--
>Greetz,
>Jan
>__________________________________
>Read my weblog: http://weblogs.asp.net/jan
>"Silvia" <(E-Mail Removed)> schreef in bericht
>news:07bd01c3c31b$2a0a0960$(E-Mail Removed)...
>> I have a ASP.NET web application in
>> c:\inetpub\wwwroot\webnet directory and I have de dll in
>> c:\program Files\filesdll, is posible that this
>> dll aren't into de \bin directory?? Can I configurate

that
>> in de web.config file??
>>
>> Please e-mail me at (E-Mail Removed)
>>
>> Silvia

>
>
>.
>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off



Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 11:25 AM.