Mike Dimmick wrote:
> I still don't really understand why the Class table is being
> de-emphasised. I suppose it's possible that if you advertise a Class -
> say for a feature that is installed on first use - that that feature
> will be installed if some third-party program references it, which cou
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Johan
Appelgren
Sent: 26 September 2006 09:58
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Installing COM components
Thank you for your response.
In what way would automatic generation be more
have I misunderstood something?
--
Mike Dimmick
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 25 September 2006 18:05
To: Mike Dimmick
Cc: Johan Appelgren; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Installing COM components
Mike Dimmick wrote:
> You
e
> assembly. This causes the Framework to use that version number when
> computing the GUIDs and therefore the GUIDs are stable across versions.
>
> --
> Mike Dimmick
>
> -Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Johan
>
Mike Dimmick wrote:
> You can use the Class table to take away some of the pain of creating
> the registry entries, although Rob Mensching has some reservations with
> this apparently. I'm not quite sure why. The SDK currently calls out the
> Typelib table as having problems with rollback. Using th
]
[mailto:[EMAIL PROTECTED] On Behalf Of Johan
Appelgren
Sent: 22 September 2006 13:03
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installing COM components
Hi,
I'm looking at using wix to create an installer for an application that
consists of both .NET assemblies and COM. A
Hi,
I'm looking at using wix to create an installer for an application
that consists of both .NET assemblies and COM. As far as I can tell if
I want to try wix3 I'm supposed to use heat to generate wxs files for
the COM components and their primary interop assemblies.
During the development there
Not really. Tallow pulls a bunch of VB6 properties, and additional registry
info, which creates additional issues, like possibly blowing up VB with an
uninstall.
In this case the MSI created by VS.NET only conatins those keys necessary to
install the single object.
--
View this message in con
jdrake, your suggestion is essentially the same as using tallow to extract the COM infromation...On 7/3/06, jdrake <
[EMAIL PROTECTED]> wrote:I should qualify my answer. IF you are only installing the components
themselves, and NOT a COM+ Application, then you should use the .NET IDE tocreate an i
I should qualify my answer. IF you are only installing the components
themselves, and NOT a COM+ Application, then you should use the .NET IDE to
create an installer, and set the Register type to vsdrfCOM, and THEN run
dark on the MSI to reverse engineer the registry entries.
My WIX file looks l
At this point I haven't seen any of this work, at least with VB 6 components,
none of the MSIs I've seen actually uninstall the thing. Including those
generated by the .NET IDE.
If you care about leave the machine in a known good state, good luck.
--
View this message in context:
http://www.na
applications_an
d_side_by_side_assemblies_start_page.asp?frame=true
> -Original Message-
> From: Bill Arnette [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 30, 2006 9:59 AM
> To: 'wix-users@lists.sourceforge.net'
> Subject: RE: [WiX-users] Installing COM components
>
> Ta
Tallow is intended to be used one time to aid in the initial creation of MSI
components for the COM components you need to install. It is not intended
to be used in an automated build.
The idea is to run Tallow to harvest the components, including registry
entries, and then hand-edit them to ad
Is there any better way of installing COM components instead of using
tallow.exe and the related WiX fragment from the output?
I am wrinting at a nant script at the moment for building the setup. Now
I want insert the installation of my COM components. The problem is that
the output from tallow
14 matches
Mail list logo
