Hello Phil,
Thank You for Your answer, but this doesn't help.
I have set the InstallPrivileges to elevated, as You can see here:
Package InstallerVersion=405
Compressed=yes
InstallScope=perMachine
InstallPrivileges=elevated /
But even when i execute
Hi all,
Is there a standard way, as there is for checking VS installed by using
WixVSExtension, to check if the Visual Studio SDK is installed?
Any suggestion is welcome.
Mario Majcica
--
Download BIRT iHub F-Type -
You have 'TESTPC/Users' The separator should be a backslash.
Try 'TESTPC\Users'
Another issue that you may want to consider is that Group names are
localized. I use an mba to get the localized name, and then pass that in a
Burn variable (in this case the name of the Administrators group).
It is curious that the error message has a forward slash, rather than a
backslash:
CreateUser: Error 0x80004005: Failed to get group 'TESTPC/Users'.
Both the Users group and the Administrators group are in the 'Builtin'
domain, but the name of the group might be localized so using the English
Nick,
It's not a script, but a configuration tool/Application with UI.
Thanks for the input, it is very appreciated.
Marc
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: December-15-2014 12:51 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users]
Configure on first run is a common pattern with some installs.
One question I have is if it always needs to be elevated. Is the configuration
tool a separate executable than the application? Does it provide any value when
in low privilege mode? If it's yes to the first and no to the second,
After my previous answer I started questioning my whole approach.
The configuration tool has the responsibility amongst other things to bind
an SSL certificate to a port. I initially did not want to do this as part
of the install, but as part of a configuration tool, since the user can
choose to
That text is a template from the WiX ActionText for copying the files,
it might be for the InstallFiles action. It should be a template with
parameter number in square brackets, maybe not exactly this: File:[1],
Directory:[9], Size:[6] but similar. To get to the point, I'd guess
that the parameter
Hi,
I am trying to run a powershell script in deferred custom action, but it
fails. The command works when manually run from command prompt.
CustomAction Id=PropCA Property=UpdateIdentityCA
Value=quot;[POWERSHELLEXE] -Version 2.0 -NoProfile -NonInteractive
-InputFormat None
CustomAction Id=PropCA Property=UpdateIdentityCA
Value=quot;[POWERSHELLEXE] -Version 2.0 -NoProfile -NonInteractive
-InputFormat None -ExecutionPolicy Bypass -File
quot;[#UpdateIdentity.ps1]quot; testhub\ericd Manatee1 quot;/
The above CA has a quot missing and Execute=immediate property
Thanks for pointing out the missing quote. After fixing that, I am still not
able to run the ps script. Also, I am now enclosing the quotes around the
file path like this -
-File C:\Program Files (x86)\\Bridge
Server\Bridges\Exchange\UpdateIdentity.ps1 testhub\ericd pwd1
Why is WixCA not
The quotes look good, my bad!
-Original Message-
From: Pavan Konduru [mailto:pavan.kond...@accelrys.com]
Sent: Tuesday, December 16, 2014 12:35 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] CustomAction to run powershell script
CustomAction Id=PropCA
Did you add the Execute=immediate to the CustomAction PropCA?
-Original Message-
From: wixtester [mailto:sangee...@hotmail.com]
Sent: Tuesday, December 16, 2014 12:51 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] CustomAction to run powershell script
Thanks for
Thanks for the hint Nick. Here is my torch cmdline :
%WIX%\torch -ax %PATCH_ADMIN_INSTALL% -p -xo
%BASE_ADMIN_INSTALL%\setup%BASE%.msi %PATCH_ADMIN_INSTALL%\setup.msi -out
%PATCHDIR%\diff.wixmst
I tried both -ext UtilExtension and -ext
Also the PropCA must run before the UpdateIdentityCA in the Installexecute
sequence.
-Original Message-
From: Pavan Konduru [mailto:pavan.kond...@accelrys.com]
Sent: Tuesday, December 16, 2014 12:59 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] CustomAction
-ext %WIX%\WixUtilExtension.dll
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/XmlFile-or-XmlConfig-in-patch-msp-tp7598517p7598615.html
Sent from the wix-users mailing list archive at Nabble.com.
Does /-ext WixUtilExtension/ work?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/XmlFile-or-XmlConfig-in-patch-msp-tp7598517p7598616.html
Sent from the wix-users mailing list archive at Nabble.com.
I tried this, and also '-ext %WIX%\WixUtilExtension.dll', and while
torch/pyro didn't complain, I also didn't see an XmlFile table added by the
.msp. The XML file was not modified when I ran the resulting patch, though
the log did indicate that the enclosing component was installed.
Same result
Mario,
I don’t know if there is a way from WixVSExtension. However, if you know the
UpgradeCode for the particular Visual Studio SDK, you could look for it in an
Upgrade block (assuming was installed via MSI). Perhaps something like this:
Upgrade Id={UPGRADE_GUID_HERE}
UpgradeVersion
19 matches
Mail list logo
