-----------------------------------------------------------
New Message on BDOTNET
-----------------------------------------------------------
From: SitaramanM
Message 3 in Discussion
Hi Akshit Though the Private Bin path will work, it is used for storing private
assemblies in a directory other than the ones searched by default and assist at the
time of assembly probing. However using the privatebinpath for the problem posted by
Eeswar will lead to having a buggy version in the gac existing + a new version as a
private assembly which is not good deployment technique. Do note that the new version
will be a private assembly. On top of it , this will also not ensure that the
existing clients will use the new assembly(.Net client apps will by default use the
same assembly(Name+version+culture+publickey) with which they were built) The
recommended solution for the problem would be to use the BindingRedirect Element in
the config file. This element when specified will redirect the request for an older
version of an assembly to a new version as specified Redirects one assembly
version to another.
<configuration>
<runtime>
<assemblyBinding>
<dependentAssembly>
<bindingRedirect><bindingRedirect oldVersion="old assembly version"
newVersion="new assembly version"/> Required Attributes Attribute Description
oldVersion Specifies the version of the assembly that was originally requested. The
format of an assembly version number is major.minor.build.revision. Valid values for
each part of this version number are 0 to 65535.
You can also specify a range of versions in the following format:
n.n.n.n - n.n.n.n newVersion Specifies the version of the assembly to use instead of
the originally requested version in the format: n.n.n.n Remarks
When you build a .NET Framework application against a strong-named assembly, the
application uses that version of the assembly at run time by default, even if a new
version is available. However, you can configure the application to run against a
newer version of the assembly. For details on how the runtime uses these files to
determine which assembly version to use, see <MSHelp:link tabIndex=0
keywords="cpconHowRuntimeLocatesAssemblies">How the Runtime Locates
Assemblies</MSHelp:link>.
You can redirect more than one assembly version by including multiple
<bindingRedirect> elements in a <dependentAssembly> element. Example hth regards,
sr
-----------------------------------------------------------
To stop getting this e-mail, or change how often it arrives, go to your E-mail
Settings.
http://groups.msn.com/BDotNet/_emailsettings.msnw
Need help? If you've forgotten your password, please go to Passport Member Services.
http://groups.msn.com/_passportredir.msnw?ppmprop=help
For other questions or feedback, go to our Contact Us page.
http://groups.msn.com/contact
If you do not want to receive future e-mail from this MSN group, or if you received
this message by mistake, please click the "Remove" link below. On the pre-addressed
e-mail message that opens, simply click "Send". Your e-mail address will be deleted
from this group's mailing list.
mailto:[EMAIL PROTECTED]
