Hi Cetin and Einar,

Thank you both for you pointers and ideas. That was exactly what I needed.

Time to hit the books (again)

Alex


>Check "Structuring a .NET Application For Easy Deployment","Basic Instincts: Deploying Assemblies", "Deploying Multiple Versions of an Application or Component", "Simplifying Deployment and Solving DLL Hell with the .NET Framework", "Packaging and Deploying Resources",KB324168, KB315682 ... on MSDN.
>
>A few lines from first source as is:
>"Shared Assemblies
>Often, an assembly is required by more than one application or even a host of unknown applications. When this is the case, it is desirable not to have to deploy the assembly privately with every application, but rather to make it available to any application that needs it. The .NET Framework makes this possible through shared assemblies.
>
>The Global Assembly Cache
>Shared assemblies are commonly installed in the Global Assembly Cache (GAC). The GAC is a machine-wide store of assemblies.
>
>Because assemblies stored in the GAC are public, they must have what is called a strong name, which is made up of the assembly actual name, version (discussed in the next section), culture, and public/private key pair."
>Cetin