[WiX-users] Shortcuts created in ALLUSER mode invokes MSI installer
After turning on MSI logging, I found that my issue is more complicate. The shortcut is created for a file installed in ALLUSER ( Per Machine) mode, so I must set Advertise=yes on the shortcut as shown below. This turns out be the problem later. Component Id=SomeApp Guid =Guid File Id =SomeApp_exe Name =SomeApp.exe Source =$(var.MSIBuildDir)Signed\EXE\SomeApp.exe Shortcut Id=SomeAppShortcut Directory =BLAHProgramMenuFolder Name=SomeApp Advertise=yes Icon=SomeAppIcon.exe DisplayResourceDll =[!SomeApp_exe] DescriptionResourceDll =[!SomeApp_exe] Icon Id=SomeAppIcon.exe SourceFile =$(var.MSIBuildDir)Signed\EXE\SomeApp.exe/ /Shortcut /File /Component The above worked like charm, until i have to place a uninstall shortcut for the product, like the code below Component Id =BLAHUninstall Guid =0E588613-C67B-402A-9F50-BDF4A833F420 RegistryValue Id=BLAHUninstaller Root=HKCU Key=SOFTWARE\MyCompany\BLAH Value=BLAHUnistall Type=string Name =BLAHUninstall KeyPath =yes/ Shortcut Id=UninstallBLAH Name=Uninstall BLAH Target=[System64Folder]msiexec.exe Arguments=/x [ProductCode] Directory=BLAHProgramMenuFolder Description=Uninstalls BLAH / /Component Now, because this is the only way i can place an uninstall link, with a dummy entry in the HKCU root key. When a user clicks the above advertised SomeApplication.exe shortcut, msi tries to install the dummy registry key in HKCU root key, and so i have an msi installation going when the user uses the shortcut for the first time. Is there any way i can place a Unistall shortcut without a per-user Component (Registry Key in this case) ? Or is it possible to add a non-advertised shortuct for items installed on Per-Machine Mode ? Any suggestions are highly appreciated. thanks Arun V Rob Wrote: -- Turn on the MSI logging registry key and check out the verbose log file. It'll tell you which component is getting reinstalled. The EventViewer will also give you the Component GUID but I find the verbose log file easier to work through. Arun Wrote : --- I am creating some shortcuts in my Wix installer script under ALL USER, by setting the property value to 1. My shortcuts do get created in ProgramMenuFolder under All Users section, and are visible to all users, irrespective of who installed it. But, when a user (not the one who installed it) clicks on a shortcut, it tries to run the msi installer again and goes looking for the original msi used to perform the installation. I am not sure, how to avoid this behaviour ? User performing the initial intall is infact admin on the machine, and the installation doesnt give any error. But shortcuts for some reason doesnt seem to work for a different user. Any idea why this happens ? thanks for your help in advance. Arun * Arun Kumar The Distance between heaven and earth, is not a matter of Altitude, but ATTITUDE - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shortcuts created in ALLUSER mode invokes MSI installer
2008/10/30 Arun Kumar A V [EMAIL PROTECTED]: After turning on MSI logging, I found that my issue is more complicate. The shortcut is created for a file installed in ALLUSER ( Per Machine) mode, so I must set Advertise=yes on the shortcut as shown below. This turns out be the problem later. Component Id=SomeApp Guid =Guid File Id =SomeApp_exe Name =SomeApp.exe Source =$(var.MSIBuildDir)Signed\EXE\SomeApp.exe Shortcut Id=SomeAppShortcut Directory =BLAHProgramMenuFolder Name=SomeApp Advertise=yes Icon=SomeAppIcon.exe DisplayResourceDll =[!SomeApp_exe] DescriptionResourceDll =[!SomeApp_exe] Icon Id=SomeAppIcon.exe SourceFile =$(var.MSIBuildDir)Signed\EXE\SomeApp.exe/ /Shortcut /File /Component The above worked like charm, until i have to place a uninstall shortcut for the product, like the code below Component Id =BLAHUninstall Guid =0E588613-C67B-402A-9F50-BDF4A833F420 RegistryValue Id=BLAHUninstaller Root=HKCU Key=SOFTWARE\MyCompany\BLAH Value=BLAHUnistall Type=string Name =BLAHUninstall KeyPath =yes/ Shortcut Id=UninstallBLAH Name=Uninstall BLAH Target=[System64Folder]msiexec.exe Arguments=/x [ProductCode] Directory=BLAHProgramMenuFolder Description=Uninstalls BLAH / /Component Now, because this is the only way i can place an uninstall link, with a dummy entry in the HKCU root key. When a user clicks the above advertised SomeApplication.exe shortcut, msi tries to install the dummy registry key in HKCU root key, and so i have an msi installation going when the user uses the shortcut for the first time. Is there any way i can place a Unistall shortcut without a per-user Component (Registry Key in this case) ? Or is it possible to add a non-advertised shortuct for items installed on Per-Machine Mode ? Any suggestions are highly appreciated. thanks Arun V Already answered in this list, search the archive. Look here for background: http://robmensching.com/blog/archive/2007/04/27/How-to-create-an-uninstall-shortcut-and-pass-all-the.aspx And there for another solution: http://msdn.microsoft.com/en-us/library/aa368297(VS.85).aspx - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Shortcuts created in ALLUSER mode invokes MSI installer
I am creating some shortcuts in my Wix installer script under ALL USER, by
setting the property value to 1. My shortcuts do get created in
ProgramMenuFolder under All Users section, and are visible to all users,
irrespective of who installed it.
But, when a user (not the one who installed it) clicks on a shortcut, it tries
to run the msi installer again and goes looking for the original msi used to
perform the installation.
I am not sure, how to avoid this behaviour ? User performing the initial intall
is infact admin on the machine, and the installation doesnt give any error. But
shortcuts for some reason doesnt seem to work for a different user.
Any idea why this happens ?
thanks for your help in advance.
Arun
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Sent: Wednesday, October 29, 2008 4:47:44 PM
Subject: WiX-users Digest, Vol 29, Issue 224
Send WiX-users mailing list submissions to
wix-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/wix-users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than Re: Contents of WiX-users digest...
Today's Topics:
1. Re: Store an RTF string in a Property? (Rob Mensching)
2. memory question (Natxo Mateos)
3. Re: StartMetabaseTransaction: Error 0x8007041d: failedto get
IID_IIMSAdminBase object ( S?bastien Mouren )
4. Directories in merge module (Ulf Jonson)
5. Re: Directories in merge module (Rob Mensching)
6. MSMQ Error (David Gonzalez)
--
Message: 1
Date: Wed, 29 Oct 2008 11:33:47 -0700
From: Rob Mensching [EMAIL PROTECTED]
Subject: Re: [WiX-users] Store an RTF string in a Property?
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
From the MSI SDK: http://msdn.microsoft.com/en-us/library/aa371540.aspx
ScrollableText Control
This control displays a long string of text that cannot fit entirely on the
page. A common use for this control is displaying the license agreement.
Note that the string of text used with this control cannot contain an embedded
property. To display text with embedded properties use instead the Text
Control.
Other things: http://blogs.msdn.com/robmen/archive/2006/05/30/610950.aspx
-Original Message-
From: Andrew Kendall [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 08:46
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Store an RTF string in a Property?
Hi All,
Is it valid to hold a RTF string in a Property, like this:
Property Id=CONFIRMINSTALLRTF
Value={\rtf1\ansi\deff0{\fonttbl{\f0\fnil\fcharset0 MS Sans
Serif;}}\viewkind4\uc1\pard\lang1033\f0\fs17 Some text\par } /
and then use this property in a ScrollableText control of a dialog:
Control Id=SummaryText Type=ScrollableText X=20 Y=80 Width=330
Height=100 Sunken=no TabSkip=yes
Text[CONFIRMINSTALLRTF]/Text
/Control
If so, I'm doing something wrong, as the example text does not appear in the
dialog :(
I'm actually trying to create a summary dialog at the end of the gui sequence,
to confirm to the user what will be installed. I want to present some free-form
text, so it seems that using a ScrollableText control is a better idea than,
say, a bunch of Text controls.
I've seen a post showing how a Custom Action can insert RTF text into a MSI db
Control record, so I was hoping I could do the same with a Property, ie
MsiSetProperty. As with most of what I've gleaned about MSI/Wix, it's all a
hideously painful struggle to make any progress, and so once again, my
dejection has got the better of me and I eagerly look for pointers/assistance
from the WWW (World Wide Wix) community. Many thanks for your time and
attention.
Yours truly,
Andrew Kendall
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Message: 2
Date: Wed, 29 Oct 2008 19:44:17 +0100
From: Natxo Mateos [EMAIL PROTECTED]
Subject: [WiX-users] memory question
To: wix-users@lists.sourceforge.net
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi,
I'm having some problems with
Re: [WiX-users] Shortcuts created in ALLUSER mode invokes MSI installer
Turn on the MSI logging registry key and check out the verbose log file. It'll
tell you which component is getting reinstalled. The EventViewer will also
give you the Component GUID but I find the verbose log file easier to work
through.
-Original Message-
From: Arun Kumar A V [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 14:33
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Shortcuts created in ALLUSER mode invokes MSI installer
I am creating some shortcuts in my Wix installer script under ALL USER, by
setting the property value to 1. My shortcuts do get created in
ProgramMenuFolder under All Users section, and are visible to all users,
irrespective of who installed it.
But, when a user (not the one who installed it) clicks on a shortcut, it tries
to run the msi installer again and goes looking for the original msi used to
perform the installation.
I am not sure, how to avoid this behaviour ? User performing the initial intall
is infact admin on the machine, and the installation doesnt give any error. But
shortcuts for some reason doesnt seem to work for a different user.
Any idea why this happens ?
thanks for your help in advance.
Arun
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Sent: Wednesday, October 29, 2008 4:47:44 PM
Subject: WiX-users Digest, Vol 29, Issue 224
Send WiX-users mailing list submissions to
wix-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/wix-users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than Re: Contents of WiX-users digest...
Today's Topics:
1. Re: Store an RTF string in a Property? (Rob Mensching)
2. memory question (Natxo Mateos)
3. Re: StartMetabaseTransaction: Error 0x8007041d: failedto get
IID_IIMSAdminBase object ( S?bastien Mouren )
4. Directories in merge module (Ulf Jonson)
5. Re: Directories in merge module (Rob Mensching)
6. MSMQ Error (David Gonzalez)
--
Message: 1
Date: Wed, 29 Oct 2008 11:33:47 -0700
From: Rob Mensching [EMAIL PROTECTED]
Subject: Re: [WiX-users] Store an RTF string in a Property?
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
From the MSI SDK: http://msdn.microsoft.com/en-us/library/aa371540.aspx
ScrollableText Control
This control displays a long string of text that cannot fit entirely on the
page. A common use for this control is displaying the license agreement.
Note that the string of text used with this control cannot contain an embedded
property. To display text with embedded properties use instead the Text
Control.
Other things: http://blogs.msdn.com/robmen/archive/2006/05/30/610950.aspx
-Original Message-
From: Andrew Kendall [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 08:46
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Store an RTF string in a Property?
Hi All,
Is it valid to hold a RTF string in a Property, like this:
Property Id=CONFIRMINSTALLRTF
Value={\rtf1\ansi\deff0{\fonttbl{\f0\fnil\fcharset0 MS Sans
Serif;}}\viewkind4\uc1\pard\lang1033\f0\fs17 Some text\par } /
and then use this property in a ScrollableText control of a dialog:
Control Id=SummaryText Type=ScrollableText X=20 Y=80 Width=330
Height=100 Sunken=no TabSkip=yes
Text[CONFIRMINSTALLRTF]/Text
/Control
If so, I'm doing something wrong, as the example text does not appear in the
dialog :(
I'm actually trying to create a summary dialog at the end of the gui sequence,
to confirm to the user what will be installed. I want to present some free-form
text, so it seems that using a ScrollableText control is a better idea than,
say, a bunch of Text controls.
I've seen a post showing how a Custom Action can insert RTF text into a MSI db
Control record, so I was hoping I could do the same with a Property, ie
MsiSetProperty. As with most of what I've gleaned about MSI/Wix, it's all a
hideously painful struggle to make any progress, and so once again, my
dejection has got the better of me and I eagerly look for pointers/assistance
from the WWW (World Wide Wix) community. Many thanks for your time and
attention.
Yours truly,
Andrew Kendall
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url
