[WiX-users] decompile "burn" exe

Hi, I know it is possible to decompile msi file using dark.exe. Is it possible to decompile exe file created with burn.exe?When I run dark.exe passing the exe file as parameter I get the error below: dark.exe : error DARK0001 : Value cannot be null.Parameter name: path1 Exception Type: System.Arg

Re: [WiX-users] major upgrade from per-client to per-machine install

ext arguments. This would only detect that such products > exist. MsiConfigureProductEx could then be used to remove them but I wouldn't > do this in an installer... maybe as part of a chainer. > > -Original Message- > From: Martin Kulov [mailto:mar...@kulov.net] > Sent:

Re: [WiX-users] major upgrade from per-client to per-machine install

Hi everyone, Is there a way to detect per-user installation and so that per-machine install is prevented unless the per-user one is uninstalled first? Thank you, Martin Kulov > From: mar...@kulov.net > To: wix-users@lists.sourceforge.net > Date: Tue, 11 Oct 2011 21:01:23 + >

Re: [WiX-users] major upgrade from per-client to per-machine install

lient to per-machine install > > Sadly, Windows Installer doesn't support that. > > On Mon, Oct 10, 2011 at 9:23 AM, Martin Kulov wrote: > > > > > Hi, (moving this to a new thread) I have an existing MSI that needs to be > > MajorUpgrade'd from per clie

[WiX-users] major upgrade from per-client to per-machine install

Hi, (moving this to a new thread) I have an existing MSI that needs to be MajorUpgrade'd from per client to per machine installation.Right now installing the latest bits results in two versions of the program being installed side by side.This does not work for at all. How can I remove the exi

Re: [WiX-users] majorupgrade when signing and merge

rom: b...@joyofsetup.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] majorupgrade when signing and merge > > On 06-Oct-11 19:53, Martin Kulov wrote: > > files in ProgramFiles, Windows and ProgramData. Should it install per-user > > or per-machine mode? &g

Re: [WiX-users] majorupgrade when signing and merge

ProgramData. Should it install per-user or per-machine mode? Now my MSI file is working in per-machine mode and it cannot upgrade the existing per-user installations. What is it right way of removing existing installations before installing the new one?Thank you so much! Martin Kulov Microsoft

Re: [WiX-users] majorupgrade when signing and merge

. > > Phil Wilson > > -Original Message- > From: Martin Kulov [mailto:mar...@kulov.net] > Sent: Thursday, October 06, 2011 3:59 AM > To: John Robbins; wix-users > Subject: Re: [WiX-users] majorupgrade when signing and merge > > > So I verified that digitally

Re: [WiX-users] majorupgrade when signing and merge

//wix.sourceforge.net/manual-wix3/major_upgrade.htm shows how to > > integrate a major upgrade into your .WXS file. > > > > John > > Wintellect > > http://www.wintellect.com > > +1-877-968-5528 > > > > > > -Original Message- > >

Re: [WiX-users] majorupgrade when signing and merge

ur .WXS file. > > John > Wintellect > http://www.wintellect.com > +1-877-968-5528 > > > -Original Message- > From: Martin Kulov [mailto:mar...@kulov.net] > Sent: Wednesday, October 05, 2011 2:59 PM > To: wix-users > Subject: [WiX-users] majorupgrade wh

[WiX-users] majorupgrade when signing and merge

Hi, I have an MSI installer built few months ago. It used to work fine during MajorUpgrade. Today I signed the MSI with code certificate and also added one Merge Module. However now my MSI file gets installed as a new product and does not upgrade the existing installation as it used to do.

Re: [WiX-users] Another version of this product is already installed

file I installed the product originally from, it behaves correctly by displaying Repair/Remove options. Thanks for your help, Michael! Martin Kulov -Original Message- From: Michael Stoll [mailto:unwicht...@mistoll.de] Sent: Wednesday, June 22, 2011 9:05 PM To: General discussion for

[WiX-users] Another version of this product is already installed

? Thank you very much, Martin Kulov http://www.kulov.net -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is

Re: [WiX-users] logging

; -dcabName="'&$CABINET_NAME&'.cab" -dcodepage='&$wixInitLcidCode&' -dproductGUID='&$productCode&' -out "'&$BUILD_FOLDER&'\" "'&$BUILD_FOLDER&'\*.wxs" > myfile.txt ',$BUILD

Re: [WiX-users] remember installed features during major upgrade

behavior. You're using the older way, so you need to specify it explicitly. -- John Merryweather Cooper Jack Henry & Associates, Inc. (Premier Tech, Inc.) Build & Install Engineer - jXchange Office: 913-341-3434 x791011 jocoo...@jackhenry.com -Original Message- From: Martin Kulo

Re: [WiX-users] remember installed features during major upgrade

If you use MajorUpgrade, migrate features is the default. -Original Message----- From: Martin Kulov [mailto:mar...@kulov.net] Sent: 10 June 2011 16:25 To: wix-users Subject: [WiX-users] remember installed features during major upgrade Hi, I am sure this is a commonly asked question, but I canno

[WiX-users] remember installed features during major upgrade

at first place and installs all features as specified by default in the MSI. Question: How should one keep user selected features between major upgrades? Thank you! Martin Kulov Microsoft Regional Director VS ALM MVP, MCT, INETA Speaker http://www.kulov.net Phone: (+359) 88 821

Re: [WiX-users] moving component to another feature

feature-component tree then you can only use major upgrades. You won't be able to create a small or minor update. -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: 09 June 2011 15:30 To: wix-users Subject: [WiX-users] moving component to another feature Hi, I hav

[WiX-users] moving component to another feature

Hi, I have one component that I need to move from one feature to another. Should I change the component GUID in order to prevent orphaned files? Thanks, Martin Kulov http

Re: [WiX-users] orphaned desktop shortcut

Blair, Can you please give more guidance/tips here? Thanks! Martin -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: Saturday, May 28, 2011 4:20 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] orphaned desktop shortc

Re: [WiX-users] deferred task with elevated impersonation

, Martin Kulov wrote: > How can I execute deferred task with elevated privileges under user's > running the installer credentials? MSI doesn't support that except by running the entire .msi from an elevated process. -- sig://boB http:

[WiX-users] deferred task with elevated impersonation

is no longer elevated. How can I execute deferred task with elevated privileges under user's running the installer credentials? Thank you, Martin Kulov Microsoft Regional Director VS ALM MVP, MCT, INETA Speaker http://www.kulov.net Phone: (+359) 8

Re: [WiX-users] orphaned desktop shortcut

r' > > Name='$(var.ProductName) Command Prompt' > > WorkingDirectory='MyFolder' > > Icon='MyIcon.ico' > > Target='[%ComSpec]' > > Arguments='[SHELLARGS]'

[WiX-users] orphaned desktop shortcut

. I did not change the component guid as the shortcut is not keypath. Here is excerpt of my code: Can you please help? Thank you! Martin Kulov Microsoft Regional Director

Re: [WiX-users] dependent features

-Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: Tuesday, 10 May 2011 11:14 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] dependent features Michael, Any tips on how to implement compensating action on uninstall? Should

Re: [WiX-users] dependent features

m/en-us/library/ee872121%28v=vs.85%29.aspx#reg_app -Original Message----- From: Martin Kulov [mailto:mar...@kulov.net] Sent: 09 May 2011 22:41 To: wix-users Subject: [WiX-users] dependent features Hi all, I would like to set environment variable PATH based on other features that user has sele

Re: [WiX-users] dependent features

Michael, Any tips on how to implement compensating action on uninstall? Should I preserve the property in xml file or registry? Any other implementation? Martin -Original Message- From: Martin Kulov [mailto:mar...@kulov.net] Sent: Tuesday, May 10, 2011 3:32 AM To: wix-users

Re: [WiX-users] dependent features

e="[PathAdd];Feature1Path" /> > Value="[PathAdd];Feature2Path" /> > > > &Feature1 = > 3 > &Feature2 = > 3 > > > > Add [PathAdd] to registry > > > > Regards > > Michael > > > -Original Mess

[WiX-users] dependent features

Thanks, Martin Kulov http://www.kulov.net -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowe