Re: [WiX-users] are fragments still the right way to componentize development and is there a recommended wix3 solution for targeting installationlocation at c:\Program Files (x86)\... on x64 systems a
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 used to reference those fragments has changed and the scope of what they contain is defined by how they are referenced? Saying Goodbye to FragmentRef's March 15, 2007 After many months of being deprecated, its time to say goodbye (builds >= 3.0.2716.0). All FragmentRef's will need to be converted to one of the supported reference elements in WiX 3.0. Examples of these are ComponentRef, FeatureRef, PropertyRef, or CustomActionRef among others. Regarding response to q2 - Using the flag and $(var.variables) preprocessor references will impact the results of my msi output at compile time based on the host I used to compile versus what happens at msi runtime during installation right? Is creating x64 and x86 specific msi build output the current recommended approach versus a single msi that at runtime can handle x64 and x86 installation differences? From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2008 3:10 PM To: Robert O'Brien Cc: 'wix-users@lists.sourceforge.net' Subject: Re: [WiX-users] are fragments still the right way to componentize development and is there a recommended wix3 solution for targeting installationlocation at c:\Program Files (x86)\... on x64 systems and c:\Program Files\... on x86 systems 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:\Program Files\... on x86 systems? Use the preprocessor, either $(var.variables) or based on a flag you pass in to the compiler. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] are fragments still the right way to componentize development and is there a recommended wix3 solution for targeting installationlocation at c:\Program Files (x86)\... on x64 systems a
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:\Program Files\... on x86 systems? Use the preprocessor, either $(var.variables) or based on a flag you pass in to the compiler. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Speech API 5.1 issue
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 compare them. You can also use Orca to check them out -- SP5SR.msm depends on DuplicateFiles, for example. You can add just that action to InstallExecuteSequence. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing Assembly to GAC & installdir
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 path -- it's "magic" that the actual directory for the GAC is different. Use a subdirectory with a Name attribute; that will satisfy the ICE that the paths are different. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem with Custom Dialogs
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.joyofsetup.com/2007/05/30/feature-conditions-and-ui/ for issues. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding an ok/cancel popup dialog?
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 the > Welcome page wait on the results of the spawned dialog before > evaluating the next Publish action in the list? Or do I just need to > give up and make the warning a standalone dialog page rather than a > popup? > When a spawned dialog is running, so is the dialog that spawns it. MSI doesn't have a way to close both dialogs from the spawned one. That's why we handled something similar before the welcome dialog, in src\Setup\VStudio.wxs. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] PerfCounter on NT 4.0?
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 does appear to work, but as it's > not documented as being supported I thought I'd ask if anyone had seen any > problems. > Never used it, but maybe it was added in a service pack? Might be worth tracking down to ensure it's available. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ComPlusExtension v3
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) : error LGHT0102 : The localization variable > !(loc.ComPlusInstallExecute) is > unknown. Please ensure the variable is defined. > You need to specify a -cultures:en-us switch for Light. The other extensions default to en-us but we missed WixComPlusExtension (and probably WixMsmqExtension). Please enter a bug so we can get them up to snuff. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Checking for Widnows 2008 server components?
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 the OS attack surface, after all. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Two installers for the same component - how?
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 challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] are fragments still the right way to componentize development and is there a recommended wix3 solution for targeting installationlocation at c:\Program Files (x86)\... on x64 systems and c
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? Searching through some of the mail archives it would seem to suggest using something like the following approach but that appears to have you defining your features and components twice? (VersionNT) AND (NOT > VersionNT64) (VersionNT) AND (NOT > VersionNT64) /robertob - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Doctor's approved enlargement formula
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/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Light... could spare me some time!
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 out.. specify the attribute diskid in the file tag Aurélien DEROUINEAU wrote: > > I build packages with two media components: > > > > > > > > > > > > And here is a sample Component/File couplet that I use: > > > > > > KeyPath="yes" Source="C:\Original Path\file.fil" /> > > > > > > > > The problem is that when building the project, the FIL files are put in > the > right folder (\files), however Windows Installer looks for them > inside > the root folder and not the files subfolder, which is rather frustrating: > I’ve been trying to hack around with it but no luck came out. Hopefully > you > can show me the light. > > > > > > Also, another annoyance: FIL files amount for a few gigabytes, and it > seems > that light tries to copy them to my files subfolder each time I compile, > even though no changes have been made to these files! Is there a way to > restrain light from copying them every time to save compilation time? > > > > Thanks a bunch. > > > > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > Quoted from: http://www.nabble.com/Light...-could-spare-me-some-time%21-tp15625238p15625238.html - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
