On Tue, 14 Mar 2006 00:39:20 -0600, Sebastian Good <[EMAIL PROTECTED]> wrote:
Sort of. On Windows XP and above, If you know the third party you can supply (or modify an existing) manifest to point it to your com object. But, the article quoted below implies that the COM object must be unmanaged (not sure why that restriction is there). Configuring COM Components for Registration-Free Activation http://msdn2.microsoft.com/en-us/library/x65a421a(VS.80).aspx >Along these lines, and I suspect this *is* a stupid question... > >If a third party expects to load COM objects by GUID, but we don't have >access to the registry to register our components, can we still have a >.NET interop object conjured up in its place? It seems to go against >everything that is right and good (if there is any in the COM world), >but I figured I'd see if anyone had brilliant ideas. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
