I'm working on an application which consists of both managed and unmanaged parts. The app itself is huge (fileset is several hundreds of megabytes on disk), so I don't really want to push it to the GAC just to make it available as an assembly for other .NET clients to consume. Instead, I'm looking for a way to make the assembly information for the app publicly available without dumping all of the code into the GAC.
I came across regasm's /codebase option which at first looked like the solution to the problem. But when I tried it, it turned out to work differently than I had expected it. Can anybody shed more light on how the /codebase option works and which problem it is supposed to solve? Any experiences?
From what I've seen, my assumption is that regasm /codebase is useful for COM clients which want to call objects in .NET code; they do this by looking up the registry for the server DLL (in this case, mscoree.dll), and when mscoree.dll starts, it knows where to search the actual assembly by checking the codebase entry in the registry.
However, I'm looking for a similar solution for .NET-based clients, i.e. I want a .NET client to find my assembly even though it is not in the GAC. (The .NET clients can be anywhere, not just in the app's installation directory, so private assemblies are not sufficient in this case.)
Any hints or pointers most welcome.
Thanks!
Claus
[EMAIL PROTECTED] Claus Brod, CoCreate R&D Have you hugged your manager today? CoCreate Software GmbH Phone: +49 7031 951 2152 http://www.cocreate.com Fax: +49 7031 951 6152 --http://clausbrod.com --------------------------#include <disclaimer>--
=================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in:
NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls
View archives and manage your subscription(s) at http://discuss.develop.com
