Hi Adam,
My build scenario is even more difficult than yours. You may have seen
my email earlier about my blight. Our product has 3 levels of
inheritance (with room for more) each with customizations adding to the
previous tier spanning across .net code, databases, reporting services,
etc. I have incorporated wix libraries at the lowest level for the UI
and first level components, The next tier has its fragments of
components, custom actions, etc build upon the first and the last tier
adds the remaining components and has the wix project building the msi.
I have come across all sorts of problems, because each one is a separate
project in our source control (TFS) each with its own build automation
and so the 'paths' to the files/binaries is different from the first
time it builds the wixlib which binds in all the file paths (and not the
actual files). Then when the second tier goes through it can't find it
at ..\..\..\..\..\binaries (because the build automation is occurring in
another directory and the source files have been moved to the companies
drop location. I can't use full paths either because the build
automation cleans builds project files and the setup project for the
first tier, moves it to drop location, cleans up. So first build cant
reference finished path (not there yet) and second build cant access the
other builds prelim area (its deleted).
Basically for a compromise I am sadly copying and pasting the projects
containing the fragment with files around and modifying pre-compiler
variables for paths. The UI fragments with localization can be linked
from the wixlib as I made a modification to the UIWiX_Common to remove
the binary tags, and I basically include the binary tags in my .msi
project so I can get the paths right.
In the end it does feel like a big hack, so I'm trying to figure out how
to bind the files into the wixlib or even create extension dll to try
and mimic what UIExtensions.dll does which has all the dialog files in
it. (If anyone could tell me or look at my previous email please? :P)
Once I have things more under control and less 'hacky' I'd be happy to
explain more how we did things.
Best of luck,
Murray
Date: Thu, 17 Jul 2008 14:29:39 +0100
From: Adam Connelly <[EMAIL PROTECTED]>
Subject: Re: [WiX-users] Wix and MSBuild
To: General discussion for Windows Installer XML toolset.
<wix-users@lists.sourceforge.net>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
I actually sorted the problem (a typo :(). I would still be interested
to find out how others structure their projects.
Adam
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Adam
Connelly
Sent: 17 July 2008 11:19
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix and MSBuild
Hi,
I currently trying to add a task into my MSBuild file that will create
the various MSI files needed for the project. I've got the following
file structure:
Root/
Build.xml
Code/
Deploy/
ProjA
ProjB
Installs/
ProjA.wxs
Sorry if that's not amazingly clear. Basically, all the assemblies, etc
for each project are in Code/Deploy/ProjX, and the wix file is in
Installs/ProjX.wxs. I want to be able to build an installer while
keeping this structure if possible.
The problem I'm having is that although candle.exe runs fine, light.exe
can't seem to find the source files no-matter if I set the -b switch, or
if I alter the Source attributes in the wxs file.
I guess what I really want to know is how do other people structure
their builds when there may be multiple projects needing installers
built, etc.
Sorry for such a broad question.
Cheers,
Adam
------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
This e-mail and any attachments to it (the "Communication") are confidential
and are for the use only of the intended recipient. The Communication may
contain copyright material of the Snowden Group ("Snowden"), or any of its
related entities or of third parties. If you are not the intended recipient of
the Communication, please notify the sender immediately by return e-mail,
delete the Communication, and do not copy, print, retransmit, disclose, store
or act in reliance on the Communication. Any views expressed in the
Communication are those of the individual sender only, unless expressly stated
to be those of Snowden. Although virus protection devices and procedures are in
place, Snowden does not guarantee the integrity of the Communication, or that
it is free from errors, viruses or interference. Snowden advises email
recipients to carry out their own virus checks before opening any attachment.
Please note that the main telephone number for the Snowden Perth office has ch
anged to +61 8 9213 9213.
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
