Does this help:
http://blogs.technet.com/b/alexshev/archive/2008/04/04/from-msi-to-wix-part-
16-installable-items-handling-installation-media.aspx
-Original Message-
From: Philip Garofalo [mailto:ph...@vavatini.com]
Sent: Friday, August 13, 2010 6:55 PM
To: wix-users@lists.sourceforge.n
Hi Igor,
I've been having problems with Internet connection at home recently and I am
sorry I don't have time to give you extended answer. What you want is
easily doable and this is more of XPATH issue. Attached is my old document
I wrote for my colleagues which may help you to understand how to
Hi Eric,
Are you sure that msi.ini file is in the default windows folder?
Alex
-Original Message-
From: Eric Napier [mailto:napi...@gmail.com]
Sent: Tuesday, July 21, 2009 3:34 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] inifilesearch doesn't execute
I'm having a prob
Clarification: CAs need to be scheduled in InstallUISequence and Execute
attribute should be set to "immediate".
-Original Message-----
From: Alex Shevchuk [mailto:shevc...@live.com]
Sent: Monday, July 20, 2009 2:24 PM
To: 'General discussion for Windows Installer XML to
Hi Rafael,
This is one of those cases when keypath is very important. Target of the
shortcut in advertised shortcut is the keypath of the component. When you
don't specify the keypath for your component (as in the sample below), WiX
will select first file as a keypath. Hence the behavior you're
Hi Jirong,
Schedule custom CAs in InstallUISequence.
Regarding ICE warning - it looks like setting Execute attribute to
"firstSequence" also adds behind the scene deferred
(msidbCustomActionTypeInScript) flag as well. You can verify it be checking
the value of Type column in CustomAction table.
>Can a Type 18 custom action have a dynamically designated command line
>property such that the target executable of the custom action is aware
>that it is being executed during installation or uninstallation? If so,
>what internal variable can be used to determine the current condition of
>the MSI
Hi David,
You can use WISubStg.vbs:
WISubStg.vbs "full path to msi" "full path to mst" TransformName
Command line for msiexec:
Msiexec /I "full path to msi" TRANSFORMS=:TransformName
At the very end of
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-7-
customizing-ins
My understanding of original problem is that environment variables are
created on install, but not deleted on uninstall.
Action="remove" must be used when environment variable needs to be deleted
*on install*.
As Rob already mentioned, there is nothing wrong with tag
itself. Problem is somewhere
> However what I would like to have is no dialog but restart of the app.
Hi Stefan,
This blog post
(http://blogs.msdn.com/windows_installer_team/archive/2006/12/11/windows-ins
taller-and-restart-manager-msi-files-in-use-v2.aspx) explains the behavior
in different UI modes. Looks like what you w
Search for "WixUI_InstallDir Dialog Set" in WiX.chm.
-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com]
Sent: Tuesday, June 09, 2009 12:28 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How do I remove or bypass the dialog w
Path attribute has AnyPath type
(http://msdn.microsoft.com/en-us/library/aa367562(VS.85).aspx). It is
either actual path (or subpath) or it may contain property enclosed in
brackets. My guess is that TOOLSDIR is a property containing path where
MCT.exe is located. If that assumption is correct,
one for the
system folder in the main file or in the fragment?
-Original Message-
From: Alex Shevchuk [mailto:shevc...@live.com]
Sent: Friday, June 05, 2009 12:00 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Variable not recognized i
HelpDirectory is a key to Directory table. Do you have a entry
for SystemFolder?
Alex
-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com]
Sent: Friday, June 05, 2009 8:49 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Vari
Major upgrade requires ProductCode, PackageCode, and ProductVersion to be
different in the new version.
I don't know if that will make any difference, but because you product has 4
fields in the version number, try to change mailto:gulfam.mu...@gmail.com]
Sent: Friday, June 05, 2009 8:08 AM
To: Ge
table entiry
(upgradecode) {82594B5A-5CA6-4C6F-A9F1-EF75A504B592} (VersionMin)
1.0.0 (VersionMax) 12.0.1.9020 (Attributes) 256 (actionproperty)
OLDERVERSIONBEINGUPGRADED
> On Thu, Jun 4, 2009 at 4:37 PM, Alex Shevchuk wrote:
>>
>> > Language="!(l
Make sure that var.UpgradeCode and have the same
value.
Alex
--
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that in
>It shows the value in shortcut property "[INSTALLDIR]ALMGUI" which is like
hard code value.
Use instead of and schedule it accordingly.
sets the value to a string value, whereas is a
wrapper for Type 51 CA and can handle Formatted data type.
Alex
>So I tried
>
>How can I set the directory [INSTALLDIR]ALMGUI to WorkingDirectory
WorkingDirectory contains the name of the property that has the path.
Try convert "StartinDir" to all uppercase and set Secure="yes", so that it
can be passed from client to server process.
Alex
>However I think it searches only system folder. The .ini file is part of
>my installation and copies on user machine. So how can I search this
>one?
Actually, WI requires file to be in the Windows folder.
You can either copy your .ini file to windows folder during installation or
custom action is
You need .
Alex
-Original Message-
From: rahul.ekb...@sungard.com [mailto:rahul.ekb...@sungard.com]
Sent: Monday, May 25, 2009 5:25 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Read the text from .ini file.
Hi,
How can I read the text from .ini file and store it into p
You can check for presence of CustomActionData property. It will be set if
custom action is deferred.
Alex
-Original Message-
From: Dov Kleinman [mailto:d...@microsoft.com]
Sent: Thursday, May 21, 2009 12:55 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to identify th
Hi Jacques,
Yes, major upgrade removes previous version and if upgrade will be
uninstalled, the whole product will be uninstalled. There is no support for
going back to previous version.
What you may or may not want in this case is uninstallable patch.
Alex
-Original Message-
From: Ja
d elevated privileges to run CeAppMgr.exe but it seems that I
cannot get them on Vista unless I set Impersonate="no" and deferred
execution.
Is there any workaround to this?
Thanks,
Tom
Alex Shevchuk schrieb:
> Well, your custom action is deferred, no-impersonate, which means that it
&g
Well, your custom action is deferred, no-impersonate, which means that it
will be run under Local System credentials. Local System, albeit very
powerful, has some limitations, like no access to network, etc.
You can try to set Impersonate="yes".
Alex
-Original Message-
From: Tom Kazim
I don't have ready to use solution, but
http://blogs.technet.com/alexshev/archive/2008/06/30/from-msi-to-wix-part-17
-windows-installer-automation-interface-part-2.aspx may give you a good
starting point, if that's what you want.
Alex
-Original Message-
From: Chris Ridd [mailto:chrisr...
PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Two Entries in Add or Remove Programs
Alex Shevchuk wrote:
> Well, if per-user/per-machine context did not change, I can only
> suggest comparing your upgrade steps to steps in here:
> ...from-msi-to-w
>If I pass a property to my msi via command line, it seems like it is only
>reflected in the current msi context but not when removeexistingproducts is
>called to uninstall the old product. Is tehre any way to make this public
>property pass to old msi as well?
You need to preserve value of prope
> The 'two entries' problem continues.
Well, if per-user/per-machine context did not change, I can only suggest
comparing your upgrade steps to steps in here:
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-
major-upgrade.aspx
Alex
-
>And how about QWORD value?
Looks like Registry table
(http://msdn.microsoft.com/en-us/library/aa371168(VS.85).aspx) supports
only:
- REG_SZ
- REG_MULTI_SZ
- REG_EXPAND_SZ
- REG_BINARY
- REG_DWORD
No REG_QWORD and XXX_LITTLE_ENDIAN (or REG_LINK) support, I think.
Alex
--
>I go back to Wix Edit and change both the Product GUID and the Package
GUID.
>The Upgrade ID GUID does not change. I rebuild the MSI setup package.
> ...
>
>
> Maximum="!(bind.FileVersion.gssta_exe)" IncludeMinimum="yes"
>OnlyDetect="no" IncludeMaximum="no" Minimum="0.0.0.0" />
> Minimum="!(
Hi Alex,
Short answer: Yes, maybe, no. :-)
Detailed answer:
http://blogs.technet.com/alexshev/archive/2009/05/11/is-it-possible-to-use-r
egistrysearch-result-in-registryvalue.aspx
Regards,
Alex
-Original Message-
From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com]
Sent: Monday, May
Hi Karma,
Actually, after carefully re-reading your question, I don't think you can
achieve what you want. Only temporary tables, rows, or columns can be
modified. In your case you are trying to modify existing component's 64-bit
flag. Won't work. Besides, I think that 32-bit and 64-bit versio
See
http://robmensching.com/blog/posts/2007/4/27/How-to-create-an-uninstall-shor
tcut-and-pass-all-the
Alex
-Original Message-
From: slmnow [mailto:slm...@hotmail.com]
Sent: Thursday, May 07, 2009 7:24 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating Internet Shorcu
To add to response from Curtis Jewell:
During installation WI is using in-memory copy of original MSI. As a
result, no changes to original MSI are allowed and changes can be made to
in-memory copy only. To indicate your intent to change in-memory copy use
TEMPORARY as Curtis suggested.
Alex
-
Here is the order:
- InstallUISequence (everything up to ExecuteAction)
- ExecuteAction in InstallUISequence calls InstallExecuteSequence (you can
think of it as a blocking function call. You will get control back after
all actions in InstallExecuteSequence are done)
- Any action scheduled after
George,
To get behavior you want:
* Make your file a keypath of your component (File/@KeyPath="yes")
* Use /fc option to repair your installation
Alex Shevchuk
On Tue, Mar 25, 2008 at 5:16 PM, Georgi Shopov <[EMAIL PROTECTED]> wrote:
> Hi,
>
> can any body give
37 matches
Mail list logo
