#x27;t find it in the archives..)
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Geoff
Finger
Sent: Friday, October 27, 2006 3:24 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Installing shared assemblies
On Fri, 27 Oct
On Fri, 27 Oct 2006, Phil Wilson wrote:
> If you have a .NET assembly exposing COM interfaces you don't need an
> interop Dll, but you need it registering in the same general way that
> Regasm does (there's Tallow). Gacutil just puts it in the GAC. What you
> get for a registered .NET assembly are
@lists.sourceforge.net
Subject: Re: [WiX-users]
Installing shared assemblies
I'm pretty sure you get a
bunch of ICE 33 warnings with the typelib registry entries over the TypeLib
table. I can vouch that the Registry Table route works. It is, I believe, the
generally (arguably?) preferred w
Wilson, Phil wrote:
> I'm not sure whether Wix prefers type library registration with the
> Registry table or with the TypeLib table.
>
WiX turns TypeLib (et al) authoring into Registry rows unless Advertise
is explicitly set to Yes.
--
sig://boB
http://bobs.org
--
I'm pretty sure you get a bunch of ICE 33 warnings with the typelib registry entries over the TypeLib table. I can vouch that the Registry Table route works. It is, I believe, the generally (arguably?) preferred way so msiexec can track the registry entries and uninstall them. But I needn't tell yo
If you have a .NET assembly exposing COM interfaces you don't need an
interop Dll, but you need it registering in the same general way that
Regasm does (there's Tallow). Gacutil just puts it in the GAC. What you
get for a registered .NET assembly are CLSID/{Guid} entries that show
mscoree.dll as th
6 matches
Mail list logo