Does this still imply I need to hand-maintain something after the 
initial build?

Would this limit us from doing things like automated daily builds of 
blead/svn versions and so on?

We'd also like to allow for "subclassing" of product installations.

While we build two basic installs (purist experimental, and a 
user-focused version that bundles some basic additions) we would like to 
allow for customized builds derived from ours, and it would seem that 
anything that requires me to maintain anything by hand long term is a 
significant reduction in functionality from what we get with Inno Setup 
Script generation.

Of course, moving to .msi is slightly more important than the dynamic 
build process, but that would still mean we could only offer .msi 
install in our "official" build, and out others could only get "reduced 
functionality"...

Am I right here though in thinking that the fundamental issue with 
dynamic generation is to do with guid and component state over time?

Could I avoid this problem by generation a guid state cache for 
components automatically instead of maintaining it by hand?

Adam K
> Hi Adam,
>
> one point to look might be the enhanced tallow tool named 'mallow' which is
> inteded to create consistent guids on subsequent calls. But both are
> designed for Wix 2.0 only.
>
> My suggestion is following:
> - Use heat (v3.0) to crawl your directories as your starting point
> - Adjust all entries to your needs
>
> - When it comes to an upgrade then just run wix, do an administrative
> install an compare this directory with your base one. As result you will get
> a list which files are missing in install. (Wix will show obsolete files)
> - This missing files then must be added to your wxs files (which should not
> be a issue since you might use perl)
>
> for comparing the install to your base see
> http://www.nabble.com/Wix-layout-td12592040.html for a batch and a nant
> solution.
>   

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to