Jimbo,
In addition to what Mike was saying (regarding understanding what's been
generated), the WiX source files should be created during the development
phase of a project (early). The wxs files will be developed as the project
is developed, I would consider it one of the most important parts of a
project (since if the installer isn't working correctly, the rest doesn't
matter). After that, the wxs files should remain relatively static.
Automated builds are necessary, however automated builds that change the WiX
files is dangerous (in my opinion, I guess it depends on the situation too).
InstallShield does things like "COM Extract at Build", which is useful but I
find the cleanliness of WiX more suitable for smaller projects.
I hope this helps,
David.
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Collins, James
Sent: Wednesday, 1 August 2007 5:58 AM
To: Mike Dimmick; David Howell; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Wix 3.0.2925 heat TypeLib RegistryValue
Hey mike,
What would you consider the future of heat? I don't see heat as
a starting point at all, I see it as a beginning of an automated build
extractor/creator. I know its not there yet, but its really not that far
off. I need create installers (out of TFS) daily in a repeatable and
manageable way. Right now I'm using wise which works but is limited, I'm
looking towards WIX because I see it's potential to solve many of the issues
I have right now with an automated build process. The truth be told in this
day and age, I can't believe solutions are not available out there to do
this, it sounds simple enough. This is the holy grail of installer tech, if
WIX cracks this nut it will quickly make everything else obsolete.
Jimbo
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick
Sent: Tuesday, July 31, 2007 12:58 PM
To: 'David Howell'; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Wix 3.0.2925 heat TypeLib RegistryValue
Generally you should consider Heat's output as a starting point, not a final
product. You need to understand what's been generated.
Heat captures the raw registry output from running the DllRegisterServer
output; it then transforms what's been harvested into the higher-level
values. Anything left as RegistryValue elements was written by the DLL but
didn't match the TypeLib information. Could you post what's shown?
If you're not already doing so, I would recommend using VB's Binary
Compatibility setting to ensure that the GUIDs are stable as far as
possible.
--
Mike Dimmick
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Howell
Sent: 31 July 2007 01:03
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix 3.0.2925 heat TypeLib RegistryValue
Hello,
I've been using WiX 3.0.2925 to install some of our COM DLLs (created by
Visual Basic 6.0 SP6).
With WiX 3.0.2925 when I use:
"heat file MyLibrary.dll -out MyLibrary.wxs"
I will often get a mixture of <TypeLib> entries (which is what I want) and a
mixture of <RegistryValue> entries (which seem to be instead of other
<TypeLib> entries).
This makes it very difficult to edit a wxs file when interfaces have changed
etc.
Is there any way to force heat to produce only the <TypeLib> entries?
Cheers,
David.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
