it's
> like being in a homebuilder's forum and asking about the best glue to
> stick together the walls of your paper house. They'll tell you not to
> do it and you won't get many replies because it's not something anyone
> actually does.
>
> ---
>
r, so be
> sure that's the right one - that's the native 64-bit folder.
> -------
> Phil Wilson
>
>
> On Thu, Feb 6, 2014 at 7:25 PM, Gerry Reno wrote:
>> It knows about our custom actions as well and they rollback just fine.
>>
>>
>> On 02/
TORY\\")
And now since I added InstallScope="perMachine" the LogonUser on XP gets set to
SYSTEM instead of the user name. And
this is why things fail on XP.
On Win 7 this is not a problem. The LogonUser stays as the user name.
How to fix this?
On 02/06/2014 05:41 PM, Gerry Reno w
ence handles
> uninstall, rollback, upgrade, etc).
>
> Dave
>
> On 2/6/2014 5:35 PM, Gerry Reno wrote:
>> Ok, after some experiments:
>>
>> The copy file is like this:
>> CustomActionSchedule(Action=CopyFile,ActionType=3073,Source=BinaryData,Target=CAQuietExec,Cu
I now have this half-way working.
Installing on Windows 7 w/UAC succeeds
Installing on Windows XP fails
In .wxs:
InstallScope="perMachine"
InstallPrivileges="elevated"
CopyFile is setup in an immediate property and then executed deferred
without impersonation.
XP Install Log
oduct must install in the
Program Files tree, then it needs to be "perMachine".
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
Phil, sorry, correction, my configuration is:
InstallScope="perUser"
InstallPrivileges="elevated"
On 02/03/2014 02:52 PM, Gerry Reno wrote:
> InstallPrivileges="elevated"
> InstallScope="perMachine"
>
>
>
> Feb
--
Phil Wilson
On Mon, Feb 3, 2014 at 10:38 AM, Gerry Reno wrote:
> I am still having difficulty getting this install to work reliably.
>
> Today I go to uninstall / reinstall on this Win 7 machine w/UAC enabled and
> it refuses to install.
>
> First, I uninstalled the prev
; From: roberthyang
> Sent: Wednesday, January 22, 2014 4:26 PM
> To: General discussion for Windows Installer XML toolset.
>
>
>
>
>
> Also look into Package/InstallScope, which might be more appropriate.
>
>
> Gerry Reno wrote
>> It looks like adding
>
>
>
> From: roberthyang
> Sent: Wednesday, January 22, 2014 4:26 PM
> To: General discussion for Windows Installer XML toolset.
>
>
>
>
>
> Also look into Package/InstallScope, which might be more appropriate.
>
>
> Gerry Reno wrote
>> It lo
It looks like adding this to Package may do the trick:
|InstallPrivileges="elevated"|
I'll try it and see.
On 01/21/2014 08:21 PM, Gerry Reno wrote:
> I have a WIX installer built that installs fine on XP machines.
>
> When I go to install on Win 7 machines that have
I have a WIX installer built that installs fine on XP machines.
When I go to install on Win 7 machines that have UAC enabled the install gets a
Premature Failure and rolls back.
How do I get the installer to install on these Win 7 machines without disabling
UAC?
-
sching wrote:
> What exactly is not intuitive? The fact that backslash is the escape
> character for paths (not sure where that is documented)? The fact that the
> Windows Installer ends all folders in backslashes (that is documented in the
> MSI SDK)?
>
> -----Original Mess
a path with a backslash on it. For example:
>
> test.exe "c:\foo foo\bar\" "c:\baz baz\quuz\"
>
>
> -Original Message-
> From: Gerry Reno [mailto:gr...@verizon.net]
> Sent: Friday, December 20, 2013 1:46 PM
> To: wix-users@lists.sourceforge
Yes, agreed. The illustration was just of one of the many ways that were
tested.
As I stated earlier, I tested both ways including moving the quote to the end.
And the command line produces different results than WIX.
I just got finished another battery of tests without calling cmd.exe and got
On 12/20/2013 03:59 PM, Phill Hogland wrote:
> Aside from all the other good points which folks have made, if there was some
> reason to do the following:
> '/k "[INSTALLDIR]"/myprogram.exe'
>
> Is the second double quote above in the wrong place, and should be moved to
> the end of the path?
> '/k
On 12/20/2013 02:23 PM, David Connet wrote:
>> From: Gerry Reno
>> To: wix-users@lists.sourceforge.net
>> Cc:
>> Sent: Friday, December 20, 2013 10:42 AM
>> Subject: Re: [WiX-users] ExeCommand will not accept any path with spaces
>>
>> On 12/20/201
Castro [mailto:0ptikgh...@gmx.us]
> Sent: Friday, December 20, 2013 10:38 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] ExeCommand will not accept any path with spaces
>
> On 12/20/13, 10:27 AM, Gerry Reno wrote:
>> I not certain this will work. It might with something l
On 12/20/2013 01:57 PM, Jeremy Farrell wrote:
>> From: Gerry Reno [mailto:gr...@verizon.net]
>> Sent: Friday, December 20, 2013 6:46 PM
>> On 12/20/2013 01:43 PM, Jeremy Farrell wrote:
>>>> From: Gerry Reno [mailto:gr...@verizon.net]
>>>> Sent: Friday, De
On 12/20/2013 01:43 PM, Jeremy Farrell wrote:
>> From: Gerry Reno [mailto:gr...@verizon.net]
>> Sent: Friday, December 20, 2013 6:28 PM
>> On 12/20/2013 01:16 PM, Edwin Castro wrote:
>>> On 12/20/13, 9:49 AM, Gerry Reno wrote:
>>>> It's not a Windows
On 12/20/2013 01:20 PM, David Connet wrote:
>> From: Gerry Reno
>> To: wix-users@lists.sourceforge.net
>> Cc:
>> Sent: Friday, December 20, 2013 10:03 AM
>> Subject: Re: [WiX-users] ExeCommand will not accept any path with spaces
>>
>> On 12/20/2013 12:4
On 12/20/2013 01:16 PM, Edwin Castro wrote:
> On 12/20/13, 9:49 AM, Gerry Reno wrote:
>> It's not a Windows program. It's a CUI program that you launch from cmd.exe
> Which you can still more easily start directly. If you insist in
> wrapping the call with cmd.ex
On 12/20/2013 12:49 PM, Edwin Castro wrote:
> On 12/20/13, 9:46 AM, Gerry Reno wrote:
>> On 12/20/2013 10:44 AM, David Connet wrote:
>>>> From: Gerry Reno [mailto:gr...@verizon.net]
>>>> >
>>>>>>
>>>> I don't think that&
On 12/20/2013 12:47 PM, Edwin Castro wrote:
> On 12/19/13, 5:31 PM, Gerry Reno wrote:
>> The relevant code section is:
>>
>>
>>
>> >Execute='deferred'
>>ExeCommand='/k "[INSTALLDIR]"/myprogram.exe'
On 12/20/2013 10:44 AM, David Connet wrote:
> From: Gerry Reno [mailto:gr...@verizon.net]
> >
>>
> I don't think that's legal. cmd.exe is not a redistributable file. You
> can't include it in your installer.
cmd.exe is not being distributed. Binary is
rrent version of WIX.
> Try "[INSTALLDIR]/myprogram.exe" instead. If that doesn't work then
> you can go to the lengths described in
> http://blogs.msdn.com/b/twistylittlepassagesallalike/archive/2011/04/23/everyone-quotes-arguments-the-wrong-way.aspx.
>
> Sincerel
I have been trying to get WIX to deal with an ExeCommand which uses INSTALLDIR
which contains spaces in the path without
success.
I won't repeat the bug I opened on this. Here is the link:
http://wixtoolset.org/issues/4257/
As you can see in the bug. I cannot get a cmd.exe to launch one of m
27 matches
Mail list logo
