Re: [WiX-users] minor issues with WiX installer gui

[Bob Arnson]

On 3/17/2010 6:08 AM, Jacek Pospychała wrote:
> This time, it's WiX dialog. On attached screenshot you can see which exactly
> button is stuck.
>

Check a verbose log and you'll see what's taking the time.

-- 
sig://boB
http://joyofsetup.com/


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] ICE038 - revised

[Bob Arnson]

On 3/16/2010 4:03 AM, Kristoffer Danielsson wrote:
> I noticed that using the same registry setting works, but I'm not sure what 
> this implies. Is this a bad idea?
>

Yes, it violates component rules. See "Organizing Applications into 
Components" in the MSI SDK.

-- 
sig://boB
http://joyofsetup.com/


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] registrysearch

[Bob Arnson]

On 3/16/2010 6:08 AM, Yu, Brian wrote:
> How do I check if a registry directory exists or not using
> registrysearch?
>

AppSearch doesn't have that functionality.

-- 
sig://boB
http://joyofsetup.com/


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to execute a custom action that depends on an assembly being installed to the GAC

[Bob Arnson]

On 3/16/2010 7:05 PM, Jacques Eloff wrote:
> It sounds to me then that a type 2 CA is not the solution then.
>
> I guess that gives rise to some more questions:
> 1) Where should I schedule this to ensure that rollbacks can be handled,
> keeping in mind that the assemblies I installed are in the GAC before the CA
> runs?
> 2) What options do I have to keep these CAs as managed code EXEs
> 3) Would a typ 18 CA serve me any better?
>
> The CAs are modifying an XML file, but there can potentially be a 32-bit and
> 64-bit version of the file (both need to be modified) and the CA takes care
> of that since it relies on using both the 32-bit and 64-bit registry entries
> to locate the file. Having multiple installers is not an option, so that
> takes using XmlFile elements out of the solution for me.
>

You're trying to do several things that aren't supported (either well or 
at all). Your choices are limited. The short answer is to follow the 
package rules (separate x86 and x64 packages) and use XmlConfig/XmlFile 
and get rollback for free. Slightly longer is to remove your 
dependencies on the GAC for custom actions.

-- 
sig://boB
http://joyofsetup.com/


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrade Vs Install - Leaving folders/files behind on Upgrade, not on Install

[Bob Arnson]

On 3/16/2010 4:28 PM, Dan Covill wrote:
> I've been dropped into the deep end of Wix for the last couple of weeks and 
> am trying to come up with a way to make this work. I've learned how to mostly 
> make major upgrades work but for some reason I can't quite nail down this 
> aspect of the installer. How can I do a major upgrade such that certain 
> components aren't uninstalled/reinstalled. I thought that all I would need to 
> do is not change the ComponentID for the component I don't want erased.

That depends on where you schedule RemoveExistingProducts. It sounds 
like you're doing it "early" so it's an uninstall of the old product and 
install of the new one. You can move it later. But see 
http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/ for caveats.

-- 
sig://boB
http://joyofsetup.com/


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Installing from embedded CAB file and Folder

[Bob Arnson]

On 3/16/2010 8:15 AM, Sanjay Poria wrote:
> 
>
> Will mean that all the File elements will be embedded into the cab. Basically 
> I wish to have “special” file elements that are to be installed but are not 
> taken from the embedded CAB file.
>

Don't use @Cabinet or @EmbedCab attributes. That creates "loose" files.

-- 
sig://boB
http://joyofsetup.com/


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Uninstalling with merge module now takes nearly three minutes

[Wilson, Phil]

It would be a bootstrapper install, look at Burn. 

Phil Wilson 



-Original Message-
From: s...@pacaccess.com [mailto:s...@pacaccess.com] 
Sent: Wednesday, March 17, 2010 3:06 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstalling with merge module now takes nearly three 
minutes

Thanks for the feedback Phil.  Do you have any examples of adding
vc_redist.exe to a Wix install script?

Thanks,

Jeff

> The issue has to do with lots and lots of stuff going on when the C++
> runtime support merge modules are uninstalled. I am not aware of any way
> to stop them, other than by using the vc_redist.exe package as a
> prerequisite install up front and forgetting about merge modules.
>
> Phil Wilson
>
>
> -Original Message-
> From: s...@pacaccess.com [mailto:s...@pacaccess.com]
> Sent: Wednesday, March 17, 2010 11:33 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Uninstalling with merge module now takes nearly three
> minutes
>
> My installer is fairly simple and only installs two files.  I just added
> the VC8 runtime merge module to my installer.  Installation time increased
> a little, but the time to uninstall increased a lot.  Towards the end of
> the uninstall, the uninstaller appears to wait for 2:45 and gives the
> appearance that it has hung.  I know it hasn't because I'm monitoring the
> task manager and I see msiexec churning, but my average user won't know
> this and will think it has locked up.
>
> My application which I'm distributing is built with C/C++ and I am
> including the VC runtime merge module in my installer.  When I uninstall,
> the uninstaller gets half way through, with the message "Please wait while
> the Setup Wizard removes My Product", and sits there for almost three
> minutes.
>
> My first question is, is this a known/expected issue?  Is there a
> workaround?
>
>
> I ran the uninstaller with the following:
> MyInstaller.msi /l* output.txt
>
>
> I'm new to Wix, so my second question is, is this the way to debug the
> installer/uninstaller, or is there a more verbose method?
>
>
>
> While the uninstaller was churning, I opened up the log file and the last
> logs were:
> .
> .
> .
> RollbackCleanup: File: C:\Config.Msi\d8a95f3.rbf
> Action ended 11:15:17: InstallFinalize. Return value 1.
> Action 11:15:17: SxsUninstallCA.
> Action start 11:15:17: SxsUninstallCA.
> 1: sxsdelca tried opening key w/o wow64key  2:
> Software\Microsoft\Windows\CurrentVersion\SideBySide\PatchedComponents 3:
> 368 4: 0
> 1: sxsdelca tried opening wow64key  2:
> Software\Microsoft\Windows\CurrentVersion\SideBySide\PatchedComponents 3:
> 392 4: 0
> 1: sxsdelca 2: traceop 3: 1158 4: 0
> 1: sxsdelca 2: traceop 3: 1186 4: 0
> 1: sxsdelca 2: traceop 3: 732 4: 0
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {5FD88490-011C-4DF1-B886-F298D955171B} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {0CA21011-069B-B16A-A5CA-9ABE49DAC05C} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {237CD223-1B9D-47E8-A76C-E478B83CCEA2} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {13D502A3-FCDA-4843-AA66-CC11FDD94047} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {87441A59-5E64-4096-A170-14EFE67200C3} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {CAE7D1D9-3794-4169-B4DD-964ADBC534EE} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {41A2736B-89A2-40BC-AD98-CC81C375D358} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
>
> ...which doesn't do me much good (those aren't my GUIDs).
>
>
>
>
> Maybe the issue has to do with my installer file.  Here's what I currently
> have:
> 
> http://schemas.microsoft.com/wix/2006/wi";>
>Name="...the name..."
> Version="1.1.0.0"
> Language="1033"
> Id="...guid..."
> UpgradeCode="...giud..."
>   >
>Description="...description..."
>   InstallerVersion="300"
>   Compressed="yes"
> />
> 
> 
>
> 
> 
>   
> 
>SourceFile="MyCustomAction.CA.dll" />
>
>Id="Action1_CheckIfAppIsRunning"
>   BinaryKey="Action1_CheckIfAppIsRunning_File"
>   DllEntry="CheckIfAppIsRunning"
>   Impersonate="yes"
>   Execute="immediate"
>   Return="check"
> />
> 
>
>
> 
>Id="CRT"
> Language="0"
> SourceFile="C:\Program Files\Common Files\Merge
> Modules\Mi

Re: [WiX-users] test and production install

[Albert At School]

Hi,

I generate 2 MSI files in my nightly build: a test installer for the 
testers, which is basically a release installer just not officially to be 
released and contains more log info, and a development installer which 
developers can install. This last one is build with debug flags and contains 
the debug builds of our custom action DLLs. So basically showing more info 
in the log files and has asserts enabled and all sorts. This version the 
developers can install in a VM environment for personal testing and 
incorperating changes by other developers.
When we reach a point in time that we need a release for customers we 
generate an installer for release (and some MSP files for patching existing 
versions if required) which contains no extended logging and more optimized 
code in the custom action DLLs. Ofcourse it is tested very thoroughly before 
shipping ;)

When testing all installers (as we developers sometimes need to do :) ) we 
run them inside VMs (virtual machines).
With VMs you can also switch very easily between different versions, by 
using snapshots, for comparing issues in different versions.

Regards,

Albert van Peppen
Senior System Engineer
Insad Grafisch b.v.

- Original Message - 
From: "Sam Domonkos" 
To: "General discussion for Windows Installer XML toolset." 

Sent: Wednesday, March 17, 2010 8:24 PM
Subject: [WiX-users] test and production install


> Hi, what is the best practice or recommended approach for providing a
> Test version of a product and a Production version on the same server?
> One installer or two?
>
> Thanks,
> Sam
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users 


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Uninstalling with merge module now takes nearly three minutes

[sd]

Thanks for the feedback Phil.  Do you have any examples of adding
vc_redist.exe to a Wix install script?

Thanks,

Jeff

> The issue has to do with lots and lots of stuff going on when the C++
> runtime support merge modules are uninstalled. I am not aware of any way
> to stop them, other than by using the vc_redist.exe package as a
> prerequisite install up front and forgetting about merge modules.
>
> Phil Wilson
>
>
> -Original Message-
> From: s...@pacaccess.com [mailto:s...@pacaccess.com]
> Sent: Wednesday, March 17, 2010 11:33 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Uninstalling with merge module now takes nearly three
> minutes
>
> My installer is fairly simple and only installs two files.  I just added
> the VC8 runtime merge module to my installer.  Installation time increased
> a little, but the time to uninstall increased a lot.  Towards the end of
> the uninstall, the uninstaller appears to wait for 2:45 and gives the
> appearance that it has hung.  I know it hasn't because I'm monitoring the
> task manager and I see msiexec churning, but my average user won't know
> this and will think it has locked up.
>
> My application which I'm distributing is built with C/C++ and I am
> including the VC runtime merge module in my installer.  When I uninstall,
> the uninstaller gets half way through, with the message "Please wait while
> the Setup Wizard removes My Product", and sits there for almost three
> minutes.
>
> My first question is, is this a known/expected issue?  Is there a
> workaround?
>
>
> I ran the uninstaller with the following:
> MyInstaller.msi /l* output.txt
>
>
> I'm new to Wix, so my second question is, is this the way to debug the
> installer/uninstaller, or is there a more verbose method?
>
>
>
> While the uninstaller was churning, I opened up the log file and the last
> logs were:
> .
> .
> .
> RollbackCleanup: File: C:\Config.Msi\d8a95f3.rbf
> Action ended 11:15:17: InstallFinalize. Return value 1.
> Action 11:15:17: SxsUninstallCA.
> Action start 11:15:17: SxsUninstallCA.
> 1: sxsdelca tried opening key w/o wow64key  2:
> Software\Microsoft\Windows\CurrentVersion\SideBySide\PatchedComponents 3:
> 368 4: 0
> 1: sxsdelca tried opening wow64key  2:
> Software\Microsoft\Windows\CurrentVersion\SideBySide\PatchedComponents 3:
> 392 4: 0
> 1: sxsdelca 2: traceop 3: 1158 4: 0
> 1: sxsdelca 2: traceop 3: 1186 4: 0
> 1: sxsdelca 2: traceop 3: 732 4: 0
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {5FD88490-011C-4DF1-B886-F298D955171B} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {0CA21011-069B-B16A-A5CA-9ABE49DAC05C} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {237CD223-1B9D-47E8-A76C-E478B83CCEA2} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {13D502A3-FCDA-4843-AA66-CC11FDD94047} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {87441A59-5E64-4096-A170-14EFE67200C3} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {CAE7D1D9-3794-4169-B4DD-964ADBC534EE} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
> 1: sxsdelca 2: traceop 3: 748 4: 0
> 1: scavenge 2: {41A2736B-89A2-40BC-AD98-CC81C375D358} 3:
> {9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
> {8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
>
> ...which doesn't do me much good (those aren't my GUIDs).
>
>
>
>
> Maybe the issue has to do with my installer file.  Here's what I currently
> have:
> 
> http://schemas.microsoft.com/wix/2006/wi";>
>Name="...the name..."
> Version="1.1.0.0"
> Language="1033"
> Id="...guid..."
> UpgradeCode="...giud..."
>   >
>Description="...description..."
>   InstallerVersion="300"
>   Compressed="yes"
> />
> 
> 
>
> 
> 
>   
> 
>SourceFile="MyCustomAction.CA.dll" />
>
>Id="Action1_CheckIfAppIsRunning"
>   BinaryKey="Action1_CheckIfAppIsRunning_File"
>   DllEntry="CheckIfAppIsRunning"
>   Impersonate="yes"
>   Execute="immediate"
>   Return="check"
> />
> 
>
>
> 
>Id="CRT"
> Language="0"
> SourceFile="C:\Program Files\Common Files\Merge
> Modules\Microsoft_VC80_CRT_x86.msm"
> DiskId="1"
>   />
>
>   
> 
>   
>   
>DiskId="2"
>   Id="MyDll.dll"
>   Source="MyDll.dll"
> >
> 
>DiskId="2"
>   Id="MyHelpFile.chm"
>   S

Re: [WiX-users] Detect older version not working?

[Kristoffer Danielsson]

Ok, thanks.

So how can I detect the old version? All I want is to display a message box 
advising the user to uninstall the previous version.
 
> From: phil.wil...@invensys.com
> To: wix-users@lists.sourceforge.net
> Date: Wed, 17 Mar 2010 17:34:44 -0400
> Subject: Re: [WiX-users] Detect older version not working?
> 
> You can't use the Upgrade mechanism at all here - it's not that the previous 
> install was elevated, it's that the FindRelatedProducts action running in one 
> context won't detect a product installed in the other. A per machine won't 
> upgrade a per-user either. 
> 
> Phil Wilson 
> 
> 
> 
> -Original Message-
> From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se] 
> Sent: Wednesday, March 17, 2010 1:20 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Detect older version not working?
> 
> 
> Note that my previous MSI was a per-machine installation made with VS 2008. 
> The product version was 1.0.0.
> 
> 
> 
> Now I'm creating a per-user installation with WIX 3.5. I want to detect this 
> older version. Correct me if I'm wrong, but the older version cannot be 
> removed since it was an elevated installation. Hence, I want to at least 
> notify the user about the older version.
> 
> 
> 
> I can't get it working! I read this:
> 
> http://wix.mindcapers.com/wiki/Upgrade
> 
> 
> 
> * I changed the product version to 1.0.1.0.
> 
> * I changed the product code.
> 
> * The package code is set to '*'.
> 
> * The upgrade code is the same.
> 
> 
> 
> Below is the relevant part of my script. I don't understand how OLDAPPFOUND 
> is used. Please help!
> 
> 
> 
> 
> 
> 
> 
>  Maximum="$(var.ThisProductVersion)" IncludeMaximum="no" OnlyDetect="yes" 
> Language="1033" Property="OLDAPPFOUND" />
> 
>  OnlyDetect="yes" Language="1033" Property="NEWAPPFOUND" />
> 
> 
> 
> 
> 
> !(loc.LaunchCondition_LaterVersion)
> 
> 
> 
> 
> 
> 
> 
>  After="FindRelatedProducts">NEWAPPFOUND
> 
> 
> 
> _
> Mejla i busskön! Hotmail i mobilen
> http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> *** Confidentiality Notice: This e-mail, including any associated or attached 
> files, is intended solely for the individual or entity to which it is 
> addressed. This e-mail is confidential and may well also be legally 
> privileged. If you have received it in error, you are on notice of its 
> status. Please notify the sender immediately by reply e-mail and then delete 
> this message from your system. Please do not copy it or use it for any 
> purposes, or disclose its contents to any other person. This email comes from 
> a division of the Invensys Group, owned by Invensys plc, which is a company 
> registered in England and Wales with its registered office at Portland House, 
> Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of 
> European legal entities within the Invensys Group, please go to 
> http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. 
> You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail 
> inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be 
> subject to the terms of any agreements between Invensys (and/or its 
> subsidiaries and affiliates) and the recipient (and/or its subsidiaries and 
> affiliates).
> 
> 
> 
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
  
_
Hotmail i mobilen!
http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___

Re: [WiX-users] Detect older version not working?

[Wilson, Phil]

You can't use the Upgrade mechanism at all here - it's not that the previous 
install was elevated, it's that the FindRelatedProducts action running in one  
context won't detect a product installed in the other. A per machine won't 
upgrade a per-user either. 

Phil Wilson 



-Original Message-
From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se] 
Sent: Wednesday, March 17, 2010 1:20 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Detect older version not working?


Note that my previous MSI was a per-machine installation made with VS 2008. The 
product version was 1.0.0.

 

Now I'm creating a per-user installation with WIX 3.5. I want to detect this 
older version. Correct me if I'm wrong, but the older version cannot be removed 
since it was an elevated installation. Hence, I want to at least notify the 
user about the older version.

 

I can't get it working! I read this:

http://wix.mindcapers.com/wiki/Upgrade

 

* I changed the product version to 1.0.1.0.

* I changed the product code.

* The package code is set to '*'.

* The upgrade code is the same.

 

Below is the relevant part of my script. I don't understand how OLDAPPFOUND is 
used. Please help!

 

 











!(loc.LaunchCondition_LaterVersion)







NEWAPPFOUND


  
_
Mejla i busskön! Hotmail i mobilen
http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at Portland House, Bressenden Place, London, 
SW1E 5BF (Registered number 166023). For a list of European legal entities 
within the Invensys Group, please go to 
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. 
You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail 
inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be 
subject to the terms of any agreements between Invensys (and/or its 
subsidiaries and affiliates) and the recipient (and/or its subsidiaries and 
affiliates).



--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Invert Feature based on other Feature

[Dave Brotherstone]

On Wed, Mar 17, 2010 at 4:17 PM, Pally Sandher wrote:

> Set the default path for it to be AppData & add a Type 51 Custom Action
> to change the path to your .exe's directory when the main feature is
> selected for install.
>

Many thanks for your answer. I understand the logic behind this, but I can't
seem to do it - it's the "changing the path to the exe's directory" that I
can't seem to work out.

I think I want something like the following, even though this doesn't
link... (Unresolved reference to symbol 'Directory:CONFIGDIRECTORY')










   &FT_DOLOCALCONF = 3




> Simplest option would be to modify your app so it always loads the
> config from AppData regardless & just put it there. Actually why does it
> need to be in the same directory as the .exe in the first place? From
> your description it sounds like you could just put it in AppData & it'd
> work as long as there wasn't one in the same directory as the .exe.
>

We provide the option to install a "portable" version, to be installed onto
a USB drive or similar, so AppData can't be used for this type of install.

Thanks again,

Dave.



>
> -Original Message-
> From: Dave Brotherstone [mailto:dav...@pobox.com]
> Sent: 17 March 2010 06:59
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Invert Feature based on other Feature
>
> Hi all,
>
> I have a feature that controls where the config file for our application
> is located (either "locally" next to the exe in Program Files, or in
> %APPDATA%).  When this feature is selected, the config file is copied
> correctly to the right place, and the indicator file (to let the .exe
> know that the config should be loaded next to the .exe rather than
> %APPDATA%) is also created.
>
> However, if this feature is not selected, I need to place the config
> file in %APPDATA%.  I had attempted to do this with a hidden feature for
> the appdata config, and conditions on the main feature action, but that
> doesn't seem to work.
>
> FT_DOLOCALCONF is the feature that is shown to the user.  I've tried
> with !
> states as well, but from what I've read action state is correct to use
> in this case?
>
>  Display="hidden" Title="Hidden feature for AppData Config">
>NOT
> &FT_DOLOCALCONF=3
>&FT_DOLOCALCONF=3
>  
>
>
> Many thanks for any pointers,
>
> Dave.
> 
> --
> Download Intel® Parallel Studio Eval Try the new software tools for
> yourself. Speed compiling, find bugs proactively, and fine-tune
> applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Strange MSI output directory using WiX 3.5.1512.0 on Win2003 R2 SP2 Cruise Control server

[Kristoffer Danielsson]

I tried using $(OutDir) to correct my $(TargetDir) problem, but got the same 
error (variable does not match actual path). So I believe it is indeed related.


 
> Date: Wed, 17 Mar 2010 11:14:25 -0700
> From: b...@bradcunningham.net
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Strange MSI output directory using WiX 3.5.1512.0 on 
> Win2003 R2 SP2 Cruise Control server
> 
> Hmmm, sounds somewhat related but not enough info in that post to fully
> understand. Also, my issue appears to be related to OutDir not TargetDir
> (though I suspect they are handled in a similar fashion.
> 
> Thanks for pointing me to the issue. If mine does indeed end up being
> related I will make sure to update that issue with my details.
> 
> Any other thoughts?
> 
> 
> -- 
> Brad Cunningham
> Microsoft MVP: C#
> 
> http://blog.bradcunningham.net
> 
> On Wed, Mar 17, 2010 at 11:01 AM, Kristoffer Danielsson <
> kristoffer.daniels...@live.se> wrote:
> 
> >
> > Do you think this could have something to do with this bug?
> >
> >
> > http://sourceforge.net/tracker/?func=detail&aid=2970793&group_id=105970&atid=642714
> >
> >
> >
> > > Date: Wed, 17 Mar 2010 10:57:15 -0700
> > > From: b...@bradcunningham.net
> > > To: wix-users@lists.sourceforge.net
> > > Subject: [WiX-users] Strange MSI output directory using WiX 3.5.1512.0 on
> > Win2003 R2 SP2 Cruise Control server
> > >
> > > I just installed WiX 3.5.1512.0 onto my build server and added a new
> > project
> > > that is using WiX to the build. I am getting strange behavior when
> > compiling
> > > my installer. I don't see any build errors, and the MSI does get built
> > but
> > > it is put in the wrong path. When building my release configuration the
> > MSI
> > > is output into the following directory:
> > >
> > >
> > > MyProject\`, `bin\Release\`))`))MyProject.msi\
> > >
> > >
> > > *NOTE*: the backticks, commas, and extra parens.
> > >
> > > This project is developed in VS2010 but targeting .NET 3.5. I narrowed
> > the
> > > problem down to the WiX2010.targets file on the build server (C:\Program
> > > Files\MSBuild\Microsoft\WiX\v3.5\wix2010.targets)
> > >
> > > In that file I found the following property group
> > >
> > > 
> > > 
> > > 
> > > * $([System.IO.Path]::GetFullPath(`$([System.IO.Path]::Combine(`$(MSBuildProjectDirectory)`,
> > > `$(OutDir)`))`))
> > > *
> > > 
> > > $(TargetDir)$(TargetFileName)
> > >
> > > $(TargetDir)$(TargetPdbName)
> > > 
> > >
> > >
> > > *NOTE:* the escape sequence in the $(OutDir) condition. Also note the
> > > comment above stating the condition is intentionally omitted, However it
> > > isn't actually commented out. Either the comment is out of date or this
> > > condition should actually be commented out?
> > >
> > > The code snippet in the condition looks like powershell to me so I
> > thought
> > > maybe it was a version issue with powershell on my build server causing
> > the
> > > problem? I upgraded to powershell 2.0 on the server and it didn't fix the
> > > problem.
> > >
> > >
> > > Builds work correctly on my dev box (Win 7 x86 Enterprise). I am stumped
> > at
> > > this point what is causing the issue?
> > >
> > > Any ideas?
> > >
> > >
> > > Thanks
> > >
> > >
> > >
> > >
> > > Brad Cunningham
> > > Microsoft MVP: C#
> > >
> > > http://blog.bradcunningham.net
> > >
> > --
> > > Download Intel® Parallel Studio Eval
> > > Try the new software tools for yourself. Speed compiling, find bugs
> > > proactively, and fine-tune applications for parallel performance.
> > > See why Intel Parallel Studio got high marks during beta.
> > > http://p.sf.net/sfu/intel-sw-dev
> > > ___
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> > _
> > Mejla från tåget! Hotmail i mobilen.
> >
> > http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx
> >
> > --
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___

[WiX-users] Detect older version not working?

[Kristoffer Danielsson]

Note that my previous MSI was a per-machine installation made with VS 2008. The 
product version was 1.0.0.

 

Now I'm creating a per-user installation with WIX 3.5. I want to detect this 
older version. Correct me if I'm wrong, but the older version cannot be removed 
since it was an elevated installation. Hence, I want to at least notify the 
user about the older version.

 

I can't get it working! I read this:

http://wix.mindcapers.com/wiki/Upgrade

 

* I changed the product version to 1.0.1.0.

* I changed the product code.

* The package code is set to '*'.

* The upgrade code is the same.

 

Below is the relevant part of my script. I don't understand how OLDAPPFOUND is 
used. Please help!

 

 











!(loc.LaunchCondition_LaterVersion)







NEWAPPFOUND


  
_
Mejla i busskön! Hotmail i mobilen
http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Strange MSI output directory using WiX 3.5.1512.0 on Win2003 R2 SP2 Cruise Control server

[Tony Paloma]

Sorry, meant to say that the the comment is referring to how there is no 
condition against TargetDir's value when setting the TargetDir property -- not 
TargetName.

-Original Message-
From: Tony Paloma 
Sent: Wednesday, March 17, 2010 12:30 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Strange MSI output directory using WiX 3.5.1512.0 on 
Win2003 R2 SP2 Cruise Control server

I think the comment is referring to how there is no condition against 
TargetName's value (notice how most others only set the property if it doesn't 
yet exist, but this one doesn't do that).

I'm unsure of what you mean by "the code snippet in the condition" because all 
of the GetFullPath and Combine stuff is (or should be) outside of the condition:

 
$([System.IO.Path]::GetFullPath(`$([System.IO.Path]::Combine(`$(MSBuildProjectDirectory)`,
 `$(OutDir)`))`)) 

This is unrelated to powershell. What are the values for 
MSBuildProjectDirectory, OutDir, and TargetDir on the build machine during the 
build? You can get these by turning on diagnostic output 
(Tools->Options->Projects and Solutions->Build and Run) and searching for them 
after the "Initial Properties:" line (which is near the beginning of the 
output).

-Original Message-
From: Brad Cunningham [mailto:b...@bradcunningham.net]
Sent: Wednesday, March 17, 2010 10:57 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Strange MSI output directory using WiX 3.5.1512.0 on 
Win2003 R2 SP2 Cruise Control server

I just installed WiX 3.5.1512.0 onto my build server and added a new project 
that is using WiX to the build. I am getting strange behavior when compiling my 
installer. I don't see any build errors, and the MSI does get built but it is 
put in the wrong path. When building my release configuration the MSI is output 
into the following directory:


MyProject\`, `bin\Release\`))`))MyProject.msi\


*NOTE*: the backticks, commas, and extra parens.

This project is developed in VS2010 but targeting .NET 3.5.  I narrowed the 
problem down to the WiX2010.targets file on the build server (C:\Program
Files\MSBuild\Microsoft\WiX\v3.5\wix2010.targets)

In that file I found the following property group




*$([System.IO.Path]::GetFullPath(`$([System.IO.Path]::Combine(`$(MSBuildProjectDirectory)`,
`$(OutDir)`))`))
*

$(TargetDir)$(TargetFileName)

$(TargetDir)$(TargetPdbName)
  


*NOTE:* the escape sequence in the $(OutDir) condition. Also note the comment 
above stating the condition is intentionally omitted, However it isn't actually 
commented out. Either the comment is out of date or this condition should 
actually be commented out?

The code snippet in the condition looks like powershell to me so I thought 
maybe it was a version issue with powershell on my build server causing the 
problem? I upgraded to powershell 2.0 on the server and it didn't fix the 
problem.


Builds work correctly on my dev box (Win 7 x86 Enterprise). I am stumped at 
this point what is causing the issue?

Any ideas?


Thanks




Brad Cunningham
Microsoft MVP: C#

http://blog.bradcunningham.net
--
Download Intel® Parallel Studio Eval Try the new software tools for 
yourself. Speed compiling, find bugs proactively, and fine-tune applications 
for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Strange MSI output directory using WiX 3.5.1512.0 on Win2003 R2 SP2 Cruise Control server

[Tony Paloma]

I think the comment is referring to how there is no condition against 
TargetName's value (notice how most others only set the property if it doesn't 
yet exist, but this one doesn't do that).

I'm unsure of what you mean by "the code snippet in the condition" because all 
of the GetFullPath and Combine stuff is (or should be) outside of the condition:


$([System.IO.Path]::GetFullPath(`$([System.IO.Path]::Combine(`$(MSBuildProjectDirectory)`,
 `$(OutDir)`))`))


This is unrelated to powershell. What are the values for 
MSBuildProjectDirectory, OutDir, and TargetDir on the build machine during the 
build? You can get these by turning on diagnostic output 
(Tools->Options->Projects and Solutions->Build and Run) and searching for them 
after the "Initial Properties:" line (which is near the beginning of the 
output).

-Original Message-
From: Brad Cunningham [mailto:b...@bradcunningham.net] 
Sent: Wednesday, March 17, 2010 10:57 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Strange MSI output directory using WiX 3.5.1512.0 on 
Win2003 R2 SP2 Cruise Control server

I just installed WiX 3.5.1512.0 onto my build server and added a new project 
that is using WiX to the build. I am getting strange behavior when compiling my 
installer. I don't see any build errors, and the MSI does get built but it is 
put in the wrong path. When building my release configuration the MSI is output 
into the following directory:


MyProject\`, `bin\Release\`))`))MyProject.msi\


*NOTE*: the backticks, commas, and extra parens.

This project is developed in VS2010 but targeting .NET 3.5.  I narrowed the 
problem down to the WiX2010.targets file on the build server (C:\Program
Files\MSBuild\Microsoft\WiX\v3.5\wix2010.targets)

In that file I found the following property group




*$([System.IO.Path]::GetFullPath(`$([System.IO.Path]::Combine(`$(MSBuildProjectDirectory)`,
`$(OutDir)`))`))
*

$(TargetDir)$(TargetFileName)

$(TargetDir)$(TargetPdbName)
  


*NOTE:* the escape sequence in the $(OutDir) condition. Also note the comment 
above stating the condition is intentionally omitted, However it isn't actually 
commented out. Either the comment is out of date or this condition should 
actually be commented out?

The code snippet in the condition looks like powershell to me so I thought 
maybe it was a version issue with powershell on my build server causing the 
problem? I upgraded to powershell 2.0 on the server and it didn't fix the 
problem.


Builds work correctly on my dev box (Win 7 x86 Enterprise). I am stumped at 
this point what is causing the issue?

Any ideas?


Thanks




Brad Cunningham
Microsoft MVP: C#

http://blog.bradcunningham.net
--
Download Intel® Parallel Studio Eval Try the new software tools for 
yourself. Speed compiling, find bugs proactively, and fine-tune applications 
for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] test and production install

[Sam Domonkos]

Hi, what is the best practice or recommended approach for providing a 
Test version of a product and a Production version on the same server?  
One installer or two?

Thanks,
Sam

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Uninstalling with merge module now takes nearly three minutes

[Wilson, Phil]

The issue has to do with lots and lots of stuff going on when the C++ runtime 
support merge modules are uninstalled. I am not aware of any way to stop them, 
other than by using the vc_redist.exe package as a prerequisite install up 
front and forgetting about merge modules. 

Phil Wilson 


-Original Message-
From: s...@pacaccess.com [mailto:s...@pacaccess.com] 
Sent: Wednesday, March 17, 2010 11:33 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Uninstalling with merge module now takes nearly three 
minutes

My installer is fairly simple and only installs two files.  I just added
the VC8 runtime merge module to my installer.  Installation time increased
a little, but the time to uninstall increased a lot.  Towards the end of
the uninstall, the uninstaller appears to wait for 2:45 and gives the
appearance that it has hung.  I know it hasn't because I'm monitoring the
task manager and I see msiexec churning, but my average user won't know
this and will think it has locked up.

My application which I'm distributing is built with C/C++ and I am
including the VC runtime merge module in my installer.  When I uninstall,
the uninstaller gets half way through, with the message "Please wait while
the Setup Wizard removes My Product", and sits there for almost three
minutes.

My first question is, is this a known/expected issue?  Is there a workaround?


I ran the uninstaller with the following:
MyInstaller.msi /l* output.txt


I'm new to Wix, so my second question is, is this the way to debug the
installer/uninstaller, or is there a more verbose method?



While the uninstaller was churning, I opened up the log file and the last
logs were:
.
.
.
RollbackCleanup: File: C:\Config.Msi\d8a95f3.rbf
Action ended 11:15:17: InstallFinalize. Return value 1.
Action 11:15:17: SxsUninstallCA.
Action start 11:15:17: SxsUninstallCA.
1: sxsdelca tried opening key w/o wow64key  2:
Software\Microsoft\Windows\CurrentVersion\SideBySide\PatchedComponents 3:
368 4: 0
1: sxsdelca tried opening wow64key  2:
Software\Microsoft\Windows\CurrentVersion\SideBySide\PatchedComponents 3:
392 4: 0
1: sxsdelca 2: traceop 3: 1158 4: 0
1: sxsdelca 2: traceop 3: 1186 4: 0
1: sxsdelca 2: traceop 3: 732 4: 0
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {5FD88490-011C-4DF1-B886-F298D955171B} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {0CA21011-069B-B16A-A5CA-9ABE49DAC05C} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {237CD223-1B9D-47E8-A76C-E478B83CCEA2} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {13D502A3-FCDA-4843-AA66-CC11FDD94047} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {87441A59-5E64-4096-A170-14EFE67200C3} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {CAE7D1D9-3794-4169-B4DD-964ADBC534EE} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {41A2736B-89A2-40BC-AD98-CC81C375D358} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1

...which doesn't do me much good (those aren't my GUIDs).




Maybe the issue has to do with my installer file.  Here's what I currently
have:

http://schemas.microsoft.com/wix/2006/wi";>
  






  








  

  

  
  




  

  




  
  









  



  

  




Is there anything glaring wrong?  Did I mess up the VC runtime merge module?

Sorry for the really long message... I didn't know how else to describe
the issue.

Jeff




--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this mess

Re: [WiX-users] Strange MSI output directory using WiX 3.5.1512.0 on Win2003 R2 SP2 Cruise Control server

[Brad Cunningham]

Hmmm, sounds somewhat related but not enough info in that post to fully
understand. Also, my issue appears to be related to OutDir not TargetDir
(though I suspect they are handled in a similar fashion.

Thanks for pointing me to the issue. If mine does indeed end up being
related I will make sure to update that issue with my details.

Any other thoughts?


-- 
Brad Cunningham
Microsoft MVP: C#

http://blog.bradcunningham.net

On Wed, Mar 17, 2010 at 11:01 AM, Kristoffer Danielsson <
kristoffer.daniels...@live.se> wrote:

>
> Do you think this could have something to do with this bug?
>
>
> http://sourceforge.net/tracker/?func=detail&aid=2970793&group_id=105970&atid=642714
>
>
>
> > Date: Wed, 17 Mar 2010 10:57:15 -0700
> > From: b...@bradcunningham.net
> > To: wix-users@lists.sourceforge.net
> > Subject: [WiX-users] Strange MSI output directory using WiX 3.5.1512.0 on
> Win2003 R2 SP2 Cruise Control server
> >
> > I just installed WiX 3.5.1512.0 onto my build server and added a new
> project
> > that is using WiX to the build. I am getting strange behavior when
> compiling
> > my installer. I don't see any build errors, and the MSI does get built
> but
> > it is put in the wrong path. When building my release configuration the
> MSI
> > is output into the following directory:
> >
> >
> > MyProject\`, `bin\Release\`))`))MyProject.msi\
> >
> >
> > *NOTE*: the backticks, commas, and extra parens.
> >
> > This project is developed in VS2010 but targeting .NET 3.5. I narrowed
> the
> > problem down to the WiX2010.targets file on the build server (C:\Program
> > Files\MSBuild\Microsoft\WiX\v3.5\wix2010.targets)
> >
> > In that file I found the following property group
> >
> > 
> > 
> > 
> > * $([System.IO.Path]::GetFullPath(`$([System.IO.Path]::Combine(`$(MSBuildProjectDirectory)`,
> > `$(OutDir)`))`))
> > *
> > 
> > $(TargetDir)$(TargetFileName)
> >
> > $(TargetDir)$(TargetPdbName)
> > 
> >
> >
> > *NOTE:* the escape sequence in the $(OutDir) condition. Also note the
> > comment above stating the condition is intentionally omitted, However it
> > isn't actually commented out. Either the comment is out of date or this
> > condition should actually be commented out?
> >
> > The code snippet in the condition looks like powershell to me so I
> thought
> > maybe it was a version issue with powershell on my build server causing
> the
> > problem? I upgraded to powershell 2.0 on the server and it didn't fix the
> > problem.
> >
> >
> > Builds work correctly on my dev box (Win 7 x86 Enterprise). I am stumped
> at
> > this point what is causing the issue?
> >
> > Any ideas?
> >
> >
> > Thanks
> >
> >
> >
> >
> > Brad Cunningham
> > Microsoft MVP: C#
> >
> > http://blog.bradcunningham.net
> >
> --
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
>
> _
> Mejla från tåget! Hotmail i mobilen.
>
> http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Uninstalling with merge module now takes nearly three minutes

[sd]

My installer is fairly simple and only installs two files.  I just added
the VC8 runtime merge module to my installer.  Installation time increased
a little, but the time to uninstall increased a lot.  Towards the end of
the uninstall, the uninstaller appears to wait for 2:45 and gives the
appearance that it has hung.  I know it hasn't because I'm monitoring the
task manager and I see msiexec churning, but my average user won't know
this and will think it has locked up.

My application which I'm distributing is built with C/C++ and I am
including the VC runtime merge module in my installer.  When I uninstall,
the uninstaller gets half way through, with the message "Please wait while
the Setup Wizard removes My Product", and sits there for almost three
minutes.

My first question is, is this a known/expected issue?  Is there a workaround?


I ran the uninstaller with the following:
MyInstaller.msi /l* output.txt


I'm new to Wix, so my second question is, is this the way to debug the
installer/uninstaller, or is there a more verbose method?



While the uninstaller was churning, I opened up the log file and the last
logs were:
.
.
.
RollbackCleanup: File: C:\Config.Msi\d8a95f3.rbf
Action ended 11:15:17: InstallFinalize. Return value 1.
Action 11:15:17: SxsUninstallCA.
Action start 11:15:17: SxsUninstallCA.
1: sxsdelca tried opening key w/o wow64key  2:
Software\Microsoft\Windows\CurrentVersion\SideBySide\PatchedComponents 3:
368 4: 0
1: sxsdelca tried opening wow64key  2:
Software\Microsoft\Windows\CurrentVersion\SideBySide\PatchedComponents 3:
392 4: 0
1: sxsdelca 2: traceop 3: 1158 4: 0
1: sxsdelca 2: traceop 3: 1186 4: 0
1: sxsdelca 2: traceop 3: 732 4: 0
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {5FD88490-011C-4DF1-B886-F298D955171B} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {0CA21011-069B-B16A-A5CA-9ABE49DAC05C} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {237CD223-1B9D-47E8-A76C-E478B83CCEA2} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {13D502A3-FCDA-4843-AA66-CC11FDD94047} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {87441A59-5E64-4096-A170-14EFE67200C3} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {CAE7D1D9-3794-4169-B4DD-964ADBC534EE} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1
1: sxsdelca 2: traceop 3: 748 4: 0
1: scavenge 2: {41A2736B-89A2-40BC-AD98-CC81C375D358} 3:
{9BFEE365-EA45-10B3-B01F-C8B3B9A1E18E} 4:
{8576DD38-E9CD-4CB6-A6BF-9AD4D870B486} 5: -1

...which doesn't do me much good (those aren't my GUIDs).




Maybe the issue has to do with my installer file.  Here's what I currently
have:

http://schemas.microsoft.com/wix/2006/wi";>
  






  








  

  

  
  




  

  




  
  









  



  

  




Is there anything glaring wrong?  Did I mess up the VC runtime merge module?

Sorry for the really long message... I didn't know how else to describe
the issue.

Jeff




--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding multiple files to component

[Castro, Edwin G. (Hillsboro)]

I have successfully automated heat in situations where I don't have to register 
COM component *and* was only going to support Major Upgrades. In these cases I 
use my build tool, MSBuild, to stage the files correctly for me. I tell heat to 
let the compiler determine GUIDs for me as candle does this in a very stable 
fashion now. I also make sure to schedule RemoveExistingProducts early. If you 
_need_ to support other upgrade mechanisms than Major Upgrades, then I would 
highly recommend using the more heavy weight approaches described on other 
emails.

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail

> -Original Message-
> From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se]
> Sent: Wednesday, March 17, 2010 5:57 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> 
> 1) I believe I posted a detailed explanation on this. You should only
> use heat manually!
> 
> > From: cameron.ker...@philips.com
> > To: wix-users@lists.sourceforge.net
> > Date: Wed, 17 Mar 2010 13:19:54 +0100
> > Subject: Re: [WiX-users] Adding multiple files to component
> >
> > Thanks. I guess people have been giving me two different responses
> here and I'm trying to figure out the right way to do this.
> >
> > 1) Should I use heat each time during a build, to harvest all the
> files in a directory (directory contains a executable and all of its
> associated dlls and dependencies). Then include that fragment with my
> main wix project.
> >
> > 2) Or do I either use this WixFileTool or Heat to just generate this
> for me once, add it to my Wix Project, and forever maintain that list
> of files. Since we are still in the beginning of the development for
> this project, it is likely files will be renamed/files will be
> added/files will be deleted.
> >
> > What is the proper way / benefits of each?
> >
> > Thanks,
> >
> >
> > -Original Message-
> > From: Ivo Stoyanov [mailto:ivos...@yahoo.com]
> > Sent: Wednesday, March 17, 2010 8:10 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Adding multiple files to component
> >
> > You can try this - simple GUI
> > http://flexsetup.codeplex.com/
> > WiXFileTool: generates WiX file definitions and component definitions
> for a collection of files
> >
> >
> >
> >
> > 
> > From: "Kerber, Cameron" 
> > To: General discussion for Windows Installer XML toolset.  us...@lists.sourceforge.net>
> > Sent: Tue, March 16, 2010 8:43:52 AM
> > Subject: Re: [WiX-users] Adding multiple files to component
> >
> > Yes, I understand that you can put multiple files in a component, but
> that means I have to write the Source for each of the files, and spell
> out each file xml element. I basically just want to set the Source to a
> directory and include all files under that directory. Or some process
> that converts a directory to   Source="B.txt">
> >
> > I can't be typing this each and everytime.
> >
> > Heat tool. I'll look into it.
> >
> > Do you know of any websites with tutorial on it? Any way to integrate
> into MSBuild?
> >
> > -Original Message-
> > From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se]
> > Sent: Tuesday, March 16, 2010 11:36 AM
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Adding multiple files to component
> >
> >
> > I'm also a newbie, so my solution below could be "wrong". However, it
> works:
> >
> >
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> >
> > Something like that. However, I do remember that this technique is
> not recommended - for some reason I don't know...
> >
> >
> > > From: cameron.ker...@philips.com
> > > To: WiX-users@lists.sourceforge.net
> > > Date: Tue, 16 Mar 2010 16:27:31 +0100
> > > Subject: [WiX-users] Adding multiple files to component
> > >
> > > I'm sure this question has been asked before in some variety but
> searching the mail archives on SourceForge is awful. I am also new to
> WIX
> > >
> > > Anyways, in my build process I am outputting a bunch of files to a
> directory. I want all those files added to a component in my WIX
> project. To build my WIX project, during my build process I just build
> my WIX installer solution and it creates the setup package. So besides
> manually adding all these files (~50) to my component by hand, I don't
> understand how to accomplish this. All the tutorials just use one file
> in there examples. No one uses adding files from a source directory.
> > >
> > > Thanks!
> > >
> > > 
> > > The information contained in this message may be confidential and
> legally protected under applicable law. The message is intended solely
> for the addressee(s). If you are not the intended recipient, you are
> hereby notified that any use,

Re: [WiX-users] Disable UI in patch by default

[Oleksandr Y. Nechyporenko]

Yes, I've placed it in main wxs and have moved it to InstallExecuteSequence.

Now it looks like 




PATCH
AND Installed



Also I've produced new msi with this change and have installed it. Then I
have produced new msi version, and have created msp.

But it still doesn't work ((

I'm not sure, is it correct that I use value "2" for LIMITUI.
Also is it correct that I've set the custom action after the
LaunchConditions action?

Thanks.



-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Wednesday, March 17, 2010 7:36 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Disable UI in patch by default

Is that code in your new Product or in the patch XML? It should be in
the new Product if it's not already.
Try putting your Custom Action in the InstallExecuteSequence not the
InstallUISequence. Since you're essentially trying to suppress running
of the InstallUISequence it may already be too late at that point.
Other than that it looks fine, I have the exact same code in the
InstallExecuteSequence to set the REINSTALL & REINSTALLMODE properties
when running MSPs. If it still doesn't work you may not be able to
retroactively apply the change in this manner, it may need to exist in
the original Product for it to work (which means it'll work for any
future patches of your new product, just not this one).


Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
 
 
 

-Original Message-
From: Oleksandr Y. Nechyporenko [mailto:alexnc69...@gmail.com] 
Sent: 17 March 2010 16:46
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Disable UI in patch by default

I've tried to add following code




PATCH AND Installed


But it does't work (((


-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Tuesday, March 16, 2010 7:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Disable UI in patch by default

http://msdn.microsoft.com/en-us/library/aa369759.aspx 

Use a type 51 custom action to set that & condition it with "PATCH AND
Installed".

Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501 

http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP Email Disclaimer

-Original Message-
From: Oleksandr Y. Nechyporenko [mailto:alexnc69...@gmail.com]
Sent: 16 March 2010 14:29
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] Disable UI in patch by default

Hi All,

 

I've created install for our product. Now I've created a path as
described here http://wix.sourceforge.net/manual-wix3/wix_patching.htm.

 

Is there way to hide user interface when MSP file is running by mouse
double click? I've used in WixUI_Mondo in my setup project.

Now when I run MSP by double click the user interface is also appeared.
I want to create silent patch install by default, like MS Office MSPs
works.

 

Is there any directive or tag which I can specify in patch's wxs file
which will create patch without UI?

 

Thanks.

 


--
Download Intel® Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users





--
Download Intel® Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Download Intel® Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.n

Re: [WiX-users] Strange MSI output directory using WiX 3.5.1512.0 on Win2003 R2 SP2 Cruise Control server

[Kristoffer Danielsson]

Do you think this could have something to do with this bug?

http://sourceforge.net/tracker/?func=detail&aid=2970793&group_id=105970&atid=642714


 
> Date: Wed, 17 Mar 2010 10:57:15 -0700
> From: b...@bradcunningham.net
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Strange MSI output directory using WiX 3.5.1512.0 on 
> Win2003 R2 SP2 Cruise Control server
> 
> I just installed WiX 3.5.1512.0 onto my build server and added a new project
> that is using WiX to the build. I am getting strange behavior when compiling
> my installer. I don't see any build errors, and the MSI does get built but
> it is put in the wrong path. When building my release configuration the MSI
> is output into the following directory:
> 
> 
> MyProject\`, `bin\Release\`))`))MyProject.msi\
> 
> 
> *NOTE*: the backticks, commas, and extra parens.
> 
> This project is developed in VS2010 but targeting .NET 3.5. I narrowed the
> problem down to the WiX2010.targets file on the build server (C:\Program
> Files\MSBuild\Microsoft\WiX\v3.5\wix2010.targets)
> 
> In that file I found the following property group
> 
> 
> 
> 
> * $([System.IO.Path]::GetFullPath(`$([System.IO.Path]::Combine(`$(MSBuildProjectDirectory)`,
> `$(OutDir)`))`))
> *
> 
> $(TargetDir)$(TargetFileName)
> 
> $(TargetDir)$(TargetPdbName)
> 
> 
> 
> *NOTE:* the escape sequence in the $(OutDir) condition. Also note the
> comment above stating the condition is intentionally omitted, However it
> isn't actually commented out. Either the comment is out of date or this
> condition should actually be commented out?
> 
> The code snippet in the condition looks like powershell to me so I thought
> maybe it was a version issue with powershell on my build server causing the
> problem? I upgraded to powershell 2.0 on the server and it didn't fix the
> problem.
> 
> 
> Builds work correctly on my dev box (Win 7 x86 Enterprise). I am stumped at
> this point what is causing the issue?
> 
> Any ideas?
> 
> 
> Thanks
> 
> 
> 
> 
> Brad Cunningham
> Microsoft MVP: C#
> 
> http://blog.bradcunningham.net
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
  
_
Mejla från tåget! Hotmail i mobilen.
http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Recall: Where can I get the symbols for WIX 3.0 RTM?

[Sandip Shahane]

Sandip Shahane would like to recall the message, "Where can I get the symbols 
for WIX 3.0 RTM?".
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Where can I get the symbols for WIX 3.0 RTM?

[Sandip Shahane]

Hey internal site http://wix should have the details for binaries, sources and 
symbols. I had enlisted wix 3.0 RTM tree some time back.

-Original Message-
From: Sharat Janapareddy [mailto:sharat.janapare...@microsoft.com] 
Sent: Tuesday, March 16, 2010 3:53 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Where can I get the symbols for WIX 3.0 RTM?

Can someone point me to the symbols for WIX 3.0 RTM sources? I don't see 
anything related to that @ http://sourceforge.net/projects/wix/files/.

Thanks,

Sharat Janapareddy
~ 40269

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Strange MSI output directory using WiX 3.5.1512.0 on Win2003 R2 SP2 Cruise Control server

[Brad Cunningham]

I just installed WiX 3.5.1512.0 onto my build server and added a new project
that is using WiX to the build. I am getting strange behavior when compiling
my installer. I don't see any build errors, and the MSI does get built but
it is put in the wrong path. When building my release configuration the MSI
is output into the following directory:


MyProject\`, `bin\Release\`))`))MyProject.msi\


*NOTE*: the backticks, commas, and extra parens.

This project is developed in VS2010 but targeting .NET 3.5.  I narrowed the
problem down to the WiX2010.targets file on the build server (C:\Program
Files\MSBuild\Microsoft\WiX\v3.5\wix2010.targets)

In that file I found the following property group




*$([System.IO.Path]::GetFullPath(`$([System.IO.Path]::Combine(`$(MSBuildProjectDirectory)`,
`$(OutDir)`))`))
*

$(TargetDir)$(TargetFileName)

$(TargetDir)$(TargetPdbName)
  


*NOTE:* the escape sequence in the $(OutDir) condition. Also note the
comment above stating the condition is intentionally omitted, However it
isn't actually commented out. Either the comment is out of date or this
condition should actually be commented out?

The code snippet in the condition looks like powershell to me so I thought
maybe it was a version issue with powershell on my build server causing the
problem? I upgraded to powershell 2.0 on the server and it didn't fix the
problem.


Builds work correctly on my dev box (Win 7 x86 Enterprise). I am stumped at
this point what is causing the issue?

Any ideas?


Thanks




Brad Cunningham
Microsoft MVP: C#

http://blog.bradcunningham.net
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] strangeness with directory permissions

[Andrew Hammond]

I have a strange issue with creating and setting permissions on a new
directory. My goal is to have THE_USER_ACCOUNT user to have permission to
create, and rename files in this new directory. The following relevant
snippets create the dir and set permissions for all the other users
correctly. It gets most of the correct permissions for THE_USER_ACCOUNT, but
not modify permissions (specifically, it's missing the ability to "delete
children"). Strangely, a co-worker tried running with this configuration and
it worked exactly correctly. We have not been able to identify a meaningful
difference in environments.

It is probably also worth noting that a typical deployment of this has
THE_USER_ACCOUNT as NT AUTHORITY\NETWORK SERVICE, but that parameter can be
set to any valid name (and we have tested with a local user, network
service, and a domain user on both systems. On his, this works, but on mine
and in QA it fails).


  


 
  




  
CREATE_MY_NEW_DIR="1"

  
  
  

  

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Disable UI in patch by default

[Pally Sandher]

Is that code in your new Product or in the patch XML? It should be in
the new Product if it's not already.
Try putting your Custom Action in the InstallExecuteSequence not the
InstallUISequence. Since you're essentially trying to suppress running
of the InstallUISequence it may already be too late at that point.
Other than that it looks fine, I have the exact same code in the
InstallExecuteSequence to set the REINSTALL & REINSTALLMODE properties
when running MSPs. If it still doesn't work you may not be able to
retroactively apply the change in this manner, it may need to exist in
the original Product for it to work (which means it'll work for any
future patches of your new product, just not this one).


Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
 
 
 

-Original Message-
From: Oleksandr Y. Nechyporenko [mailto:alexnc69...@gmail.com] 
Sent: 17 March 2010 16:46
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Disable UI in patch by default

I've tried to add following code




PATCH AND Installed


But it does't work (((


-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Tuesday, March 16, 2010 7:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Disable UI in patch by default

http://msdn.microsoft.com/en-us/library/aa369759.aspx 

Use a type 51 custom action to set that & condition it with "PATCH AND
Installed".

Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501 

http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP Email Disclaimer

-Original Message-
From: Oleksandr Y. Nechyporenko [mailto:alexnc69...@gmail.com]
Sent: 16 March 2010 14:29
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] Disable UI in patch by default

Hi All,

 

I've created install for our product. Now I've created a path as
described here http://wix.sourceforge.net/manual-wix3/wix_patching.htm.

 

Is there way to hide user interface when MSP file is running by mouse
double click? I've used in WixUI_Mondo in my setup project.

Now when I run MSP by double click the user interface is also appeared.
I want to create silent patch install by default, like MS Office MSPs
works.

 

Is there any directive or tag which I can specify in patch's wxs file
which will create patch without UI?

 

Thanks.

 


--
Download Intel® Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users





--
Download Intel® Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Download Intel® Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Disable UI in patch by default

[Oleksandr Y. Nechyporenko]

I've tried to add following code




PATCH
AND Installed


But it does't work (((


-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Tuesday, March 16, 2010 7:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Disable UI in patch by default

http://msdn.microsoft.com/en-us/library/aa369759.aspx 

Use a type 51 custom action to set that & condition it with "PATCH AND
Installed".

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer

-Original Message-
From: Oleksandr Y. Nechyporenko [mailto:alexnc69...@gmail.com] 
Sent: 16 March 2010 14:29
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] Disable UI in patch by default

Hi All,

 

I've created install for our product. Now I've created a path as
described here http://wix.sourceforge.net/manual-wix3/wix_patching.htm.

 

Is there way to hide user interface when MSP file is running by mouse
double click? I've used in WixUI_Mondo in my setup project.

Now when I run MSP by double click the user interface is also appeared.
I want to create silent patch install by default, like MS Office MSPs
works.

 

Is there any directive or tag which I can specify in patch's wxs file
which will create patch without UI?

 

Thanks.

 


--
Download Intel® Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Invert Feature based on other Feature

[Pally Sandher]

Set the default path for it to be AppData & add a Type 51 Custom Action
to change the path to your .exe's directory when the main feature is
selected for install.

Simplest option would be to modify your app so it always loads the
config from AppData regardless & just put it there. Actually why does it
need to be in the same directory as the .exe in the first place? From
your description it sounds like you could just put it in AppData & it'd
work as long as there wasn't one in the same directory as the .exe.

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer


-Original Message-
From: Dave Brotherstone [mailto:dav...@pobox.com] 
Sent: 17 March 2010 06:59
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Invert Feature based on other Feature

Hi all,

I have a feature that controls where the config file for our application
is located (either "locally" next to the exe in Program Files, or in
%APPDATA%).  When this feature is selected, the config file is copied
correctly to the right place, and the indicator file (to let the .exe
know that the config should be loaded next to the .exe rather than
%APPDATA%) is also created.

However, if this feature is not selected, I need to place the config
file in %APPDATA%.  I had attempted to do this with a hidden feature for
the appdata config, and conditions on the main feature action, but that
doesn't seem to work.

FT_DOLOCALCONF is the feature that is shown to the user.  I've tried
with !
states as well, but from what I've read action state is correct to use
in this case?


NOT
&FT_DOLOCALCONF=3
&FT_DOLOCALCONF=3
  


Many thanks for any pointers,

Dave.

--
Download Intel® Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding multiple files to component

[Pally Sandher]

So how would you automatically include everything in a directory where the 
filenames of those files can change from 1 build to the next?
WiX does have a way to handle this, it's called heat.exe. There are people 
using it as part of an automated system to generate fragments, there's even 
been changes to heat.exe during WiX 3.0 development to support this but it's 
still not a recommended practice. That doesn't mean you can't do it, just don't 
expect it to be 100% perfect every time.

I think what your having issues with is that commercial alternatives which 
build Windows Installer packages hide things like actually writing code from 
you so you're used to just clicking buttons & having entire directories appear 
in your installers. That's not how Windows Installer itself works, every file 
you want to install needs a File Id & a Component to belong to, every Component 
needs a Component Id (GUID) and a Directory to install in etc. heat.exe can 
take a good guess at this for you but it subscribes to the "rubbish in, rubbish 
out" philosophy & nothing in WiX (or the Windows Installer itself for that 
matter) holds your hand like most commercial packages will.

WiX is a powerful framework for creating Windows Installer packages, same way 
C++ is a powerful framework for creating executables & DLL's. Without a basic 
knowledge of STL/ATL/MFC/.NET/etc would you attempt to write fully fledged 
applications in C++?

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 
0SP
Email Disclaimer


-Original Message-
From: Kerber, Cameron [mailto:cameron.ker...@philips.com] 
Sent: 17 March 2010 13:17
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding multiple files to component

Maybe, but it seems kind of silly.  So if have a directory fill with a thousand 
help files, I need to manually maintain this.  Even if the tool that generates 
the help files have a different name each time.  This seems completely 
ridiculous that WiX doesn't have a way to handle this!

-Original Message-
From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se]
Sent: Wednesday, March 17, 2010 8:57 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding multiple files to component


1) I believe I posted a detailed explanation on this. You should only use heat 
manually!
 
> From: cameron.ker...@philips.com
> To: wix-users@lists.sourceforge.net
> Date: Wed, 17 Mar 2010 13:19:54 +0100
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> Thanks. I guess people have been giving me two different responses here and 
> I'm trying to figure out the right way to do this. 
> 
> 1) Should I use heat each time during a build, to harvest all the files in a 
> directory (directory contains a executable and all of its associated dlls and 
> dependencies). Then include that fragment with my main wix project.
> 
> 2) Or do I either use this WixFileTool or Heat to just generate this for me 
> once, add it to my Wix Project, and forever maintain that list of files. 
> Since we are still in the beginning of the development for this project, it 
> is likely files will be renamed/files will be added/files will be deleted.
> 
> What is the proper way / benefits of each?
> 
> Thanks,
> 
> 
> -Original Message-
> From: Ivo Stoyanov [mailto:ivos...@yahoo.com] 
> Sent: Wednesday, March 17, 2010 8:10 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> You can try this - simple GUI
> http://flexsetup.codeplex.com/
> WiXFileTool: generates WiX file definitions and component definitions for a 
> collection of files
> 
> 
> 
> 
> 
> From: "Kerber, Cameron" 
> To: General discussion for Windows Installer XML toolset. 
> 
> Sent: Tue, March 16, 2010 8:43:52 AM
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> Yes, I understand that you can put multiple files in a component, but that 
> means I have to write the Source for each of the files, and spell out each 
> file xml element. I basically just want to set the Source to a directory and 
> include all files under that directory. Or some process that converts a 
> directory to   
> 
> I can't be typing this each and everytime.
> 
> Heat tool. I'll look into it. 
> 
> Do you know of any websites with tutorial on it? Any way to integrate into 
> MSBuild?
> 
> -Original Message-
> From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se] 
> Sent: Tuesday, March 16, 2010 11:36 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> 
> I'm also a newbie, so my s

Re: [WiX-users] "disk space requirements" message appearing (and not going away)

[Chris Lord]

Jeff,

Several people including myself have reported seeing this during the 
course of an installation. It appears to only happen once in a while so 
its very difficult to catch. In fact, I had it happen yesterday when I 
was trying to install either WiX or WixEdit (I don't remember which) 
onto a Win XP machine. I had to cancel the install and restart it and 
then everything was good.

As far as I know this one remains unresolved.

Chris


s...@pacaccess.com wrote:
> In my installer, at various times I'm getting a message which says,
> "Please wait while the installer finishes determining your disk space
> requirements" and then never goes away.
>
> I've searched on this error and from what I've read, this happens when the
> MSI doesn't have any components to install.  Well, my MSI is installing
> components, so I don't know what's going on.
>
> This issue doesn't happen 100% of the time, but I've found that if I
> attempt go through the uninstall process (I've seen thin in both install
> and uninstall), go through a few of the screens, cancel out right before
> the installer starts to uninstall, and then repeat this process, the disk
> space message alternates in appearance (in other words, every other time I
> start the uninstall and then cancel, I get the 'determining disk space'
> message).
>
> I ran my installer with "myinstaller.msi /l* output.txt" and the steps
> that are logged are exactly the same, so this is a mystery to me.
>
> Any suggestions?
>
> Thanks,
>
> Jeff
>
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>   

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding multiple files to component

[Kristoffer Danielsson]

That's exactly how you solve it, according to the docs! :)

 
> From: alb...@de-notenbalk.nl
> To: wix-users@lists.sourceforge.net
> Date: Wed, 17 Mar 2010 14:34:45 +0100
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> I've been following this discussion and still I haven't seen the solution
> we've build;
> 
> When we create an installer set we harvest the files into the appropriate
> folders, then we have create a tool which scans which files are there.
> The files are stored into a database where they are assigned a GUID for the
> current release version (version 1.0, 1.2, 2.0 etc..)
> When the file is already in the database only a datetimestamp is modified
> and the GUID (for that specific version) stays the same. These files are
> also marked as active.
> At the end all files for the current release version where the datetimestamp
> is not altered are marked as inactive.
> >From this database we have a tool which can generate the WiX (component)
> files for Minor updates, Major Updates and even patches between versions.
> In this system there are more features like language independency,
> x86/x64/IA64 handling etc.
> I cannot donate this system to the community since it is a business thing :)
> But I could describe parts of it so someone can build this for the WiX
> community :)
> We use it in our nightly builds to generate test-branche sets and
> development-brance sets. For a definitive release we manyaly generate a
> clean set and a set of patches.
> The system is also WiX version independent; It can generate for WiX 2.0, 3.0
> (current active release version) and 3.5.
> 
> Maybe this can help somebody started?
> 
> Regards,
> 
> Albert van Peppen
> 
> -Oorspronkelijk bericht-
> Van: Kerber, Cameron [mailto:cameron.ker...@philips.com] 
> Verzonden: woensdag 17 maart 2010 14:17
> Aan: General discussion for Windows Installer XML toolset.
> Onderwerp: Re: [WiX-users] Adding multiple files to component
> 
> Maybe, but it seems kind of silly. So if have a directory fill with a
> thousand help files, I need to manually maintain this. Even if the tool
> that generates the help files have a different name each time. This seems
> completely ridiculous that WiX doesn't have a way to handle this!
> 
> -Original Message-
> From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se] 
> Sent: Wednesday, March 17, 2010 8:57 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> 
> 1) I believe I posted a detailed explanation on this. You should only use
> heat manually!
> 
> > From: cameron.ker...@philips.com
> > To: wix-users@lists.sourceforge.net
> > Date: Wed, 17 Mar 2010 13:19:54 +0100
> > Subject: Re: [WiX-users] Adding multiple files to component
> > 
> > Thanks. I guess people have been giving me two different responses here
> and I'm trying to figure out the right way to do this. 
> > 
> > 1) Should I use heat each time during a build, to harvest all the files in
> a directory (directory contains a executable and all of its associated dlls
> and dependencies). Then include that fragment with my main wix project.
> > 
> > 2) Or do I either use this WixFileTool or Heat to just generate this for
> me once, add it to my Wix Project, and forever maintain that list of files.
> Since we are still in the beginning of the development for this project, it
> is likely files will be renamed/files will be added/files will be deleted.
> > 
> > What is the proper way / benefits of each?
> > 
> > Thanks,
> > 
> > 
> > -Original Message-
> > From: Ivo Stoyanov [mailto:ivos...@yahoo.com] 
> > Sent: Wednesday, March 17, 2010 8:10 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Adding multiple files to component
> > 
> > You can try this - simple GUI
> > http://flexsetup.codeplex.com/
> > WiXFileTool: generates WiX file definitions and component definitions for
> a collection of files
> > 
> > 
> > 
> > 
> > 
> > From: "Kerber, Cameron" 
> > To: General discussion for Windows Installer XML toolset.
> 
> > Sent: Tue, March 16, 2010 8:43:52 AM
> > Subject: Re: [WiX-users] Adding multiple files to component
> > 
> > Yes, I understand that you can put multiple files in a component, but that
> means I have to write the Source for each of the files, and spell out each
> file xml element. I basically just want to set the Source to a directory and
> include all files under that directory. Or some process that converts a
> directory to   
> > 
> > I can't be typing this each and everytime.
> > 
> > Heat tool. I'll look into it. 
> > 
> > Do you know of any websites with tutorial on it? Any way to integrate into
> MSBuild?
> > 
> > -Original Message-
> > From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se] 
> > Sent: Tuesday, March 16, 2010 11:36 AM
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Adding multipl

Re: [WiX-users] customising dialogs

[Jacek Pospychała]

hi,
see topic "Changing the UI sequence of a built-in dialog set" at
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm

Assuming that you're using Wix_InstallDir GUI mode, here you can see how it
is implemented:
http://wix.cvs.sourceforge.net/viewvc/wix/wix/src/ext/UIExtension/wixlib/WixUI_InstallDir.wxs?view=markup

You need to copy and paste that to your own wxs file and update the
references between pages.
To remove License agreement and install dir you would change this part:

1
1
LicenseAccepted = "1"

1
1
NOT WIXUI_DONTVALIDATEPATH

WIXUI_DONTVALIDATEPATH OR
WIXUI_INSTALLDIR_VALID="1"
1
1

NOT Installed
Installed

to look like this:

1

NOT Installed
Installed

You may also want to use some other predefined WiX UI.

HTH

Jacek


On Wed, Mar 17, 2010 at 1:38 PM, Eswari  wrote:

> Hi,
>
> How to suppress licenseagreement dialog and and installdirdialog(option for
> the user to select the installtion path) as i do not want show up these
> dialogs as mine is a simple installer.
>
> Thanks, Subramanyeswari
>
>
>
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding multiple files to component

[Albert At School]

I've been following this discussion and still I haven't seen the solution
we've build;

When we create an installer set we harvest the files into the appropriate
folders, then we have create a tool which scans which files are there.
The files are stored into a database where they are assigned a GUID for the
current release version (version 1.0, 1.2, 2.0 etc..)
When the file is already in the database only a datetimestamp is modified
and the GUID (for that specific version) stays the same. These files are
also marked as active.
At the end all files for the current release version where the datetimestamp
is not altered are marked as inactive.
>From this database we have a tool which can generate the WiX (component)
files for Minor updates, Major Updates and even patches between versions.
In this system there are more features like language independency,
x86/x64/IA64 handling etc.
I cannot donate this system to the community since it is a business thing :)
But I could describe parts of it so someone can build this for the WiX
community :)
We use it in our nightly builds to generate test-branche sets and
development-brance sets. For a definitive release we manyaly generate a
clean set and a set of patches.
The system is also WiX version independent; It can generate for WiX 2.0, 3.0
(current active release version) and 3.5.

Maybe this can help somebody started?

Regards,

Albert van Peppen

-Oorspronkelijk bericht-
Van: Kerber, Cameron [mailto:cameron.ker...@philips.com] 
Verzonden: woensdag 17 maart 2010 14:17
Aan: General discussion for Windows Installer XML toolset.
Onderwerp: Re: [WiX-users] Adding multiple files to component

Maybe, but it seems kind of silly.  So if have a directory fill with a
thousand help files, I need to manually maintain this.  Even if the tool
that generates the help files have a different name each time.  This seems
completely ridiculous that WiX doesn't have a way to handle this!

-Original Message-
From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se] 
Sent: Wednesday, March 17, 2010 8:57 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding multiple files to component


1) I believe I posted a detailed explanation on this. You should only use
heat manually!
 
> From: cameron.ker...@philips.com
> To: wix-users@lists.sourceforge.net
> Date: Wed, 17 Mar 2010 13:19:54 +0100
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> Thanks. I guess people have been giving me two different responses here
and I'm trying to figure out the right way to do this. 
> 
> 1) Should I use heat each time during a build, to harvest all the files in
a directory (directory contains a executable and all of its associated dlls
and dependencies). Then include that fragment with my main wix project.
> 
> 2) Or do I either use this WixFileTool or Heat to just generate this for
me once, add it to my Wix Project, and forever maintain that list of files.
Since we are still in the beginning of the development for this project, it
is likely files will be renamed/files will be added/files will be deleted.
> 
> What is the proper way / benefits of each?
> 
> Thanks,
> 
> 
> -Original Message-
> From: Ivo Stoyanov [mailto:ivos...@yahoo.com] 
> Sent: Wednesday, March 17, 2010 8:10 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> You can try this - simple GUI
> http://flexsetup.codeplex.com/
> WiXFileTool: generates WiX file definitions and component definitions for
a collection of files
> 
> 
> 
> 
> 
> From: "Kerber, Cameron" 
> To: General discussion for Windows Installer XML toolset.

> Sent: Tue, March 16, 2010 8:43:52 AM
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> Yes, I understand that you can put multiple files in a component, but that
means I have to write the Source for each of the files, and spell out each
file xml element. I basically just want to set the Source to a directory and
include all files under that directory. Or some process that converts a
directory to   
> 
> I can't be typing this each and everytime.
> 
> Heat tool. I'll look into it. 
> 
> Do you know of any websites with tutorial on it? Any way to integrate into
MSBuild?
> 
> -Original Message-
> From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se] 
> Sent: Tuesday, March 16, 2010 11:36 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> 
> I'm also a newbie, so my solution below could be "wrong". However, it
works:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Something like that. However, I do remember that this technique is not
recommended - for some reason I don't know...
> 
> 
> > From: cameron.ker...@philips.com
> > To: WiX-users@lists.sourceforge.net
> > Date: Tue, 16 Mar 2010 16:27:31 +0100
> > Subject: [WiX-users] Adding multiple files to compo

Re: [WiX-users] Adding multiple files to component

[Kerber, Cameron]

Maybe, but it seems kind of silly.  So if have a directory fill with a thousand 
help files, I need to manually maintain this.  Even if the tool that generates 
the help files have a different name each time.  This seems completely 
ridiculous that WiX doesn't have a way to handle this!

-Original Message-
From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se] 
Sent: Wednesday, March 17, 2010 8:57 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding multiple files to component


1) I believe I posted a detailed explanation on this. You should only use heat 
manually!
 
> From: cameron.ker...@philips.com
> To: wix-users@lists.sourceforge.net
> Date: Wed, 17 Mar 2010 13:19:54 +0100
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> Thanks. I guess people have been giving me two different responses here and 
> I'm trying to figure out the right way to do this. 
> 
> 1) Should I use heat each time during a build, to harvest all the files in a 
> directory (directory contains a executable and all of its associated dlls and 
> dependencies). Then include that fragment with my main wix project.
> 
> 2) Or do I either use this WixFileTool or Heat to just generate this for me 
> once, add it to my Wix Project, and forever maintain that list of files. 
> Since we are still in the beginning of the development for this project, it 
> is likely files will be renamed/files will be added/files will be deleted.
> 
> What is the proper way / benefits of each?
> 
> Thanks,
> 
> 
> -Original Message-
> From: Ivo Stoyanov [mailto:ivos...@yahoo.com] 
> Sent: Wednesday, March 17, 2010 8:10 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> You can try this - simple GUI
> http://flexsetup.codeplex.com/
> WiXFileTool: generates WiX file definitions and component definitions for a 
> collection of files
> 
> 
> 
> 
> 
> From: "Kerber, Cameron" 
> To: General discussion for Windows Installer XML toolset. 
> 
> Sent: Tue, March 16, 2010 8:43:52 AM
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> Yes, I understand that you can put multiple files in a component, but that 
> means I have to write the Source for each of the files, and spell out each 
> file xml element. I basically just want to set the Source to a directory and 
> include all files under that directory. Or some process that converts a 
> directory to   
> 
> I can't be typing this each and everytime.
> 
> Heat tool. I'll look into it. 
> 
> Do you know of any websites with tutorial on it? Any way to integrate into 
> MSBuild?
> 
> -Original Message-
> From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se] 
> Sent: Tuesday, March 16, 2010 11:36 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> 
> I'm also a newbie, so my solution below could be "wrong". However, it works:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Something like that. However, I do remember that this technique is not 
> recommended - for some reason I don't know...
> 
> 
> > From: cameron.ker...@philips.com
> > To: WiX-users@lists.sourceforge.net
> > Date: Tue, 16 Mar 2010 16:27:31 +0100
> > Subject: [WiX-users] Adding multiple files to component
> > 
> > I'm sure this question has been asked before in some variety but searching 
> > the mail archives on SourceForge is awful. I am also new to WIX
> > 
> > Anyways, in my build process I am outputting a bunch of files to a 
> > directory. I want all those files added to a component in my WIX project. 
> > To build my WIX project, during my build process I just build my WIX 
> > installer solution and it creates the setup package. So besides manually 
> > adding all these files (~50) to my component by hand, I don't understand 
> > how to accomplish this. All the tutorials just use one file in there 
> > examples. No one uses adding files from a source directory.
> > 
> > Thanks!
> > 
> > 
> > The information contained in this message may be confidential and legally 
> > protected under applicable law. The message is intended solely for the 
> > addressee(s). If you are not the intended recipient, you are hereby 
> > notified that any use, forwarding, dissemination, or reproduction of this 
> > message is strictly prohibited and may be unlawful. If you are not the 
> > intended recipient, please contact the sender by return e-mail and destroy 
> > all copies of the original message.
> > --
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > 

[WiX-users] suppressing custom dialogs

[subramanyeswari]

Hi,

I want to suuppress licenseagreement dialog and the dialog where it will
allow the change in the install path as mine is a simple installer.

How to do that?

Thanks, Subramanyeswari
-- 
View this message in context: 
http://n2.nabble.com/suppressing-custom-dialogs-tp4750044p4750044.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding multiple files to component

[Kristoffer Danielsson]

1) I believe I posted a detailed explanation on this. You should only use heat 
manually!
 
> From: cameron.ker...@philips.com
> To: wix-users@lists.sourceforge.net
> Date: Wed, 17 Mar 2010 13:19:54 +0100
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> Thanks. I guess people have been giving me two different responses here and 
> I'm trying to figure out the right way to do this. 
> 
> 1) Should I use heat each time during a build, to harvest all the files in a 
> directory (directory contains a executable and all of its associated dlls and 
> dependencies). Then include that fragment with my main wix project.
> 
> 2) Or do I either use this WixFileTool or Heat to just generate this for me 
> once, add it to my Wix Project, and forever maintain that list of files. 
> Since we are still in the beginning of the development for this project, it 
> is likely files will be renamed/files will be added/files will be deleted.
> 
> What is the proper way / benefits of each?
> 
> Thanks,
> 
> 
> -Original Message-
> From: Ivo Stoyanov [mailto:ivos...@yahoo.com] 
> Sent: Wednesday, March 17, 2010 8:10 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> You can try this - simple GUI
> http://flexsetup.codeplex.com/
> WiXFileTool: generates WiX file definitions and component definitions for a 
> collection of files
> 
> 
> 
> 
> 
> From: "Kerber, Cameron" 
> To: General discussion for Windows Installer XML toolset. 
> 
> Sent: Tue, March 16, 2010 8:43:52 AM
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> Yes, I understand that you can put multiple files in a component, but that 
> means I have to write the Source for each of the files, and spell out each 
> file xml element. I basically just want to set the Source to a directory and 
> include all files under that directory. Or some process that converts a 
> directory to   
> 
> I can't be typing this each and everytime.
> 
> Heat tool. I'll look into it. 
> 
> Do you know of any websites with tutorial on it? Any way to integrate into 
> MSBuild?
> 
> -Original Message-
> From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se] 
> Sent: Tuesday, March 16, 2010 11:36 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Adding multiple files to component
> 
> 
> I'm also a newbie, so my solution below could be "wrong". However, it works:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Something like that. However, I do remember that this technique is not 
> recommended - for some reason I don't know...
> 
> 
> > From: cameron.ker...@philips.com
> > To: WiX-users@lists.sourceforge.net
> > Date: Tue, 16 Mar 2010 16:27:31 +0100
> > Subject: [WiX-users] Adding multiple files to component
> > 
> > I'm sure this question has been asked before in some variety but searching 
> > the mail archives on SourceForge is awful. I am also new to WIX
> > 
> > Anyways, in my build process I am outputting a bunch of files to a 
> > directory. I want all those files added to a component in my WIX project. 
> > To build my WIX project, during my build process I just build my WIX 
> > installer solution and it creates the setup package. So besides manually 
> > adding all these files (~50) to my component by hand, I don't understand 
> > how to accomplish this. All the tutorials just use one file in there 
> > examples. No one uses adding files from a source directory.
> > 
> > Thanks!
> > 
> > 
> > The information contained in this message may be confidential and legally 
> > protected under applicable law. The message is intended solely for the 
> > addressee(s). If you are not the intended recipient, you are hereby 
> > notified that any use, forwarding, dissemination, or reproduction of this 
> > message is strictly prohibited and may be unlawful. If you are not the 
> > intended recipient, please contact the sender by return e-mail and destroy 
> > all copies of the original message.
> > --
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> _
> Mejla i busskön! Hotmail i mobilen
> http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed

Re: [WiX-users] heat on VB6

[Neil Sleightholm]

Vb6 com dlls include registration information for the vb6 runtime in  
their selfreg code (this is why selfreg is evil). This option excludes  
that information so that uninstalling the component does break the vb6  
runtime.

Neil

Neil Sleightholm
n...@x2systems.com

On 16 Mar 2010, at 12:50, "Bill McCormick"   
wrote:

> What does it mean to surpress COM elements? Some of my VB6 apps  
> actually
> have COM elements that other apps use.
>
> Thanks,
>
> Bill
> Pally Sandher wrote:
>> Yes.
>> Remember to use -svb6 though.
>>
>>
>> Palbinder Sandher
>> Software Deployment & IT Administrator
>> T: +44 (0) 141 945 8500
>> F: +44 (0) 141 945 8501
>>
>> http://www.iesve.com
>> **Design, Simulate + Innovate with the **
>> Integrated Environmental Solutions Limited. Registered in Scotland  
>> No.
>> SC151456
>> Registered Office - Helix Building, West Of Scotland Science Park,
>> Glasgow G20 0SP
>> Email Disclaimer
>>
>>
>> -Original Message-
>> From: Bill McCormick [mailto:wpmccorm...@ace-co.com]
>> Sent: 16 March 2010 16:19
>> To: WIX
>> Subject: [WiX-users] heat on VB6
>>
>> can I use heat to melt a VB6 project?
>>
>> Thanks,
>>
>> Bill
>>
>> --- 
>> -
>> --
>> Download Intel® Parallel Studio Eval Try the new software  
>> tools for
>> yourself. Speed compiling, find bugs proactively, and fine-tune
>> applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>>
>>
>> --- 
>> --- 
>> --- 
>> -
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>
>
>
> --- 
> --- 
> --- 
> -
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] customising dialogs

[Eswari]

Hi,

How to suppress licenseagreement dialog and and installdirdialog(option for the 
user to select the installtion path) as i do not want show up these dialogs as 
mine is a simple installer.

Thanks, Subramanyeswari


  

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding multiple files to component

[Kerber, Cameron]

Thanks.  I guess people have been giving me two different responses here and 
I'm trying to figure out the right way to do this. 

1) Should I use heat each time during a build, to harvest all the files in a 
directory (directory contains a executable and all of its associated dlls and 
dependencies).  Then include that fragment with my main wix project.

2) Or do I either use this WixFileTool or Heat to just generate this for me 
once, add it to my Wix Project, and forever maintain that list of files.  Since 
we are still in the beginning of the development for this project, it is likely 
files will be renamed/files will be added/files will be deleted.

What is the proper way / benefits of each?

Thanks,


-Original Message-
From: Ivo Stoyanov [mailto:ivos...@yahoo.com] 
Sent: Wednesday, March 17, 2010 8:10 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding multiple files to component

You can try this - simple GUI
http://flexsetup.codeplex.com/
WiXFileTool: generates WiX file definitions and component definitions for a 
collection of files





From: "Kerber, Cameron" 
To: General discussion for Windows Installer XML toolset. 

Sent: Tue, March 16, 2010 8:43:52 AM
Subject: Re: [WiX-users] Adding multiple files to component

Yes, I understand that you can put multiple files in a component, but that 
means I have to write the Source for each of the files, and spell out each file 
xml element.  I basically just want to set the Source to a directory and 
include all files under that directory.  Or some process that converts a 
directory to   

I can't be typing this each and everytime.

Heat tool.  I'll look into it.  

Do you know of any websites with tutorial on it?  Any way to integrate into 
MSBuild?

-Original Message-
From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se] 
Sent: Tuesday, March 16, 2010 11:36 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding multiple files to component


I'm also a newbie, so my solution below could be "wrong". However, it works:





  







  




Something like that. However, I do remember that this technique is not 
recommended - for some reason I don't know...


> From: cameron.ker...@philips.com
> To: WiX-users@lists.sourceforge.net
> Date: Tue, 16 Mar 2010 16:27:31 +0100
> Subject: [WiX-users] Adding multiple files to component
> 
> I'm sure this question has been asked before in some variety but searching 
> the mail archives on SourceForge is awful. I am also new to WIX
> 
> Anyways, in my build process I am outputting a bunch of files to a directory. 
> I want all those files added to a component in my WIX project. To build my 
> WIX project, during my build process I just build my WIX installer solution 
> and it creates the setup package. So besides manually adding all these files 
> (~50) to my component by hand, I don't understand how to accomplish this. All 
> the tutorials just use one file in there examples. No one uses adding files 
> from a source directory.
> 
> Thanks!
> 
> 
> The information contained in this message may be confidential and legally 
> protected under applicable law. The message is intended solely for the 
> addressee(s). If you are not the intended recipient, you are hereby notified 
> that any use, forwarding, dissemination, or reproduction of this message is 
> strictly prohibited and may be unlawful. If you are not the intended 
> recipient, please contact the sender by return e-mail and destroy all copies 
> of the original message.
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
  
_
Mejla i busskön! Hotmail i mobilen
http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Download Intel® Parallel Studio Eval
Try the new sof

Re: [WiX-users] Adding multiple files to component

[Ivo Stoyanov]

You can try this - simple GUI
http://flexsetup.codeplex.com/
WiXFileTool: generates WiX file definitions and component definitions for a 
collection of files





From: "Kerber, Cameron" 
To: General discussion for Windows Installer XML toolset. 

Sent: Tue, March 16, 2010 8:43:52 AM
Subject: Re: [WiX-users] Adding multiple files to component

Yes, I understand that you can put multiple files in a component, but that 
means I have to write the Source for each of the files, and spell out each file 
xml element.  I basically just want to set the Source to a directory and 
include all files under that directory.  Or some process that converts a 
directory to   

I can't be typing this each and everytime.

Heat tool.  I'll look into it.  

Do you know of any websites with tutorial on it?  Any way to integrate into 
MSBuild?

-Original Message-
From: Kristoffer Danielsson [mailto:kristoffer.daniels...@live.se] 
Sent: Tuesday, March 16, 2010 11:36 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding multiple files to component


I'm also a newbie, so my solution below could be "wrong". However, it works:





  







  




Something like that. However, I do remember that this technique is not 
recommended - for some reason I don't know...


> From: cameron.ker...@philips.com
> To: WiX-users@lists.sourceforge.net
> Date: Tue, 16 Mar 2010 16:27:31 +0100
> Subject: [WiX-users] Adding multiple files to component
> 
> I'm sure this question has been asked before in some variety but searching 
> the mail archives on SourceForge is awful. I am also new to WIX
> 
> Anyways, in my build process I am outputting a bunch of files to a directory. 
> I want all those files added to a component in my WIX project. To build my 
> WIX project, during my build process I just build my WIX installer solution 
> and it creates the setup package. So besides manually adding all these files 
> (~50) to my component by hand, I don't understand how to accomplish this. All 
> the tutorials just use one file in there examples. No one uses adding files 
> from a source directory.
> 
> Thanks!
> 
> 
> The information contained in this message may be confidential and legally 
> protected under applicable law. The message is intended solely for the 
> addressee(s). If you are not the intended recipient, you are hereby notified 
> that any use, forwarding, dissemination, or reproduction of this message is 
> strictly prohibited and may be unlawful. If you are not the intended 
> recipient, please contact the sender by return e-mail and destroy all copies 
> of the original message.
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
  
_
Mejla i busskön! Hotmail i mobilen
http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Disable UI in patch by default

[Oleksandr Y. Nechyporenko]

Thank you very much for reply.

Sorry, but I'm not sure where I should specify this custom action.
Should I specify it in "mailto:pally.sand...@iesve.com] 
Sent: Tuesday, March 16, 2010 7:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Disable UI in patch by default

http://msdn.microsoft.com/en-us/library/aa369759.aspx 

Use a type 51 custom action to set that & condition it with "PATCH AND
Installed".

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer

-Original Message-
From: Oleksandr Y. Nechyporenko [mailto:alexnc69...@gmail.com] 
Sent: 16 March 2010 14:29
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] Disable UI in patch by default

Hi All,

 

I've created install for our product. Now I've created a path as
described here http://wix.sourceforge.net/manual-wix3/wix_patching.htm.

 

Is there way to hide user interface when MSP file is running by mouse
double click? I've used in WixUI_Mondo in my setup project.

Now when I run MSP by double click the user interface is also appeared.
I want to create silent patch install by default, like MS Office MSPs
works.

 

Is there any directive or tag which I can specify in patch's wxs file
which will create patch without UI?

 

Thanks.

 


--
Download Intel® Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Specify version number in Support Information window

[C P]

Thanks. I set Version attribute for Product element in format x.x.y.z and it
is displayed correctly in Show Info window, but the issue is - actual
application version is e.g. 1.260.1.25, but msi cannot be compiled due to
installer restriction (major and minor should be less than 256). So I
thought there is simple way to update DisplayVersion. Is there the only way
out to update registry after install?

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Tuesday, March 16, 2010 8:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Specify version number in Support Information
window

Works fine for me in all our MSI's & I don't do any special ARP property
settings for it unlike a lot of the other items on that dialog.

Are you setting the Version attribute correctly on your Product element?
It should be something like 1.2.3.4 & I think the maximum value you can
use for any of the 4 fields is 32768.
As far as I know it's read from the "DisplayVersion" string in the
registry under your products Uninstall information (see
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{YOUR-PRODUCT-G
UID-HERE}\). Make sure that's set properly after installation for your
product if it's still not showing up.

Comments you can do with
Insert your comment here.

See http://msdn.microsoft.com/en-us/library/aa370905.aspx for other
similar Properties relating to the ARP dialogs.

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
 
-Original Message-
From: C P [mailto:chilavegp...@mail.ru] 
Sent: 16 March 2010 16:07
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Specify version number in Support Information
window

Hi All,

 

could you please tell is there a ability to specify
version in Support Info dialog like it's done for e.g. Firefox -
"Version: 3.6 (En-US)". To see Support Info you should go to Control
Panel -> Add or Remove Programs select Firefox and click on "Click here
for support information" link.

Also how can I show string Comments: in Support Info?

 

Thanks,

TKI

 

 


--
Download Intel® Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Unsubscribe

[Vegard Sandberg]

Ok, thanks:)

Mvh
Vegard Sandberg

-Original Message-
From: Jacek Pospychała [mailto:jacek.pospych...@gmail.com] 
Sent: 17. mars 2010 11:14
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Unsubscribe

Vegard,
to unsubscribe, go to https://lists.sourceforge.net/lists/listinfo/wix-users
You only need to type your e-mail address to unsubscribe.

On Wed, Mar 17, 2010 at 8:09 AM, Vegard Sandberg
wrote:

> Hi!
>
> I want to unsubscribe from wix users list, but I seem to have lost my
> password.
>
>
>
>
>
> Kind Regards
>
> 
>
> Vegard Sandberg
>
> Systemutvikler
>
> Visma Unique AS, PB 246, Ranvik Brygge 5, 3201 Sandefjord
>
> Sentralbord:   +47 33 44 84 00
>
> Mobil:   +47 93 26 27 95
>
> http://www.visma.no/offentlig 
>
> This communication is intended for the person(s) named above only. It
> contains information that is confidential and legally privileged. If
> received in error, please delete this e-mail and notify the sender.
>
> 
>
>
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Unsubscribe

[Jacek Pospychała]

Vegard,
to unsubscribe, go to https://lists.sourceforge.net/lists/listinfo/wix-users
You only need to type your e-mail address to unsubscribe.

On Wed, Mar 17, 2010 at 8:09 AM, Vegard Sandberg
wrote:

> Hi!
>
> I want to unsubscribe from wix users list, but I seem to have lost my
> password.
>
>
>
>
>
> Kind Regards
>
> 
>
> Vegard Sandberg
>
> Systemutvikler
>
> Visma Unique AS, PB 246, Ranvik Brygge 5, 3201 Sandefjord
>
> Sentralbord:   +47 33 44 84 00
>
> Mobil:   +47 93 26 27 95
>
> http://www.visma.no/offentlig 
>
> This communication is intended for the person(s) named above only. It
> contains information that is confidential and legally privileged. If
> received in error, please delete this e-mail and notify the sender.
>
> 
>
>
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] minor issues with WiX installer gui

[Jacek Pospychała]

This time, it's WiX dialog. On attached screenshot you can see which exactly
button is stuck.

thanks for the disk space information!

Jacek


2010/3/16 Wilson, Phil 

> Is the repair a WiX dialog? These are typically standard Windows Installer
> dialogs.
>
> Disk space:
>
>
> http://blogs.msdn.com/heaths/archive/2008/07/24/why-windows-installer-may-require-so-much-disk-space.aspx
>
> Phil Wilson
>
> -Original Message-
> From: Jacek Pospychała [mailto:jacek.pospych...@gmail.com]
> Sent: Tuesday, March 16, 2010 7:16 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] minor issues with WiX installer gui
>
> hi WiXers,
> I'd like to share with you my excitement that product I'm working with, has
> almost ready MSI installer thanks to WiX!
> I still have some questions though :-)
>
> 1. We noticed that when pressing "Repair" or "Remove" button - on the last
> page of Repair and Remove wizards respectively, GUI hangs for significant
> time before going to the progress dialog. In this sate "Repair" button
> remains pressed, and only busy cursor icon indicates that something is
> going
> on. With Process Monitor that explorer.exe is going thru all the
> application
> files performing operations: CreateFile, QueryBasicInformationFile,
> QueryStandardInformationFile, CloseFile, CreateFileMapping, etc.
>
> What's happening after pressing those buttons and before going to the
> progress dialog? Is there any way to control that? At worst it takes up to
> few minutes! (Our application is big)
>
> 2. The application requires 500MB disk space. This is correctly reflected
> in
> CustomDlg, which shows correct features sizes. However "Required Space"
> dialog says that 1G is required. How is required space calculated by
> default?
>
>
> thanks
>
> Jacek
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> *** Confidentiality Notice: This e-mail, including any associated or
> attached files, is intended solely for the individual or entity to which it
> is addressed. This e-mail is confidential and may well also be legally
> privileged. If you have received it in error, you are on notice of its
> status. Please notify the sender immediately by reply e-mail and then delete
> this message from your system. Please do not copy it or use it for any
> purposes, or disclose its contents to any other person. This email comes
> from a division of the Invensys Group, owned by Invensys plc, which is a
> company registered in England and Wales with its registered office at
> Portland House, Bressenden Place, London, SW1E 5BF (Registered number
> 166023). For a list of European legal entities within the Invensys Group,
> please go to
> http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.
> You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail
> inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may
> be subject to the terms of any agreements between Invensys (and/or its
> subsidiaries and affiliates) and the recipient (and/or its subsidiaries and
> affiliates).
>
>
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Unsubscribe

[Vegard Sandberg]

Hi!

I want to unsubscribe from wix users list, but I seem to have lost my
password.

 

 

Kind Regards



Vegard Sandberg

Systemutvikler 

Visma Unique AS, PB 246, Ranvik Brygge 5, 3201 Sandefjord 

Sentralbord:   +47 33 44 84 00

Mobil:   +47 93 26 27 95

http://www.visma.no/offentlig  

This communication is intended for the person(s) named above only. It
contains information that is confidential and legally privileged. If
received in error, please delete this e-mail and notify the sender.



 

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Invert Feature based on other Feature

[Dave Brotherstone]

Hi all,

I have a feature that controls where the config file for our application is
located (either "locally" next to the exe in Program Files, or in
%APPDATA%).  When this feature is selected, the config file is copied
correctly to the right place, and the indicator file (to let the .exe know
that the config should be loaded next to the .exe rather than %APPDATA%) is
also created.

However, if this feature is not selected, I need to place the config file in
%APPDATA%.  I had attempted to do this with a hidden feature for the appdata
config, and conditions on the main feature action, but that doesn't seem to
work.

FT_DOLOCALCONF is the feature that is shown to the user.  I've tried with !
states as well, but from what I've read action state is correct to use in
this case?


NOT &FT_DOLOCALCONF=3
&FT_DOLOCALCONF=3

 


Many thanks for any pointers,

Dave.
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users