Hi
I dont think that u need to rename the assemblies. In
fact if i remember right, if the name of an assembly is
changed after it was compiled, then it will throw an
exception.
Do note that ".Net by default looks for the same version
of the assembly even if a new version is available. So i
think if u use the structure properly you can achieve
this."
so you can achieve what you want by
Build the AssemblyB with Version X of AssemblyD
Build the AssemblyC with Version Y of AssemblyD
1)Place the different versions of Assembly D in the
different subdirectories of the bin folder with the
version name as the sub-directory name.
2) Then use the CodeBase Element in the Config file to
specify the File Path for each version of Assembly D
When ur app is run, Assembly B will search with Version X
of AssemblyD( coz that was how it was built) and the code
base will ensure that it gets the version X
As Assembly C was built with Version Y of Assembly D,
this Version Y will be searched and again code base will
ensure that the correct version is got
Check out the links
General Notes on Assembly Location :
http://msdn.microsoft.com/library/default.asp?
url=/library/en-
us/cpguide/html/cpconhowruntimelocatesassemblies.asp
Locating the Assembly through Codebases :
http://msdn.microsoft.com/library/default.asp?
url=/library/en-
us/cpguide/html/cpconstep4locatingassemblythroughcodebaseso
rprobing.asp
How to Specify Code Base :
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/cpgenref/html/gngrfcodebase.asp
regards,
sr
-----Original Message-----
We have a situation where we have decided (in an attempt
to keep thingssimple) to stick to local assemblies rather than global
ones.However we now have the following situation looming
AssyA depends on AssyB depends on AssyD version 1
AssyA depends on AssyC depends on AssyD version 2
Obviously we cannot copy both versions of AssyD to the
AssyA's bindirectory. Is the only sensible way around this (rather
than going the GACroute) to name the Assemblies by version number (e.g.
AssyD001 andAssyD002).
How much of a development pain is the GAC route - all
that key generationstuff seems overkill for our 'local' libraries.
Many Thanks.
.