[WiX-users] Customizing a Maintenance Type Dialog

2012-07-03 Thread eddie burkowich
Although i am asking this questions as copied from http://stackoverflow.com/questions/11288820/customizing-a-maintainencetypedialog-not-successful, i also faced the same problem that i have not been able to modify the MaintenanceWelcomeDialog, as per alexey's advice i tried to do what he mentioned

Re: [WiX-users] Customizing a Maintenance Type Dialog

2012-07-03 Thread Ravi Raj
Hi Emma, I am using this: InstallUISequenceShow Dialog=WelcomeDlg After=MigrateFeatureStatesNOT Installed/ShowShow Dialog=ResumeDlg After=WelcomeDlgInstalled AND (RESUME OR Preselected)/ShowShow Dialog=MaintenanceWelcomeDlg After=ResumeDlgInstalled AND NOT RESUME AND NOT Preselected/ShowShow

Re: [WiX-users] Customizing a Maintenance Type Dialog

2012-07-03 Thread Ravi Raj
Hey Eddie, Sorry for the name as I referred the StackOverflow link. On Tue, Jul 3, 2012 at 1:31 PM, Ravi Raj raviraj.callin...@gmail.comwrote: Hi Emma, I am using this: InstallUISequenceShow Dialog=WelcomeDlg After=MigrateFeatureStatesNOT Installed/ShowShow Dialog=ResumeDlg

Re: [WiX-users] Customizing a Maintenance Type Dialog

2012-07-03 Thread eddie burkowich
Hey Ravi Raj, Thanks for the kindness , could you please let me know where exactly i mean in which dialog do i need to put this , as per alexey advice on stackoverflow i modified the source dialogs that means MaintenanceWelcomeDlg MaintenanceTypeDlg have used two statements as DialogRef

Re: [WiX-users] Uninstalling Sql2005 Express as part of a burn install chain.

2012-07-03 Thread Richard Mayes
Completely forgot about in-place upgrades, it's been so long since I've done one! Now I just need to work out how to detect it correctly... Thanks Richard On 2 July 2012 17:03, Neil Sleightholm n...@x2systems.com wrote: Instead of uninstalling why not do an upgrade to the SQL2005 instance.

Re: [WiX-users] Customizing a Maintenance Type Dialog

2012-07-03 Thread eddie burkowich
Hi Ravi Writing what you said exact gives the following errors: C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(38) : error LGHT0094 : Unresolved reference to symbol 'Property:ApplicationFolderName' in section 'Fragment:'.

Re: [WiX-users] Trying to create patch, getting PYRO0227 error.

2012-07-03 Thread David Watson
Hi, You can apply a small update by following this http://msdn.microsoft.com/en-us/library/windows/desktop/aa367575(v=vs.85).asp x. You can see what's changed in your patch by using orca from the windows SDK (http://msdn.microsoft.com/en-us/library/windows/desktop/aa370557(v=vs.85).as px) or a

Re: [WiX-users] Unknown WiX variables in Bundle with WiX 3.6.1908.0

2012-07-03 Thread manishshirsat
hiii Rob, i have been working on bootstrapper application. i am using WiX 3.6.2928.0 i also got the same error about this WixVariable but after declaring them as u said like- WixVariable Id=WixMbaPrereqPackageId Value=Netfx35 / WixVariable Id=WixMbaPrereqLicenseUrl Value=netfx35.eula.1033.rtf /

Re: [WiX-users] How to save return code from a command line CustomAction?

2012-07-03 Thread ferdi.oeztuerk
1) %errorlevel% env var? Never did it as CA, but I would think of batch file, storing the err to file, or another env var, and read this or that file again... if it works tell us how you did it :) 2) ignore ignores the return value :) walk the talk Ferdi http://app-w.com -Original

[WiX-users] Only perUser installation get too much errors ICE38; ICE91; ICE64

2012-07-03 Thread Alexey Ivanov
Part of XML: ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; ?include Variables.wxi? Product Id=* Name=$(var.ProductName) Manufacturer=$(var.Manufacturer) Codepage=$(var.ProductCodepage) Language=1033 Version=$(var.ProductVersion)

Re: [WiX-users] Only perUser installation get too much errors ICE38; ICE91; ICE64

2012-07-03 Thread ferdi.oeztuerk
Try to install to ProgramFilesFolder? it is a redirected property in per user context (see here http://msdn.microsoft.com/en-us/library/windows/desktop/dd765197(v=vs.85).aspx) Perhaps your ICEs are gone then. -Original Message- From: Alexey Ivanov [mailto:alexey.iva...@gmail.com] Sent:

Re: [WiX-users] Only perUser installation get too much errors ICE38; ICE91; ICE64

2012-07-03 Thread ferdi.oeztuerk
http://msdn.microsoft.com/en-us/library/windows/desktop/dd765197(v=vs.85).aspx http://msdn.microsoft.com/en-us/library/windows/desktop/dd408068(v=vs.85).aspx -Original Message- From: Alexey Ivanov [mailto:alexey.iva...@gmail.com] Sent: Dienstag, 3. Juli 2012 17:25 To: General discussion

Re: [WiX-users] Only perUser installation get too much errors ICE38; ICE91; ICE64

2012-07-03 Thread Alexey Ivanov
Redirection, only on MSI 5.0? But anyway, needed to install program into LocalAppDataFolder for everyone (admins and users) 2012/7/3 ferdi.oeztu...@accenture.com Try to install to ProgramFilesFolder? it is a redirected property in per user context (see here

Re: [WiX-users] X64 Burn Bootstrapper

2012-07-03 Thread Nathan Green (APP-V)
My install project has a 64bit cmdlet that must run from our custom Bootstrapper Application as well. Our BA is not managed, but I believe the same concept applies. You can get the install location of the 64bit PowerShell from the registry by ensuring that you open your registry key with