Re: [WiX-users] Running application after install wizard leaves install wizard unclosable

[Reinier Lamers]

Hi Blair,

The CustomAction tag looks as follows:



Reinier

2010/1/16 Blair :
> Could you please share the attributes of the  element for the
> LaunchLicenseManager action?
>
> -Original Message-
> From: Reinier Lamers [mailto:lam...@textkernel.nl]
> Sent: Friday, January 15, 2010 6:22 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Running application after install wizard leaves install
> wizard unclosable
>
> Hi all,
>
> I tried to apply the "How To: Run the installed application after
> installation" chapter from the WiX manual in a WiX file that also
> contains a modified version of the WixUI_InstallDir dialog that does
> not show an EULA confirmation dialog.
>
> I added this Publish tag just before the  closing tag:
>
>                                 Value="LaunchLicenseManager">
>              WIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and NOT Installed
>            
>
> For some reason, the installation wizard does not exit when it runs
> the application. It does exit when I uncheck the "Launch application"
> checkbox and I press finish.
>
> Must I have made some mistake or is the howto mistaken?
>
> As an extra clue, I see a shell window behind the application window
> when it is run from the installer. Does this mean that the installed
> EXE is a console application? If so, could it help to compile it as a
> GUI application?
>
> --
> Met vriendelijke groet, Kind regards,
> Reinier Lamers
> Textkernel BV

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] DCOM

[Leo Kushnir]

Hi

How is possible to configure DCOM from the installation

Thanks
Leo


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Creating a bootstrap for minor upgrade

[akash bhatia]

Hi,

Can any one just suggest me a way to create a bootstrap for my msi file so
that end user will not face a painfull process of

passing a REINSTALL and REINSTALLMODE  through command line for minor
upgrade.

i found a way of doing it through using c# and dotnet at:
http://pdkm.spaces.live.com/Blog/cns!D1DDEC9FF002FB8C!730.entry

but this will fail and will give an unknown error if dotnet runtime is not
installed at the target machine.

Am new to bootstrapping and any sort of help will be highly appreciated.

-- 
Cheers,
Akash
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Minor Upgrade and original msi file name.

[Giora keinan]

Hello
Thanks for the quick answer.

I have two quick questions:
1. My understanding is that if I want to do minor upgrade after a major 
upgrade I should use the Major upgrade product id instead of  the 
original installation product id.
2. Is there a way to do an ifdef in the wxs file. I want to use the same 
wxs file for both minor and major upgrades with an ifdef inside.

Thanks
Giora



Bob Arnson wrote:
> On 1/17/2010 11:10 AM, Giora keinan wrote:
>   
>> I have a problem in minor update. In minor upgrade the msiexec is
>> looking for the upgrade name, which should be the same as the original
>> msi name.
>> The problem is that sometimes the original setup filename is modified
>> during download. For example setup.msi is modified to setup(1).msi.
>>
>> 
>
> Use major upgrades and/or an .exe bootstrapper to install minor 
> upgrades. http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/
>
>   

-- 
-
Giora Keinan
CapsCake - The natural language launcher.
Because free text is easy.
http://www.capscake.com
-


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] CNDL1033, LGHT1079 - question about long cabinet file names

[Ondrej Zarevucky]

Hi everybody,
I have question about these two warnings thrown by Candle and Light 
tools: CNDL1033 and LGHT1079 - both are about long cabinet file names.

The warning is telling me I should use short (8.3) file names 
referencing some Windows Installer team recommendation, but I couldn't 
find any documentation describing the compatibility problems I can 
encounter. I would prefer using long file names for easier work with the 
cabinet files. ("Program_Help_EN.CAB" is better name then "Prog_HEN.CAB")

Can you please tell me, what compatibility problems could result from 
using long cabinet names? I'm targeting Windows XP with Windows 
Installer 3.1.

Thank you for clarification

Sample warning from Candle:
Media.wxi(15) : warning CNDL1033 : The Media/@Cabinet attribute's value, 
'LongCabinetName.CAB', is not a valid external cabinet name.  Legal 
cabinet names must follow 8.3 format: they should contain no more than 8 
characters followed by an optional extension of no more than 3 
characters.  Any character except for the follow may be used: \ ? | > < 
: / * " + , ; = [ ] (space).  The Windows Installer team has recommended 
following the 8.3 format for external cabinet files and any other naming 
scheme is officially unsupported (which means its not guaranteed to work 
on all platforms).

Have a nice day
zarevak

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Msi hangs on _RemoveFilePath

[SP_]

Hi all,
on some computers my msi hangs for ages. Logs says:

MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: BindImage 
MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: ProgId 
MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: PublishComponent 
MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: SelfReg 
MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: Extension 
MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: Font 
MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: Class 
MSI (s) (3C:A0) [17:13:58:001]: Note: 1: 2205 2:  3: _RemoveFilePath

Installation was craeted by wix, has about 50 000 files and about 3 000
components. Installation Requres msi.dll version 4.5. I validated
installation by orca(it does nat have _RemoveFilePath table), orca reported
the only error:
ICE57   ERROR   Component 'Component0' has both per-user data and a keypath that
can be either per-user or per-machine.
Any ideas?
-- 
View this message in context: 
http://n2.nabble.com/Msi-hangs-on-RemoveFilePath-tp4414568p4414568.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Rollback after Failed Install Causes Uninstall of Unrelated Product

[Castro, Edwin G. (Hillsboro)]

I have a major upgrade that appears to be uninstalling VMWare Tools:

(SERVER) MSI (s) (80:E0) [17:25:51:776]: Executing op: 
ProductInfo(ProductKey={3B410500-1802-488E-9EF1-4B11992E0440},ProductName=VMware
 Tools,PackageName=VMware 
Tools.msi,Language=0,Version=50397186,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,PackageMediaPath=\,PackageCode={DAD8EF9D-4831-48D3-9C0F-5A72B64B400E},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)

I started to look around because my system rebooted (because of another MSI 
installer I wrote) and when it came back up I started to see dialogs telling me 
that MSVCP71.DLL was missing! I looked through my log files and found the file 
that contained:

(SERVER) MSI (s) (80:E0) [17:25:53:270]: Executing op: 
FileRemove(,FileName=C:\Windows\system32\msvcp71.dll,,)
(SERVER) MSI (s) (80:E0) [17:25:53:271]: Note: 1: 1321 2: 
C:\Windows\system32\msvcp71.dll
(SERVER) MSI (s) (80:E0) [17:25:53:271]: Verifying accessibility of file: 
msvcp71.dll

When I searched further up in the file I noticed the ProductInfo line above. My 
installer is failing so I believe the uninstallation of VMWare Tools is 
occurring as a result of Rollback.

(UNKNOWN) === Logging stopped: 1/15/2010 17:25:51 ===
(POLICY) MSI (s) (80:E0) [17:25:51:620]: User policy value 
'DisableRollback' is 0
(POLICY) MSI (s) (80:E0) [17:25:51:620]: Machine policy value 
'DisableRollback' is 0
(SERVER) MSI (s) (80:E0) [17:25:51:620]: Incrementing counter to disable 
shutdown. Counter after increment: 0
(SERVER) MSI (s) (80:E0) [17:25:51:622]: Note: 1: 1402 2: 
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts
 3: 2
(SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op: 
Header(Signature=1397708873,Version=400,Timestamp=983407761,LangId=0,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
(SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op: 
DialogInfo(Type=0,Argument=0)
(SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op: 
DialogInfo(Type=1,Argument=VMware Tools)
(SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op: 
RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back 
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing
 backup files,CleanupTemplate=File: [1])
(SERVER) MSI (s) (80:E0) [17:25:51:775]: Executing op: 
ActionStart(Name=InstallFinalize,,)
(SERVER) MSI (s) (80:E0) [17:25:51:776]: Executing op: 
RegOpenKey(Root=-2147483646,Key=Software\Microsoft\Windows\CurrentVersion\Installer\TempPackages,SecurityDescriptor=BinaryData,BinaryType=0,)
(SERVER) MSI (s) (80:E0) [17:25:51:776]: Executing op: 
ProductInfo(ProductKey={3B410500-1802-488E-9EF1-4B11992E0440},ProductName=VMware
 Tools,PackageName=VMware 
Tools.msi,Language=0,Version=50397186,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,PackageMediaPath=\,PackageCode={DAD8EF9D-4831-48D3-9C0F-5A72B64B400E},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)

I am completely perplexed as to how this is happening. Any ideas at what I 
should look for?

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

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Running application after install wizard leaves install wizard unclosable

[Blair]

With those attributes you told Windows Installer that you care about the
result of running your action, which of course requires that it end, so
Windows Installer waits until the program ends before it exits.

By not setting the Execute attribute you have identified the CustomAction as
"immediate" which is completely appropriate. However, immediate custom
actions always run as the installing user, so the Impersonate attribute has
no effect. You can drop it.

You need to use the Return attribute, and the value you need is asyncNoWait.
So, your CustomAction tag should look like this:



-Blair

-Original Message-
From: Reinier Lamers [mailto:lam...@textkernel.nl] 
Sent: Monday, January 18, 2010 4:53 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Running application after install wizard leaves
install wizard unclosable

Hi Blair,

The CustomAction tag looks as follows:



Reinier

2010/1/16 Blair :
> Could you please share the attributes of the  element for
the
> LaunchLicenseManager action?
>
> -Original Message-
> From: Reinier Lamers [mailto:lam...@textkernel.nl]
> Sent: Friday, January 15, 2010 6:22 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Running application after install wizard leaves
install
> wizard unclosable
>
> Hi all,
>
> I tried to apply the "How To: Run the installed application after
> installation" chapter from the WiX manual in a WiX file that also
> contains a modified version of the WixUI_InstallDir dialog that does
> not show an EULA confirmation dialog.
>
> I added this Publish tag just before the  closing tag:
>
>                                 Value="LaunchLicenseManager">
>              WIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and NOT Installed
>            
>
> For some reason, the installation wizard does not exit when it runs
> the application. It does exit when I uncheck the "Launch application"
> checkbox and I press finish.
>
> Must I have made some mistake or is the howto mistaken?
>
> As an extra clue, I see a shell window behind the application window
> when it is run from the installer. Does this mean that the installed
> EXE is a console application? If so, could it help to compile it as a
> GUI application?
>
> --
> Met vriendelijke groet, Kind regards,
> Reinier Lamers
> Textkernel BV


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference
attendees to learn about information security's most important issues
through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] minor upgrade - how to check installed program version?

[CP YEH]

Hi,

I have created setup msi and it works fine. Then, I created minor
upgrade msi and I would like to check what version of my program is
installed on the machine to see if I should proceed to install.

I added some code as follows.


  
  






  NEWERFOUND
  SELFFOUND


But looking at the logs I found that actions are skipped because I am
running this msi in maintenance mode and thus, FindRelatedProducts
action is skipped.
So I am wondering how I can cause msi to run my custom actions to
check versions.
Please let me know if anyone dealt with this issue before. Thanks.


YEH <><

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Minor Upgrade and original msi file name.

[Blair]

1. Minor upgrades, by definition, use the ProductCode (produ...@id) of the
already installed package. Major upgrades, by definition, use a different
ProductCode. Definitionally, there is no other difference. The rest is
supporting each of the two different upgrade mechanisms.

2. The easiest way is:







-Original Message-
From: Giora keinan [mailto:grkei...@gmail.com] 
Sent: Monday, January 18, 2010 6:15 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Minor Upgrade and original msi file name.

Hello
Thanks for the quick answer.

I have two quick questions:
1. My understanding is that if I want to do minor upgrade after a major 
upgrade I should use the Major upgrade product id instead of  the 
original installation product id.
2. Is there a way to do an ifdef in the wxs file. I want to use the same 
wxs file for both minor and major upgrades with an ifdef inside.

Thanks
Giora



Bob Arnson wrote:
> On 1/17/2010 11:10 AM, Giora keinan wrote:
>   
>> I have a problem in minor update. In minor upgrade the msiexec is
>> looking for the upgrade name, which should be the same as the original
>> msi name.
>> The problem is that sometimes the original setup filename is modified
>> during download. For example setup.msi is modified to setup(1).msi.
>>
>> 
>
> Use major upgrades and/or an .exe bootstrapper to install minor 
> upgrades. http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/
>
>   

-- 
-
Giora Keinan
CapsCake - The natural language launcher.
Because free text is easy.
http://www.capscake.com
-



--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference
attendees to learn about information security's most important issues
through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] minor upgrade - how to check installed program version?

[Blair]

Normally those are checked by your bootstrapper that sets the REINSTALL and
REINSTALLMODE values on the commandline. If your bootstrapper doesn't check
versions you will need to write that yourself.

Question: What use case do you have for using minor upgrades? Is it for
supporting patching?

-Original Message-
From: CP YEH [mailto:ntde...@gmail.com] 
Sent: Monday, January 18, 2010 11:08 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] minor upgrade - how to check installed program version?

Hi,

I have created setup msi and it works fine. Then, I created minor
upgrade msi and I would like to check what version of my program is
installed on the machine to see if I should proceed to install.

I added some code as follows.


  
  






  NEWERFOUND
  SELFFOUND


But looking at the logs I found that actions are skipped because I am
running this msi in maintenance mode and thus, FindRelatedProducts
action is skipped.
So I am wondering how I can cause msi to run my custom actions to
check versions.
Please let me know if anyone dealt with this issue before. Thanks.


YEH <><


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference
attendees to learn about information security's most important issues
through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] minor upgrade - how to check installed program version?

[CP YEH]

Thank you very much for your reply.
My msi is pretty small in that it contains only few executable
files(exe/dll). Every now and then there are changes to these files so
I need to provide updates so that the user can download the upgrade
packages to upgrade their application. It's also possible that I might
have to add more files in the future.
I don't know which upgrades is the best option but I felt that minor
upgrade sounds most reasonable to me but if you have any other
suggestions.
Thank you.

YEH <><

On Mon, Jan 18, 2010 at 2:38 PM, Blair  wrote:
> Normally those are checked by your bootstrapper that sets the REINSTALL and
> REINSTALLMODE values on the commandline. If your bootstrapper doesn't check
> versions you will need to write that yourself.
>
> Question: What use case do you have for using minor upgrades? Is it for
> supporting patching?
>
> -Original Message-
> From: CP YEH [mailto:ntde...@gmail.com]
> Sent: Monday, January 18, 2010 11:08 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] minor upgrade - how to check installed program version?
>
> Hi,
>
> I have created setup msi and it works fine. Then, I created minor
> upgrade msi and I would like to check what version of my program is
> installed on the machine to see if I should proceed to install.
>
> I added some code as follows.
>
>    
>                            Minimum="1.0.1" IncludeMinimum="yes"
>                      Maximum="1.0.1" IncludeMaximum="yes" />
>              Minimum='1.0.2' IncludeMinimum='no' />
>    
>
>    
>    
>
>    
>       After="FindRelatedProducts">NEWERFOUND
>       After="FindRelatedProducts">SELFFOUND
>    
>
> But looking at the logs I found that actions are skipped because I am
> running this msi in maintenance mode and thus, FindRelatedProducts
> action is skipped.
> So I am wondering how I can cause msi to run my custom actions to
> check versions.
> Please let me know if anyone dealt with this issue before. Thanks.
>
>
> YEH <><
>
> 
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for Conference
> attendees to learn about information security's most important issues through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Administrative Setup UI

[Tony]

During an Administrative installation, we'd like to ask the installing
user to specify an installation directory.  We are having difficulties
adding a dialog to the adminuisequence.  When we add a dialog to the
sequence, we execute an action called, SetTargetPath, but the end
result is the install always occurs entirely in the c:\ folder.  Any
ideas?

Once the admin execute sequence begins we don't see any type of
progress dialog, just the last UI dialog with the install button
depressed.  Do we have to do something different with the
administrative install to make this happen?
-- 
Tony

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] minor upgrade - how to check installed program version?

[Blair]

Search Bob Arnson's blog "Joy of Setup" http://www.joyofsetup.com/ for
"major upgrade".

Despite the name of the term, it is usually for most project the right kind
of upgrade, especially if they don't plan on using MSP files.

-Original Message-
From: CP YEH [mailto:ntde...@gmail.com] 
Sent: Monday, January 18, 2010 11:55 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] minor upgrade - how to check installed program
version?

Thank you very much for your reply.
My msi is pretty small in that it contains only few executable
files(exe/dll). Every now and then there are changes to these files so
I need to provide updates so that the user can download the upgrade
packages to upgrade their application. It's also possible that I might
have to add more files in the future.
I don't know which upgrades is the best option but I felt that minor
upgrade sounds most reasonable to me but if you have any other
suggestions.
Thank you.

YEH <><

On Mon, Jan 18, 2010 at 2:38 PM, Blair  wrote:
> Normally those are checked by your bootstrapper that sets the REINSTALL
and
> REINSTALLMODE values on the commandline. If your bootstrapper doesn't
check
> versions you will need to write that yourself.
>
> Question: What use case do you have for using minor upgrades? Is it for
> supporting patching?
>
> -Original Message-
> From: CP YEH [mailto:ntde...@gmail.com]
> Sent: Monday, January 18, 2010 11:08 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] minor upgrade - how to check installed program
version?
>
> Hi,
>
> I have created setup msi and it works fine. Then, I created minor
> upgrade msi and I would like to check what version of my program is
> installed on the machine to see if I should proceed to install.
>
> I added some code as follows.
>
>    
>                            Minimum="1.0.1" IncludeMinimum="yes"
>                      Maximum="1.0.1" IncludeMaximum="yes" />
>              Minimum='1.0.2' IncludeMinimum='no' />
>    
>
>    
>    
>
>    
>       After="FindRelatedProducts">NEWERFOUND
>       After="FindRelatedProducts">SELFFOUND
>    
>
> But looking at the logs I found that actions are skipped because I am
> running this msi in maintenance mode and thus, FindRelatedProducts
> action is skipped.
> So I am wondering how I can cause msi to run my custom actions to
> check versions.
> Please let me know if anyone dealt with this issue before. Thanks.
>
>
> YEH <><
>
>

> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established
companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>

--
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
Conference
> attendees to learn about information security's most important issues
through
> interactions with peers, luminaries and emerging and established
companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference
attendees to learn about information security's most important issues
through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Rollback after Failed Install Causes Uninstall ofUnrelated Product

[Schrieken, Rene]

The msvcp71.dll is in my registry as shared dll and looks like it is 
refcounted. Magic happens when your uninstall decreases the counter to 0 based 
on your rollback. (i do assume your are installing msvcp71.dll). Somehow msi 
feels it needs the original installer to properly uninstall it?  Not a clue how 
that gets figured out ... If you can reproduce you can see if setting the 
refcount higher helps? Just to prove that I'm wrong.



Van: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Verzonden: ma 18-1-2010 18:52
Aan: General discussion for Windows Installer XML toolset.
Onderwerp: [WiX-users] Rollback after Failed Install Causes Uninstall 
ofUnrelated Product



I have a major upgrade that appears to be uninstalling VMWare Tools:

(SERVER) MSI (s) (80:E0) [17:25:51:776]: Executing op: 
ProductInfo(ProductKey={3B410500-1802-488E-9EF1-4B11992E0440},ProductName=VMware
 Tools,PackageName=VMware 
Tools.msi,Language=0,Version=50397186,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,PackageMediaPath=\,PackageCode={DAD8EF9D-4831-48D3-9C0F-5A72B64B400E},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)

I started to look around because my system rebooted (because of another MSI 
installer I wrote) and when it came back up I started to see dialogs telling me 
that MSVCP71.DLL was missing! I looked through my log files and found the file 
that contained:

(SERVER) MSI (s) (80:E0) [17:25:53:270]: Executing op: 
FileRemove(,FileName=C:\Windows\system32\msvcp71.dll,,)
(SERVER) MSI (s) (80:E0) [17:25:53:271]: Note: 1: 1321 2: 
C:\Windows\system32\msvcp71.dll
(SERVER) MSI (s) (80:E0) [17:25:53:271]: Verifying accessibility of file: 
msvcp71.dll

When I searched further up in the file I noticed the ProductInfo line above. My 
installer is failing so I believe the uninstallation of VMWare Tools is 
occurring as a result of Rollback.

(UNKNOWN) === Logging stopped: 1/15/2010 17:25:51 ===
(POLICY) MSI (s) (80:E0) [17:25:51:620]: User policy value 
'DisableRollback' is 0
(POLICY) MSI (s) (80:E0) [17:25:51:620]: Machine policy value 
'DisableRollback' is 0
(SERVER) MSI (s) (80:E0) [17:25:51:620]: Incrementing counter to disable 
shutdown. Counter after increment: 0
(SERVER) MSI (s) (80:E0) [17:25:51:622]: Note: 1: 1402 2: 
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts
 3: 2
(SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op: 
Header(Signature=1397708873,Version=400,Timestamp=983407761,LangId=0,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
(SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op: 
DialogInfo(Type=0,Argument=0)
(SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op: 
DialogInfo(Type=1,Argument=VMware Tools)
(SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op: 
RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back 
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing
 backup files,CleanupTemplate=File: [1])
(SERVER) MSI (s) (80:E0) [17:25:51:775]: Executing op: 
ActionStart(Name=InstallFinalize,,)
(SERVER) MSI (s) (80:E0) [17:25:51:776]: Executing op: 
RegOpenKey(Root=-2147483646,Key=Software\Microsoft\Windows\CurrentVersion\Installer\TempPackages,SecurityDescriptor=BinaryData,BinaryType=0,)
(SERVER) MSI (s) (80:E0) [17:25:51:776]: Executing op: 
ProductInfo(ProductKey={3B410500-1802-488E-9EF1-4B11992E0440},ProductName=VMware
 Tools,PackageName=VMware 
Tools.msi,Language=0,Version=50397186,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,PackageMediaPath=\,PackageCode={DAD8EF9D-4831-48D3-9C0F-5A72B64B400E},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)

I am completely perplexed as to how this is happening. Any ideas at what I 
should look for?

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

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users





Please help Logica to respect the environment by not printing this email  / 
Pour contribuer comme Logica au respect de l'environnement, merci de ne pas 
imprimer ce mail /  Bitte drucken Sie diese Nachricht nicht aus und helfen Sie 
so Logica dabei, die Umwelt zu sch

Re: [WiX-users] minor upgrade - how to check installed program version?

[CP YEH]

Thank you for your reply. I saw that web pages earlier and perhaps I
did not look at it closely enough but there are two things that led me
to think that I should use minor upgrades.

One, I check user credential during installation so I don't think the
user wants to enter their credential again during upgrade.
Two, I have certain files that I don't want to lose during upgrades
because I keep user configuration data there.

Of course, I am not really willing to create another bootstrapper just
because I need to check previous versions and I need to pass certain
command line arguments.

Please kindly let me know if I can avoid the above two points. If so,
I will look for options to implement major upgrades instead. Thank you
very much.

YEH <><

On Mon, Jan 18, 2010 at 3:31 PM, Blair  wrote:
> Search Bob Arnson's blog "Joy of Setup" http://www.joyofsetup.com/ for
> "major upgrade".
>
> Despite the name of the term, it is usually for most project the right kind
> of upgrade, especially if they don't plan on using MSP files.
>
> -Original Message-
> From: CP YEH [mailto:ntde...@gmail.com]
> Sent: Monday, January 18, 2010 11:55 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] minor upgrade - how to check installed program
> version?
>
> Thank you very much for your reply.
> My msi is pretty small in that it contains only few executable
> files(exe/dll). Every now and then there are changes to these files so
> I need to provide updates so that the user can download the upgrade
> packages to upgrade their application. It's also possible that I might
> have to add more files in the future.
> I don't know which upgrades is the best option but I felt that minor
> upgrade sounds most reasonable to me but if you have any other
> suggestions.
> Thank you.
>
> YEH <><
>
> On Mon, Jan 18, 2010 at 2:38 PM, Blair  wrote:
>> Normally those are checked by your bootstrapper that sets the REINSTALL
> and
>> REINSTALLMODE values on the commandline. If your bootstrapper doesn't
> check
>> versions you will need to write that yourself.
>>
>> Question: What use case do you have for using minor upgrades? Is it for
>> supporting patching?
>>
>> -Original Message-
>> From: CP YEH [mailto:ntde...@gmail.com]
>> Sent: Monday, January 18, 2010 11:08 AM
>> To: wix-users@lists.sourceforge.net
>> Subject: [WiX-users] minor upgrade - how to check installed program
> version?
>>
>> Hi,
>>
>> I have created setup msi and it works fine. Then, I created minor
>> upgrade msi and I would like to check what version of my program is
>> installed on the machine to see if I should proceed to install.
>>
>> I added some code as follows.
>>
>>    
>>      >                      Minimum="1.0.1" IncludeMinimum="yes"
>>                      Maximum="1.0.1" IncludeMaximum="yes" />
>>      >        Minimum='1.0.2' IncludeMinimum='no' />
>>    
>>
>>    
>>    
>>
>>    
>>      > After="FindRelatedProducts">NEWERFOUND
>>      > After="FindRelatedProducts">SELFFOUND
>>    
>>
>> But looking at the logs I found that actions are skipped because I am
>> running this msi in maintenance mode and thus, FindRelatedProducts
>> action is skipped.
>> So I am wondering how I can cause msi to run my custom actions to
>> check versions.
>> Please let me know if anyone dealt with this issue before. Thanks.
>>
>>
>> YEH <><
>>
>>
> 
>> --
>> Throughout its 18-year history, RSA Conference consistently attracts the
>> world's best and brightest in the field, creating opportunities for
>> Conference
>> attendees to learn about information security's most important issues
>> through
>> interactions with peers, luminaries and emerging and established
> companies.
>> http://p.sf.net/sfu/rsaconf-dev2dev
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>>
>>
> 
> --
>> Throughout its 18-year history, RSA Conference consistently attracts the
>> world's best and brightest in the field, creating opportunities for
> Conference
>> attendees to learn about information security's most important issues
> through
>> interactions with peers, luminaries and emerging and established
> companies.
>> http://p.sf.net/sfu/rsaconf-dev2dev
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>
> 
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and e

Re: [WiX-users] Rollback after Failed Install Causes Uninstall ofUnrelated Product

[Castro, Edwin G. (Hillsboro)]

The most bizarre aspect of all this is that I'm *not* installing MSVCP71.DLL. 
It actually uninstalls the entire VMWare Tools product. My gut says that 
perhaps the UpgradeCode and/or ProductCode are the same (as unlikely as that 
might be).

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: Schrieken, Rene [mailto:rene.schrie...@logica.com]
> Sent: Monday, January 18, 2010 12:34 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Rollback after Failed Install Causes Uninstall
> ofUnrelated Product
> 
> The msvcp71.dll is in my registry as shared dll and looks like it is
> refcounted. Magic happens when your uninstall decreases the counter to
> 0 based on your rollback. (i do assume your are installing
> msvcp71.dll). Somehow msi feels it needs the original installer to
> properly uninstall it?  Not a clue how that gets figured out ... If you
> can reproduce you can see if setting the refcount higher helps? Just to
> prove that I'm wrong.
> 
> 
> 
> Van: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
> Verzonden: ma 18-1-2010 18:52
> Aan: General discussion for Windows Installer XML toolset.
> Onderwerp: [WiX-users] Rollback after Failed Install Causes Uninstall
> ofUnrelated Product
> 
> 
> 
> I have a major upgrade that appears to be uninstalling VMWare Tools:
> 
> (SERVER) MSI (s) (80:E0) [17:25:51:776]: Executing op:
> ProductInfo(ProductKey={3B410500-1802-488E-9EF1-
> 4B11992E0440},ProductName=VMware Tools,PackageName=VMware
> Tools.msi,Language=0,Version=50397186,Assignment=1,ObsoleteArg=0,Produc
> tIcon=ARPPRODUCTICON.exe,PackageMediaPath=\,PackageCode={DAD8EF9D-4831-
> 48D3-9C0F-
> 5A72B64B400E},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,Product
> DeploymentFlags=3)
> 
> I started to look around because my system rebooted (because of another
> MSI installer I wrote) and when it came back up I started to see
> dialogs telling me that MSVCP71.DLL was missing! I looked through my
> log files and found the file that contained:
> 
> (SERVER) MSI (s) (80:E0) [17:25:53:270]: Executing op:
> FileRemove(,FileName=C:\Windows\system32\msvcp71.dll,,)
> (SERVER) MSI (s) (80:E0) [17:25:53:271]: Note: 1: 1321 2:
> C:\Windows\system32\msvcp71.dll
> (SERVER) MSI (s) (80:E0) [17:25:53:271]: Verifying accessibility of
> file: msvcp71.dll
> 
> When I searched further up in the file I noticed the ProductInfo line
> above. My installer is failing so I believe the uninstallation of
> VMWare Tools is occurring as a result of Rollback.
> 
> (UNKNOWN) === Logging stopped: 1/15/2010 17:25:51 ===
> (POLICY) MSI (s) (80:E0) [17:25:51:620]: User policy value
> 'DisableRollback' is 0
> (POLICY) MSI (s) (80:E0) [17:25:51:620]: Machine policy value
> 'DisableRollback' is 0
> (SERVER) MSI (s) (80:E0) [17:25:51:620]: Incrementing counter to
> disable shutdown. Counter after increment: 0
> (SERVER) MSI (s) (80:E0) [17:25:51:622]: Note: 1: 1402 2:
> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\
> Rollback\Scripts 3: 2
> (SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op:
> Header(Signature=1397708873,Version=400,Timestamp=983407761,LangId=0,Pl
> atform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,Script
> Attributes=1)
> (SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op:
> DialogInfo(Type=0,Argument=0)
> (SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op:
> DialogInfo(Type=1,Argument=VMware Tools)
> (SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op:
> RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back
> action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescr
> iption=Removing backup files,CleanupTemplate=File: [1])
> (SERVER) MSI (s) (80:E0) [17:25:51:775]: Executing op:
> ActionStart(Name=InstallFinalize,,)
> (SERVER) MSI (s) (80:E0) [17:25:51:776]: Executing op:
> RegOpenKey(Root=-
> 2147483646,Key=Software\Microsoft\Windows\CurrentVersion\Installer\Temp
> Packages,SecurityDescriptor=BinaryData,BinaryType=0,)
> (SERVER) MSI (s) (80:E0) [17:25:51:776]: Executing op:
> ProductInfo(ProductKey={3B410500-1802-488E-9EF1-
> 4B11992E0440},ProductName=VMware Tools,PackageName=VMware
> Tools.msi,Language=0,Version=50397186,Assignment=1,ObsoleteArg=0,Produc
> tIcon=ARPPRODUCTICON.exe,PackageMediaPath=\,PackageCode={DAD8EF9D-4831-
> 48D3-9C0F-
> 5A72B64B400E},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,Product
> DeploymentFlags=3)
> 
> I am completely perplexed as to how this is happening. Any ideas at
> what I should look for?
> 
> Edwin G. Castro
> Software Developer - Staff
> Electronic Banking Services
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> P Please consider th

Re: [WiX-users] Minor Upgrade and original msi file name.

[Giora keinan]

Thanks Blair
Just to be sure that I understood. If my major upgrade removes the 
existing  files. I should use the major upgrade product id in the next 
minor upgrade.

In my major upgrade I see a behavior I don't  understand.
If the RemoveExistingFiles is schedule before the installation, part of 
the registry keys are removed  (they have a NeverOverwite=yes in the 
upgrade).
If the RemoveExistingFiles is schedule after InstallFinaize the registry 
keys are left  with there values before the installation, but I have a 
problem that a readme.pdf file that I am launching in the original 
installation is launched at the end of the upgrade. There is no launch 
command in the upgrade. Can I prevent the launch of this file ?

Thanks
Giora
.


Blair wrote:
> 1. Minor upgrades, by definition, use the ProductCode (produ...@id) of the
> already installed package. Major upgrades, by definition, use a different
> ProductCode. Definitionally, there is no other difference. The rest is
> supporting each of the two different upgrade mechanisms.
>
> 2. The easiest way is:
>
> 
> 
> 
>
> 
>
> -Original Message-
> From: Giora keinan [mailto:grkei...@gmail.com] 
> Sent: Monday, January 18, 2010 6:15 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Minor Upgrade and original msi file name.
>
> Hello
> Thanks for the quick answer.
>
> I have two quick questions:
> 1. My understanding is that if I want to do minor upgrade after a major 
> upgrade I should use the Major upgrade product id instead of  the 
> original installation product id.
> 2. Is there a way to do an ifdef in the wxs file. I want to use the same 
> wxs file for both minor and major upgrades with an ifdef inside.
>
> Thanks
> Giora
>
>
>
> Bob Arnson wrote:
>   
>> On 1/17/2010 11:10 AM, Giora keinan wrote:
>>   
>> 
>>> I have a problem in minor update. In minor upgrade the msiexec is
>>> looking for the upgrade name, which should be the same as the original
>>> msi name.
>>> The problem is that sometimes the original setup filename is modified
>>> during download. For example setup.msi is modified to setup(1).msi.
>>>
>>> 
>>>   
>> Use major upgrades and/or an .exe bootstrapper to install minor 
>> upgrades. http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/
>>
>>   
>> 
>
>   

-- 
-
Giora Keinan
CapsCake - The natural language launcher.
Because free text is easy.
http://www.capscake.com
-


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] minor upgrade - how to check installed program version?

[Blair]

Whatever techniques you use to prevent requiring reentry of credentials and
for preventing user-modified files from being replaced will likely apply to
major upgrades as well as minor upgrades, except that you may need to modify
your dialog sequence and/or conditions if they are based on either the
REINSTALL or the Installed properties.

-Original Message-
From: CP YEH [mailto:ntde...@gmail.com] 
Sent: Monday, January 18, 2010 12:46 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] minor upgrade - how to check installed program
version?

Thank you for your reply. I saw that web pages earlier and perhaps I
did not look at it closely enough but there are two things that led me
to think that I should use minor upgrades.

One, I check user credential during installation so I don't think the
user wants to enter their credential again during upgrade.
Two, I have certain files that I don't want to lose during upgrades
because I keep user configuration data there.

Of course, I am not really willing to create another bootstrapper just
because I need to check previous versions and I need to pass certain
command line arguments.

Please kindly let me know if I can avoid the above two points. If so,
I will look for options to implement major upgrades instead. Thank you
very much.

YEH <><

On Mon, Jan 18, 2010 at 3:31 PM, Blair  wrote:
> Search Bob Arnson's blog "Joy of Setup" http://www.joyofsetup.com/ for
> "major upgrade".
>
> Despite the name of the term, it is usually for most project the right
kind
> of upgrade, especially if they don't plan on using MSP files.
>
> -Original Message-
> From: CP YEH [mailto:ntde...@gmail.com]
> Sent: Monday, January 18, 2010 11:55 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] minor upgrade - how to check installed program
> version?
>
> Thank you very much for your reply.
> My msi is pretty small in that it contains only few executable
> files(exe/dll). Every now and then there are changes to these files so
> I need to provide updates so that the user can download the upgrade
> packages to upgrade their application. It's also possible that I might
> have to add more files in the future.
> I don't know which upgrades is the best option but I felt that minor
> upgrade sounds most reasonable to me but if you have any other
> suggestions.
> Thank you.
>
> YEH <><
>
> On Mon, Jan 18, 2010 at 2:38 PM, Blair  wrote:
>> Normally those are checked by your bootstrapper that sets the REINSTALL
> and
>> REINSTALLMODE values on the commandline. If your bootstrapper doesn't
> check
>> versions you will need to write that yourself.
>>
>> Question: What use case do you have for using minor upgrades? Is it for
>> supporting patching?
>>
>> -Original Message-
>> From: CP YEH [mailto:ntde...@gmail.com]
>> Sent: Monday, January 18, 2010 11:08 AM
>> To: wix-users@lists.sourceforge.net
>> Subject: [WiX-users] minor upgrade - how to check installed program
> version?
>>
>> Hi,
>>
>> I have created setup msi and it works fine. Then, I created minor
>> upgrade msi and I would like to check what version of my program is
>> installed on the machine to see if I should proceed to install.
>>
>> I added some code as follows.
>>
>>    
>>      >                      Minimum="1.0.1" IncludeMinimum="yes"
>>                      Maximum="1.0.1" IncludeMaximum="yes" />
>>      >        Minimum='1.0.2' IncludeMinimum='no' />
>>    
>>
>>    
>>    
>>
>>    
>>      > After="FindRelatedProducts">NEWERFOUND
>>      > After="FindRelatedProducts">SELFFOUND
>>    
>>
>> But looking at the logs I found that actions are skipped because I am
>> running this msi in maintenance mode and thus, FindRelatedProducts
>> action is skipped.
>> So I am wondering how I can cause msi to run my custom actions to
>> check versions.
>> Please let me know if anyone dealt with this issue before. Thanks.
>>
>>
>> YEH <><
>>
>>
>

>> --
>> Throughout its 18-year history, RSA Conference consistently attracts the
>> world's best and brightest in the field, creating opportunities for
>> Conference
>> attendees to learn about information security's most important issues
>> through
>> interactions with peers, luminaries and emerging and established
> companies.
>> http://p.sf.net/sfu/rsaconf-dev2dev
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>>
>>
>

> --
>> Throughout its 18-year history, RSA Conference consistently attracts the
>> world's best and brightest in the field, creating opportunities for
> Conference
>> attendees to learn about information security's most important issues
> through
>> interactions with peers, luminaries and emerging and established
> comp

Re: [WiX-users] Minor Upgrade and original msi file name.

[Blair]

I assume you are referring to RemoveExistingProducts, not
RemoveExistingFiles (I've never heard of that action).

Scheduling RemoveExistingProducts before the installation causes the
previous installation being replaced to be first removed, removing
references to your (old) components causing them to be erased from the file
system/registry/etc. before your newer versions of those references are
written. Thus, NeverOverwrite doesn't apply.

In your Upgrade table you have a row where you identify a property with the
product(s) that you will remove. For purposes of illustration I will assume
that property is named OLDPRODUCT (it will be named whatever rows you didn't
tag with OnlyDetect="yes"). You would then add " AND NOT OLDPRODUCT" to your
"NOT Installed" condition (so it will look like "NOT Installed AND NOT
OLDPRODUCT") for launching your readme pdf file. Be sure to replace
OLDPRODUCT with your actual property's name to use my fix.

-Original Message-
From: Giora keinan [mailto:grkei...@gmail.com] 
Sent: Monday, January 18, 2010 1:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Minor Upgrade and original msi file name.

Thanks Blair
Just to be sure that I understood. If my major upgrade removes the 
existing  files. I should use the major upgrade product id in the next 
minor upgrade.

In my major upgrade I see a behavior I don't  understand.
If the RemoveExistingFiles is schedule before the installation, part of 
the registry keys are removed  (they have a NeverOverwite=yes in the 
upgrade).
If the RemoveExistingFiles is schedule after InstallFinaize the registry 
keys are left  with there values before the installation, but I have a 
problem that a readme.pdf file that I am launching in the original 
installation is launched at the end of the upgrade. There is no launch 
command in the upgrade. Can I prevent the launch of this file ?

Thanks
Giora
.


Blair wrote:
> 1. Minor upgrades, by definition, use the ProductCode (produ...@id) of the
> already installed package. Major upgrades, by definition, use a different
> ProductCode. Definitionally, there is no other difference. The rest is
> supporting each of the two different upgrade mechanisms.
>
> 2. The easiest way is:
>
> 
> 
> 
>
> 
>
> -Original Message-
> From: Giora keinan [mailto:grkei...@gmail.com] 
> Sent: Monday, January 18, 2010 6:15 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Minor Upgrade and original msi file name.
>
> Hello
> Thanks for the quick answer.
>
> I have two quick questions:
> 1. My understanding is that if I want to do minor upgrade after a major 
> upgrade I should use the Major upgrade product id instead of  the 
> original installation product id.
> 2. Is there a way to do an ifdef in the wxs file. I want to use the same 
> wxs file for both minor and major upgrades with an ifdef inside.
>
> Thanks
> Giora
>
>
>
> Bob Arnson wrote:
>   
>> On 1/17/2010 11:10 AM, Giora keinan wrote:
>>   
>> 
>>> I have a problem in minor update. In minor upgrade the msiexec is
>>> looking for the upgrade name, which should be the same as the original
>>> msi name.
>>> The problem is that sometimes the original setup filename is modified
>>> during download. For example setup.msi is modified to setup(1).msi.
>>>
>>> 
>>>   
>> Use major upgrades and/or an .exe bootstrapper to install minor 
>> upgrades. http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/
>>
>>   
>> 
>
>   

-- 
-
Giora Keinan
CapsCake - The natural language launcher.
Because free text is easy.
http://www.capscake.com
-



--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference
attendees to learn about information security's most important issues
through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Rollback after Failed Install Causes Uninstall ofUnrelated Product

[Castro, Edwin G. (Hillsboro)]

Looks like UpgradeCode, ProductCode, PackageCode are all different between the 
three products involved. Could a component guid be at fault here? My product 
and VMware Tools do not share any components so I wouldn't expect them to have 
any matching guids. Is it possible for something odd like this to happen if my 
product and VMware Tools both had a component with the same guid but different 
resources?

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: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
> Sent: Monday, January 18, 2010 12:49 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Rollback after Failed Install Causes Uninstall
> ofUnrelated Product
> 
> The most bizarre aspect of all this is that I'm *not* installing
> MSVCP71.DLL. It actually uninstalls the entire VMWare Tools product. My
> gut says that perhaps the UpgradeCode and/or ProductCode are the same
> (as unlikely as that might be).
> 
> 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: Schrieken, Rene [mailto:rene.schrie...@logica.com]
> > Sent: Monday, January 18, 2010 12:34 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Rollback after Failed Install Causes
> Uninstall
> > ofUnrelated Product
> >
> > The msvcp71.dll is in my registry as shared dll and looks like it is
> > refcounted. Magic happens when your uninstall decreases the counter
> to
> > 0 based on your rollback. (i do assume your are installing
> > msvcp71.dll). Somehow msi feels it needs the original installer to
> > properly uninstall it?  Not a clue how that gets figured out ... If
> you
> > can reproduce you can see if setting the refcount higher helps? Just
> to
> > prove that I'm wrong.
> >
> > 
> >
> > Van: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
> > Verzonden: ma 18-1-2010 18:52
> > Aan: General discussion for Windows Installer XML toolset.
> > Onderwerp: [WiX-users] Rollback after Failed Install Causes Uninstall
> > ofUnrelated Product
> >
> >
> >
> > I have a major upgrade that appears to be uninstalling VMWare Tools:
> >
> > (SERVER) MSI (s) (80:E0) [17:25:51:776]: Executing op:
> > ProductInfo(ProductKey={3B410500-1802-488E-9EF1-
> > 4B11992E0440},ProductName=VMware Tools,PackageName=VMware
> >
> Tools.msi,Language=0,Version=50397186,Assignment=1,ObsoleteArg=0,Produc
> > tIcon=ARPPRODUCTICON.exe,PackageMediaPath=\,PackageCode={DAD8EF9D-
> 4831-
> > 48D3-9C0F-
> >
> 5A72B64B400E},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,Product
> > DeploymentFlags=3)
> >
> > I started to look around because my system rebooted (because of
> another
> > MSI installer I wrote) and when it came back up I started to see
> > dialogs telling me that MSVCP71.DLL was missing! I looked through my
> > log files and found the file that contained:
> >
> > (SERVER) MSI (s) (80:E0) [17:25:53:270]: Executing op:
> > FileRemove(,FileName=C:\Windows\system32\msvcp71.dll,,)
> > (SERVER) MSI (s) (80:E0) [17:25:53:271]: Note: 1: 1321 2:
> > C:\Windows\system32\msvcp71.dll
> > (SERVER) MSI (s) (80:E0) [17:25:53:271]: Verifying accessibility
> of
> > file: msvcp71.dll
> >
> > When I searched further up in the file I noticed the ProductInfo line
> > above. My installer is failing so I believe the uninstallation of
> > VMWare Tools is occurring as a result of Rollback.
> >
> > (UNKNOWN) === Logging stopped: 1/15/2010 17:25:51 ===
> > (POLICY) MSI (s) (80:E0) [17:25:51:620]: User policy value
> > 'DisableRollback' is 0
> > (POLICY) MSI (s) (80:E0) [17:25:51:620]: Machine policy value
> > 'DisableRollback' is 0
> > (SERVER) MSI (s) (80:E0) [17:25:51:620]: Incrementing counter to
> > disable shutdown. Counter after increment: 0
> > (SERVER) MSI (s) (80:E0) [17:25:51:622]: Note: 1: 1402 2:
> >
> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\
> > Rollback\Scripts 3: 2
> > (SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op:
> >
> Header(Signature=1397708873,Version=400,Timestamp=983407761,LangId=0,Pl
> >
> atform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,Script
> > Attributes=1)
> > (SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op:
> > DialogInfo(Type=0,Argument=0)
> > (SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op:
> > DialogInfo(Type=1,Argument=VMware Tools)
> > (SERVER) MSI (s) (80:E0) [17:25:51:774]: Executing op:
> > RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling
> back
> >
> action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupD

[WiX-users] how to create a DisplayResourceDll for ShortCut element

[Lian Jiang]

Hi,

Could anybody provide a sample/reference about how to author a resource DLL
used by ShortCut element? I don't quitely understand this descript from WIX
document:

"The Formatted string providing the full path to the language neutral file
containing the MUI Manifest. Generally authored using [#filekey] form."

Thanks
Leon
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Add Managed Handler

[Pierson Lee (PIE)]

In IIS 7.0 there is a new option of "Add Managed Handler" under "Handler 
Mappings" which allows me to add a MIME Type handler (dll) to point to a MIME 
extension.

Is there such an option within WiX that allows me to do this using the IIS 
extensions with the 3.0 RTM version?
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] how to create a DisplayResourceDll for ShortCut element

[Blair]

Sample code. Take it for what it is worth. This assumes three things:
1. The resources are "declared" in Product.exe and are localized into two
cultures: en-US and es-ES using the MUI Win32 resource localization scheme
released to the world with Vista. The actual Spanish string will actually be
found in the Product.exe.mui file in the es-ES directory and the English
string will be found in the Product.exe.mui file in the en-US directory.
2. The desired "name" for the shortcut is the string #102 in Product.exe.
3. The relative placement of the shortcut and its target (even when
considered relative to the component list) don't matter for the purposes of
this example, but I had to put them somewhere. This is NOT a guide to where
to place shortcuts relative to their targets nor is it a guide to use
non-advertised (or even advertised) shortcuts. That doesn't matter for the
purposes of this example either.

...

  


  
  

  

...













-Original Message-
From: Lian Jiang [mailto:jiangok2...@gmail.com] 
Sent: Monday, January 18, 2010 5:04 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] how to create a DisplayResourceDll for ShortCut element

Hi,

Could anybody provide a sample/reference about how to author a resource DLL
used by ShortCut element? I don't quitely understand this descript from WIX
document:

"The Formatted string providing the full path to the language neutral file
containing the MUI Manifest. Generally authored using [#filekey] form."

Thanks
Leon

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference
attendees to learn about information security's most important issues
through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] How to assign a default value to preprocessor properties

[Joe Osman]

I am using preprocessor properties in my WIX project and I assign them 
values in msbuild when building the WIX project from the command line .
For example I have the following preprocessor properties: 
Var1=$(Var1);Var2=$(Var2)
I assign them values in msbuild in this way: msbuild 
/p:Var1="value1";Var2="value2"


The problem is that when I build the project in Visual Studio those 
properties get an empty value. I want to give these properties a default 
value so that I will be able to build the WIX project from Visual Studio 
and not just from the command line using msbuild.


Is there any way to assign these properties a default value that can be 
overridden by msbuild ?


Thanks for your help !

===
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
===

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] WIX v2.0 and IIS 7 -- Any stopgap solutions?

[Navid Azimi-Garakani]

Hello--

I have a large number of MSIs (think 75+) that are currently deploying to IIS 6 
on Windows Server 2003 (32-bit). These MSIs are being built with WIX 
2.0.3719.0. I need to get these MSIs to deploy to IIS 7 on Windows Server 2008 
R2. I am currently getting the dreaded -1603 error. I did some research on the 
Internet and it's not quite clear whether WIX supports IIS7. See [1] and [2] 
for points of discussion.

[1] http://n2.nabble.com/wix-and-IIS7-td1694777.html
[2] 
http://stackoverflow.com/questions/686190/how-do-i-install-an-asp-net-mvc-application-on-iis-7-using-wix

Can someone please shed some light on this process? I need to make a decision 
whether in the current timescale I can make our current MSIs work or if I need 
to write some custom actions that leverage the IIS 7 PowerShell providers. I 
was hoping to have a stopgap solution that would allow me to deploy these sites 
in IIS 7 Classic Mode as-is. That way we could upgrade our production servers 
to Windows Server 2008 R2 without significant deployment changes.

Then I could address the deployment story more forthright.

Thanks again,
Navid
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Add Managed Handler

[Rob Mensching]

Unfortunately, no. Be a great thing to add to WiX v3.5 where there is more
IIS7 support.

On Mon, Jan 18, 2010 at 5:29 PM, Pierson Lee (PIE) <
pierson@microsoft.com> wrote:

> In IIS 7.0 there is a new option of "Add Managed Handler" under "Handler
> Mappings" which allows me to add a MIME Type handler (dll) to point to a
> MIME extension.
>
> Is there such an option within WiX that allows me to do this using the IIS
> extensions with the 3.0 RTM version?
>
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WIX v2.0 and IIS 7 -- Any stopgap solutions?

[Rob Mensching]

If you install the IIS6 Compatibility features then the WiX toolset custom
actions will work. In WiX v3.5, there is native support for IIS7
configuration.

On Mon, Jan 18, 2010 at 8:00 PM, Navid Azimi-Garakani
wrote:

> Hello--
>
> I have a large number of MSIs (think 75+) that are currently deploying to
> IIS 6 on Windows Server 2003 (32-bit). These MSIs are being built with WIX
> 2.0.3719.0. I need to get these MSIs to deploy to IIS 7 on Windows Server
> 2008 R2. I am currently getting the dreaded -1603 error. I did some research
> on the Internet and it's not quite clear whether WIX supports IIS7. See [1]
> and [2] for points of discussion.
>
> [1] http://n2.nabble.com/wix-and-IIS7-td1694777.html
> [2]
> http://stackoverflow.com/questions/686190/how-do-i-install-an-asp-net-mvc-application-on-iis-7-using-wix
>
> Can someone please shed some light on this process? I need to make a
> decision whether in the current timescale I can make our current MSIs work
> or if I need to write some custom actions that leverage the IIS 7 PowerShell
> providers. I was hoping to have a stopgap solution that would allow me to
> deploy these sites in IIS 7 Classic Mode as-is. That way we could upgrade
> our production servers to Windows Server 2008 R2 without significant
> deployment changes.
>
> Then I could address the deployment story more forthright.
>
> Thanks again,
> Navid
>
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Msi hangs on _RemoveFilePath

[Rob Mensching]

Try running a verbose log file (msiexec /i foo.msi /l*v log.txt) and see if
it provides more details.

On Mon, Jan 18, 2010 at 8:30 AM, SP_  wrote:

>
> Hi all,
> on some computers my msi hangs for ages. Logs says:
>
> MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: BindImage
> MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: ProgId
> MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: PublishComponent
> MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: SelfReg
> MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: Extension
> MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: Font
> MSI (s) (3C:A0) [17:13:57:996]: Note: 1: 2205 2:  3: Class
> MSI (s) (3C:A0) [17:13:58:001]: Note: 1: 2205 2:  3: _RemoveFilePath
>
> Installation was craeted by wix, has about 50 000 files and about 3 000
> components. Installation Requres msi.dll version 4.5. I validated
> installation by orca(it does nat have _RemoveFilePath table), orca reported
> the only error:
> ICE57   ERROR   Component 'Component0' has both per-user data and a keypath
> that
> can be either per-user or per-machine.
> Any ideas?
> --
> View this message in context:
> http://n2.nabble.com/Msi-hangs-on-RemoveFilePath-tp4414568p4414568.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to assign a default value to preprocessor properties

[Neil Sleightholm]

Something like this should do it:



  


Neil

-Original Message-
From: Joe Osman [mailto:joe.os...@tait.co.nz] 
Sent: 19 January 2010 03:05
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How to assign a default value to preprocessor
properties

I am using preprocessor properties in my WIX project and I assign them
values in msbuild when building the WIX project from the command line .
For example I have the following preprocessor properties: 
Var1=$(Var1);Var2=$(Var2)
I assign them values in msbuild in this way: msbuild
/p:Var1="value1";Var2="value2"

The problem is that when I build the project in Visual Studio those
properties get an empty value. I want to give these properties a default
value so that I will be able to build the WIX project from Visual Studio
and not just from the command line using msbuild.

Is there any way to assign these properties a default value that can be
overridden by msbuild ?

Thanks for your help !

===
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be the
subject of legal or other privilege, none of which is waived or lost by
reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no other
act on the email.
Unfortunately, we cannot warrant that the email has not been  altered or
corrupted during transmission.
===


--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to assign a default value to preprocessor properties

[Simon Dahlbacka]

> The problem is that when I build the project in Visual Studio those
> properties get an empty value. I want to give these properties a default
> value so that I will be able to build the WIX project from Visual Studio and
> not just from the command line using msbuild.
>
> Is there any way to assign these properties a default value that can be
> overridden by msbuild ?
>
> it sounds like you could provide the defaults in your .wixproj, i.e.
something along the lines of the following should work.. Repeat for Var2


defaultValueGoesHere

--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users