I would imagine that you would need two projects, one for each package. You
can have both projects in the same solution. However, some versions of
Visual Studio misbehave if you have multiple projects with the same output
directory (though that may just apply to C# or VB).
I would recommend using the same Fragments for the main body of your
installation to ensure that you're not making component errors. If a
resource (such as a file) is installed to the same location by two different
components (identified by component GUID), Bad Things can happen.
--
Mike Dimmick
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Friedrich,
Oliver
Sent: 15 November 2006 10:38
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Votive V3 and multiple .msi support?
Hello again,
Using Votive V3 is pretty nice, though one thing is a little bit anoying...
For our Solution we need to build 2 packages, one for the client and one for
the server application. Those packages use pretty much the same code, thats
why they are in one Solution of VS2005. Now, much WiX-code could be shared
between those to packages, too. So i thought it would be enough, do add
another .wxs file to the Votive V3 project, to get it build a second .msi,
but that does not work, Votive complains about double entry points.
Is it possible, to share WiX-code for two Setups in one Votive Solution? I
have at least 10 files, that are used by both setup scripts.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
