[WiX-users] Setting date and time of files in a cabinet

2011-08-25 Thread Darren Bennett
Is there some way to set the date and time for files contained in a cabinet built using WiX? In the past I have created our cabinets using the MakeCAB tool and was able to set the date and time for all files in the cabinet using the .Set InfDate and .Set InfTime properties in the MakeCAB inf file.

Re: [WiX-users] Wix 3.6 : command line switches question "\qn" and/or "\forcerestart"

2011-08-25 Thread Sheehan, Andrew
Thanks! Sent from my iPhone On Aug 25, 2011, at 7:15 PM, "Rob Mensching" wrote: > 1. There is a bug in rollback handling of Burn. DisableRollback="yes" will > cause Burn to not rollback (but leave all your packages on the machine if > there is a failure/cancel). The bug will get fixed. > > 2

Re: [WiX-users] Wix 3.6 : command line switches question "\qn" and/or "\forcerestart"

2011-08-25 Thread Rob Mensching
1. There is a bug in rollback handling of Burn. DisableRollback="yes" will cause Burn to not rollback (but leave all your packages on the machine if there is a failure/cancel). The bug will get fixed. 2. When installing NETFX 4, I suggest setting ExePackage/@Protocol="netfx" and you'll get progr

Re: [WiX-users] WiX Burn - Loading prerequisite bootstrapper application because managed host could not be loaded

2011-08-25 Thread Shaun Hayward
I managed to get a managed WinForms (not WPF) bootstrapper working - and it's .NET 4. One thing I was missing was the [assembly: BootstrapperApplication(typeof(MyBootstrapperAppClassNameHere))] attribute in AssemblyInfo.cs. I also had to define the WixMbaPrereqPackageId and WixMbaPrereqLicenseU

[WiX-users] file content dependent delta patch bug within windows xp?

2011-08-25 Thread Alexander Stock
We observed a rarely occuring patch issue resulting in not working updates on windows xp. It was possible to reproduce the issue in a little sample project with only one file included. According to our observations, the file contents are crucial to reproduce the issue. A simple rebuild of the file

[WiX-users] Preserve generated files on MajorUpgrade, but remove on uninstall

2011-08-25 Thread Sameer Arora
Hi, I have defined a component to cleanup a generated (not part of msi) file on uninstall but leave intact on a major upgrade after reading this post http://stackoverflow.com/questions/488620/wix-major-upgrade REMOVE="ALL" AND NOT UPGRADINGPRODUCTCODE With condition above, the file is le

[WiX-users] ICE57 errors on a per-machine install

2011-08-25 Thread Bernie Schoch
I have a per-machine install. I've separated the different file pieces into different fragments/components and the shortcuts also as a separate component. I'm getting an *Error 14 ICE57: Component 'CMP_MenuShortCuts' has both per-user data and a keypath that can be either per-user or per-machine

Re: [WiX-users] WiX Burn - Loading prerequisite bootstrapper application because managed host could not be loaded - Email found in subject

2011-08-25 Thread Shaun Hayward
Thanks, Tobias. When removing Netfx4Full, it won't compile. WixBalExtension needs a reference to two variables: WixMbaPrereqPackageId and WixMbaPrereqLicenseUrl. Those variables only have meaning if I have .NET 4 stuff defined. Odd, though, that the pre-req bootstrapper that it defaults to does

Re: [WiX-users] Replace component on reinstall

2011-08-25 Thread The Eligible Bachelors
Thank you for your ideas. I will fiddle with Mike's solution and see if I can get things going as I would like. The more I read about my scenario, the more I realize it is probably best to not be overwriting a user-edited file, in fact. So perhaps I am going down the wrong road. Cheers. --

Re: [WiX-users] Identifying Features that have been installed

2011-08-25 Thread Anil Patel
Thanks for that advice Peter. I'll with the int. Cheers, Anil. On Thu, Aug 25, 2011 at 4:54 PM, Peter Shirtcliffe wrote: > I'd be very surprised if that were the case. With each release of the > Windows > OS and Windows Installer, new error codes are added. At some future date, > the > API funct

Re: [WiX-users] Identifying Features that have been installed

2011-08-25 Thread Peter Shirtcliffe
I'd be very surprised if that were the case. With each release of the Windows OS and Windows Installer, new error codes are added. At some future date, the API functions could return an error code that is not within your enum's legal set of values. Stick with an int. -Original Message- Fro

Re: [WiX-users] Identifying Features that have been installed

2011-08-25 Thread Anil Patel
The numeric codes for the symbolics can be looked up here but I'm sure there is a way to get the Enums for them. http://msdn.microsoft.com/en-us/library/18d8fbe8-a967-4f1c-ae50-99ca8e491d2d(PROT.10).aspx On Thu, Aug 25, 2011 at 4:26 PM, Anil Patel wrote: > Hi Peter & James, > > I really appreci

Re: [WiX-users] Identifying Features that have been installed

2011-08-25 Thread Anil Patel
Hi Peter & James, I really appreciate your help on this - thank you!! I went with the interop route and attach a sample app (if anyone is interested) in what I have done. Best Regards, Anil. using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Runti

Re: [WiX-users] Identifying Features that have been installed

2011-08-25 Thread James Johnston
You could always use the COM library if you're not comfortable with the C API calls. Add a COM reference to "Microsoft Windows Installer Object Library" to your project... Installer.get_Features and Installer.get_FeatureState look like they might be useful. -Original Message- From: Anil

Re: [WiX-users] Std Bootstrapper failed: Error

2011-08-25 Thread Vadym Verba
There are .Net updates after which defect is not reproducible: Update for Microsoft .NET Framework 4 on Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008 x86 (KB2533523) This update addresses stability, reliability, and performance issues in Microsoft .NET Framewor

Re: [WiX-users] Identifying Features that have been installed

2011-08-25 Thread Peter Shirtcliffe
I don't really do C# programming. However those nice Wix people have already done it for you. Look at the DTF help file in Wix for the ComponentInstallation class. Something like new ComponentInstallation("").Product.Features would enumerate your installed features. -Original Message- Fr

Re: [WiX-users] Identifying Features that have been installed

2011-08-25 Thread Anil Patel
Hi Peter, Really appreciate your feedback on this. The MsiGetEnumsFeatues() is defined as UINT MsiEnumFeatures( __in LPCTSTR szProduct, __in DWORD iFeatureIndex, __out LPTSTR lpFeatureBuf, __out LPTSTR lpParentBuf ); So to get the product code, I found this code [DllImpor

Re: [WiX-users] Identifying Features that have been installed

2011-08-25 Thread Peter Shirtcliffe
MsiEnumFeatures() http://msdn.microsoft.com/en-us/library/aa370098%28v=vs.85%29.aspx -Original Message- From: Anil Patel [mailto:apatel...@googlemail.com] Sent: 25 August 2011 11:08 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Identifying Features that h

[WiX-users] Identifying Features that have been installed

2011-08-25 Thread Anil Patel
Hello, I have a configuration program that is run manually by a user (following a new install or a change to an existing installation) which allows the user to configure the installed features. There is a requirement to disable the configuration of features not installed by the user. The questio

Re: [WiX-users] Replace component on reinstall

2011-08-25 Thread Rob Hamflett
The attribute is called DefaultVersion, although if the component is shared with other installers you might be better off going with Mike's suggestion about companion files. Rob On 24/08/2011 20:01, The Eligible Bachelors wrote: > I do not know how to "specify a version on the File element" as

Re: [WiX-users] WiX Burn - Loading prerequisite bootstrapper application because managed host could not be loaded

2011-08-25 Thread Tobias S
maybe 2 aspects: - what happens when removing the and preinstall it manually ? - there was yesterday a discussion about similar code here: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-Troubleshoot-Bootstrapper-Application-Startup-td6717206.html. Maybe diffing it against tha