Same assembly in different deployments

[Preben Zacho]

This is probably a very basic question.

I have created a class library, when builded it produces a dll called
test.dll. This dll I use as reference in many different applications. When I
create a deployment project, this dll is added to the output and is shipped
with the application.

When installed, the dll is placed in the same directory as the application
exe file. So for each application the same dll is deployed and therefor the
same assembly is placed in many different directories.

So the thing is: How can I change the setup/code/properties so the
application will look in a different directory for this particular assembly
at runtime, while it look for other assemblies in the application path?

Please note, that it is not an option to install ALL applications in the
same directory.

TIA

PZ

[Mythran]

"Preben Zacho" <[e-mail]> wrote in message
news:Os**************@TK2MSFTNGP05.phx.gbl...

This is probably a very basic question.

I have created a class library, when builded it produces a dll called
test.dll. This dll I use as reference in many different applications. When
I create a deployment project, this dll is added to the output and is
shipped with the application.

When installed, the dll is placed in the same directory as the application
exe file. So for each application the same dll is deployed and therefor
the same assembly is placed in many different directories.

So the thing is: How can I change the setup/code/properties so the
application will look in a different directory for this particular
assembly at runtime, while it look for other assemblies in the application
path?

Please note, that it is not an option to install ALL applications in the
same directory.

TIA

PZ

So, instead of xcopy deployment? You can use the GAC (Global Assembly
Cache) ... look it up on MSDN and do a search for GAC.

Mythran