Re: [WiX-users] Using Product Id="*"

2013-02-21 Thread Gary Ewan Park
Hey, Thanks for replying! Perhaps I should provide some more information... I am helping out with creating an OSS project called ChocolateyGUI. This involves creating an MSI package, which is then wrapped into a nuget package, and then which is available in install from chocolatey.org. The n

Re: [WiX-users] InstallUISequence

2013-02-21 Thread Joseph, Sijo
Thanks Steve, It worked... Thanks, Sijo Joseph -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: 20 February 2013 17:25 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] InstallUISequence If you're talking about the bitmap

Re: [WiX-users] Service call from Custom Action

2013-02-21 Thread Christopher Painter
Not that I'm aware of. Other then why? From: keith.doug...@statcan.gc.ca Sent: Thursday, February 21, 2013 4:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Service call from Custom Action Are there any gotchas one should know about cal

[WiX-users] Service call from Custom Action

2013-02-21 Thread Keith.Douglas
Are there any gotchas one should know about calling a (noninteractive) Windows Service (built to answer IPC, etc. with .NET Remoting) from a custom action? Keith Douglas Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ot

Re: [WiX-users] WixLib not behaving as desired

2013-02-21 Thread Marc Beaudry
I have a property that should be self-contained in my lib. I simply added a Ref in the Product file, but it is not used in that file except for the ref. I prefer this solution over exposing the ComponentRef in the Product file since they are also self-contained. My initial intentions and understa

Re: [WiX-users] Obsoleted msi exists after minor update.

2013-02-21 Thread Rob Mensching
What did the uninstall log of the new bundle say about the old.msi? If I understand correctly, the old.msi should have been minor upgraded to the new.msi. Then the uninstall of new bundle should have removed new.msi and old.msi was already gone. The old.msi in the cache is a bug, known I believe.

Re: [WiX-users] WixLib not behaving as desired

2013-02-21 Thread Rob Mensching
Did you have a Property in the Fragment when you started? If not, I'd use something that "exists naturally" in the Fragment. If so, good on ya. On Thu, Feb 21, 2013 at 10:43 AM, Marc Beaudry wrote: > Sorry for the late reply Thanks Rob and Jacob for the advice. > > Once the issue was solv

Re: [WiX-users] What is "LaunchAction.Layout" used for?

2013-02-21 Thread Rob Mensching
...or just copy it to a network share to distribute about your company. Tom's right. Whether you want to distribute software via sneaker-net is your call. On Thu, Feb 21, 2013 at 11:05 AM, tom wrote: > > > As far as i know this (should) downloads all packages and extract other so > you can bur

Re: [WiX-users] What is "LaunchAction.Layout" used for?

2013-02-21 Thread tom
As far as i know this (should) downloads all packages and extract other so you can burn eveything on a CD -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/What-is-LaunchAction-Layout-used-for-tp7583829p7583849.html Sent from the wix-users mailing

Re: [WiX-users] WixLib not behaving as desired

2013-02-21 Thread Marc Beaudry
Sorry for the late reply Thanks Rob and Jacob for the advice. Once the issue was solved I was curious to know best practice usage. BTW: I changed my ComponentRef to PropertyRef -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: February-20-2013 6:14 PM To:

Re: [WiX-users] Rename File based on ArgumentpassedtoMSIInstallation

2013-02-21 Thread Peter Shirtcliffe
See the Wix help for CopyFile. -Original Message- From: chennam [mailto:chatrapathi.chen...@gmail.com] Sent: 21 February 2013 16:22 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Rename File based on ArgumentpassedtoMSIInstallation Thanks Peter.. Another question is does

Re: [WiX-users] Obsoleted msi exists after minor update.

2013-02-21 Thread AK
It`s not a big trouble, that both msi (1.2.3.0 and 1.2.4.0) are still in the cache after the minor update. After uninstall new bundle, old msi was not uninstalled - that is the trouble. Alexey. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Obsol

Re: [WiX-users] Rename File based on Argument passedtoMSIInstallation

2013-02-21 Thread chennam
Thanks Peter.. Another question is does the source file of copyfile should on destination system? or Source file can be part of MSI package(after heat) and during installation process we can rename the file using Copyfile? -- View this message in context: http://windows-installer-xml-wix-t

Re: [WiX-users] Rename File based on Argument passedtoMSIInstallation

2013-02-21 Thread Peter Shirtcliffe
Yes, I'm talking about the file & component of the file that you want to copy/rename. FFF should be replaced with the Id of the File element. CCC should be replaced with the Id of the Component that is the parent of the same file element. CostFinalize is just the place in the execute sequence wher

Re: [WiX-users] Rename File based on Argument passed toMSIInstallation

2013-02-21 Thread chennam
Hi Peter I was bit confused ,please bear with me. Where FFF is the file ID of the source file. Here FFF is the fileId which is generated in Heat output file? and here "CostFinalize" is some feature? Where CCC is the Component ID of the source file. Here CCC is the Component ID which is

[WiX-users] CustomAction : FirstSequence/Rollback, OncePerProcess/Commit

2013-02-21 Thread Gabriel Ivanes
Hello, Anyone knows why does the bit FirstSequence automatically set Rollback's bit ? The same with OncePerProcess and Commit. I made an immediat custom action with FirstSequence but i don't want rollback's bit. No problem in execution, but i'm just curious why. Thanks. --

Re: [WiX-users] Authenticode verification fails on clean WindowsXp sp3

2013-02-21 Thread David Watson
I would write a KB article that explains the issue and leave it as is. Windows machines need updates installed whether it's via the internet or an internal update server, it's not your installers job to do basic IT tasks for an organisation. Dave -Original Message- From: Sørensen, Rune [

Re: [WiX-users] Using Product Id="*"

2013-02-21 Thread Gabriel Ivanes
Hello, If you plan an upgrade, why do you need ProductCode of the previous version ? Le %:Date:, Gary Ewan Park a écrit: > Hello, > > I am still quite new to WiX, so please bear with me... > > I have implemented the following pattern: > > http://wix.sourceforge.net/manual-wix3/major_upgrade.h

Re: [WiX-users] Authenticode verification fails on clean Windows Xp sp3

2013-02-21 Thread Sørensen , Rune
Installing the updated root certificates manually did indeed resolve the issue. The next issue is to determine how to install the root certificates using Burn before the other packages is verified?? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: 21. febru

Re: [WiX-users] Using Product Id="*"

2013-02-21 Thread Peter Shirtcliffe
You can use the ProductCode property within the MSI. http://msdn.microsoft.com/en-gb/library/windows/desktop/aa370854%28v=vs.85%29 .aspx If by "package" you mean a bootstrapper or something else external to the MSI then you can open the MSI with InstEd or Orca and examine the Property table for t

Re: [WiX-users] Authenticode verification fails on clean Windows Xp sp3

2013-02-21 Thread Peter Shirtcliffe
You might be missing the necessary root certificate on those machines. I think this is the link you need. Some certificates are updated by Windows Update but not all so look at the certificate chain of the exe (right click / properties) on an affected machine to see if it is installed. http://www.m

Re: [WiX-users] Burn Localisation

2013-02-21 Thread Neil Sleightholm
I think the wrong API call is being used in locutil.cpp. The burn variable UserLanguageID uses GetUserDefaultLangID which returns the correct value 2057 (en-uk), LocProbeForFile uses GetUserDefaultUILanguage which returns 1033 (en-us). Detecting the user language in Windows can be really tricky so