I tried DiskId inside before trying inside the component tag, and the
same behavior happened... :/
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: samedi 1 mars 2008 06:43
To: [EMAIL PROTECTED]
Subject: Light... could spare me some time!
hey may be try dis ou
Remember that most women prefer their men large and thick - do you measure up?-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/dir
q1 - Are fragments still the recommended way for breaking apart a wxs
development project into feature associated source files?
q2 - Is there a recommended wix3 solution for targeting installationlocation at
c:\Program Files (x86)\... on x64 systems and c:\Program Files\... on x86
systems?
Sea
Thomas Tomiczek wrote:
What is the recommended way to handle this?
Use separate feature trees for the server and agent.
--
sig://boB
http://joyofsetup.com/
-
This SF.net email is sponsored by: Microsoft
Defy all challen
Thomas Tomiczek wrote:
If not, is there a recommended standard way to install those? Exchange
etc. just break off and let the user install manually.
I assume this IS the recommended way then?
Yes. Installing OS components should never be done by an app -- you're
potentially broadening
David M. Petercheff wrote:
> I got the latest build 3.0.3829. It was the only one I saw with the
> WixComPlusExtension.dll but when I run light with -ext
> WixComPlusExtension I get the following output:
>
> C:\delivery\Dev\wix_public\src\ext\ComPlusExtension\wixlib\ComPlusExtens
> ion.wxs(
> 44)
Mike Dimmick wrote:
> I've just spent a day coding up LoadLibrary/GetProcAddress and falling back
> on CreateProcess to run lodctr.exe if LoadLibrary or GetProcAddress fail,
> then tested on NT 4.0 only to discover that the library, loadperf.dll, is
> actually present and implements the API! It doe
Geoff Finger wrote:
> I hooked up the dialog to the "Next" button for the welcome dialog and
> everything seem to work fine, except that if you hit "OK" it goes back
> to the welcome dialog and doesn't go on to the next section of the
> installer until you hit "Next" again. Is there any way to make
Scott Sam wrote:
> I have an install with about 8 features. Some of the features have
> Custom Dialogs that only apply to them. Is there a way to only show the
> dialog if that specific feature is being installed?
>
You can use feature conditions in button control events. But see
http://www.
Chris Weiss wrote:
> Am I using the correct syntax for installing to the GAC? I'm not sure
> why WiX thinks both files are going to [TARGETDIR]. This is with WiX
> 3.0.3704.0 What's the proper way to install an assembly to both GAC
> and a non-GAC folder.
>
Both directories resolve to the same
Robert O'Brien wrote:
q1 - Are fragments still the recommended way for breaking apart a wxs
development project into feature associated source files?
Yes.
q2 - Is there a recommended wix3 solution for targeting
installationlocation at c:\Program Files (x86)\... on x64 systems and
c:\Prog
Coffman, Clint wrote:
Anyone have any suggestions? Is there a install sequence that I need
to be modifying, or some other change that I should be making?
Probably a missing standard action. I'd suggest creating an empty
installer in both WiX and .vdproj then use dark to decompile and comp
Thanks for the quick responses.
Regarding response to q1 - after sending mail I saw the following comment on
http://wix.sourceforge.net/. Is that comment suggesting that fragments are
still valid and the recommended way for breaking apart a wxs development
project but now the element name us
13 matches
Mail list logo
