/SendEmail.jtp?type=nodenode=7589379i=1
Subject: [WiX-users] Quick question about WiXCA - CAQuietExec
We have an app that when runs produces a quick Dos Window and then goes away.
So we are using the WiXCA - CAQuietExec custom action to call the app in
quite mode. This work great, but my question
We have an app that when runs produces a quick Dos Window and then goes away.
So we are using the WiXCA - CAQuietExec custom action to call the app in
quite mode. This work great, but my question is if the App fails and I have
the WiXCA custom action set to Return the error code will it return
++ libs) to parse/extract the
CustomActionData make sure you use the companion APIs to build the property's
value (and visa versa).
From: jacob.hoo...@greenheck.com
To: wix-users@lists.sourceforge.net
Date: Tue, 2 Jul 2013 16:42:02 +
Subject: Re: [WiX-users] Quick Question
First guess
Hi All,
I am passing some properties to a custom action, and one of the values being
passed is quite large, and never seems to make it to the CA. I am wondering
what is the maximum size of a string that can be passed via CustomActionData?
Thanks,
Nick
Nicholas Miller (Network Administrator)
It's limited by memory, but when I exceeded it, I always got a failure (usually
when trying to retrieve the value in my deferred CA).
From: nmil...@livetechnology.com
To: wix-users@lists.sourceforge.net
Date: Tue, 2 Jul 2013 13:43:48 +
Subject: [WiX-users] Quick Question
Hi All,
I
Installer XML toolset.
Subject: Re: [WiX-users] Quick Question
It's limited by memory, but when I exceeded it, I always got a failure (usually
when trying to retrieve the value in my deferred CA).
From: nmil...@livetechnology.com
To: wix-users@lists.sourceforge.net
Date: Tue, 2 Jul 2013 13:43
-
From: Nick Miller [mailto:nmil...@livetechnology.com]
Sent: Tuesday, July 02, 2013 11:29 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Quick Question
Well, the value I am trying to pass is the contents of an INI file, so I doubt
it's running out of memory
Hi Wix users,
before I sink time into authoring installers and testing, I am seeking
your comments wether the following concept could work, or wether I have
missed something.
Assuming I have an INSTALLERA.msi, which consists of the features
MAINFEATURE and DATA1 and DATA2, and another
Message-
From: xx [mailto:contactnim...@googlemail.com]
Sent: Friday, May 28, 2010 6:50 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Quick Question: common features in multiple installers
Hi Wix users,
before I sink time into authoring installers
Make a condition for it using the VersionNT64 property (
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/system_folder_properties.asp
)
On 1/11/07, Eric Fesh [EMAIL PROTECTED] wrote:
Hello all:
I've got a situation where I need to launch a custom action when an
Levi:
Thanks... Much appreciated. I also found the Msix64 property, which I think
might be a cleaner solution for my purposes.
*chuckle* For some reason, it seems that I find answers faster by myself only
after I've sent an email asking for help...
--
Eric Fesh
Customer Support
, 2007 7:42 AM
To: Levi Wilson
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Quick question: How to determine if
Windows is64-bit at install time?
Levi:
Thanks... Much appreciated. I also found the Msix64 property,
which I think might be a cleaner solution for my purposes
))]]/RemoveExistingProducts
Please note that I inherited this J
Does this look right?
-Jeff
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Monday, September 25, 2006
11:24 PM
To: Jeff MacDuff
Cc: Wilson, Phil;
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Quick question
on upgrade
Jeff MacDuff wrote:
In my
InstallExecuteSequence I have this
reference:
RemoveExistingProducts After="InstallFinalize"![CDATA[(MyUpgrade
"C9BD4428-98AC-4AD0-9646-4E212B1BB770" AND (DefaultFeature = 3))]]/RemoveExistingProducts
As the Mythbusters say, "There's your
-users] Quick
question on upgrade checking
Jeff MacDuff wrote:
In my InstallExecuteSequence I have this reference:
RemoveExistingProducts After=InstallFinalize![CDATA[(MyUpgrade
C9BD4428-98AC-4AD0-9646-4E212B1BB770 AND (DefaultFeature = 3))]]/RemoveExistingProducts
As the Mythbusters
Jeff MacDuff wrote:
So would the
new syntax be this?
RemoveExistingProducts After="InstallFinalize/RemoveExistingProducts
Or
RemoveExistingProducts After="InstallFinalize
/
Assuming you have only one feature (DefaultFeature), you don't need to
check its install
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Tuesday, September 26, 2006
10:22 AM
To: Jeff MacDuff
Cc: Wilson, Phil;
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Quick
question on upgrade checking
Jeff MacDuff wrote:
So would the new syntax
Ok thanks for all the info.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Tuesday, September 26, 2006
10:56 AM
To: Jeff MacDuff
Cc: Wilson, Phil; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Quick
question on upgrade checking
Jeff MacDuff wrote:
The overall goal is that anytime I install the new package, it should
prompt to remove the old package regardless of language.
So if I have a English OS , with a DEU old package installed.. and I run
the new DEU package on this OS it should prompt me.
That's the case I
list the UpgradeCode and not the ProductCode ?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Monday, September 25, 2006
10:08 AM
To: Jeff MacDuff
Cc: Wilson, Phil;
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Quick
question on upgrade checking
Jeff MacDuff wrote:
Ok so I have
gone through the logs a few
times
In the
FindRelatedProducts section of the
MSI it does find 1 related product however the GUID it lists is the
ProductCode
of the Old ( V1) MSI not the UpgradeCode.
It finds it by the upgrade code but
Jeff MacDuff wrote:
It did find
the German V1 however
it didnt stop the install of V2 / uninstall v1
How are you doing that for English?
--
sig://boB
http://bobs.org
-
Take Surveys. Earn Cash.
Jeff MacDuff wrote:
Thats the
weird thing, I am not
doing anything special for English.. theres no English special syntax
I dont
believe.
Earlier you mentioned prompting for the upgrade; MSI doesn't do that so
there's gotta be something extra.
--
sig://boB
Is a previous version is detected, whats
the action the MSI takes?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Monday, September 25, 2006
9:28 PM
To: Jeff MacDuff
Cc: Wilson, Phil; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Quick
finds the old package.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson,
Phil
Sent: Friday, September 22, 2006 5:50 PM
To: Jeff MacDuff; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Quick question on upgrade checking
So we have an upgrade
, 2006 9:52 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Quick question on upgrade checking
What about version specs in your Wix UpgradeVersionElement? I don't know
how Wix behaves in the absence of them, but there's nothing in your Wix
that targets the versions you want
: Friday, September 22, 2006 11:15 AM
To: Wilson, Phil; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Quick question on upgrade checking
What version specs do you refer too?
Here is the WXS:
Upgrade Id=snip
UpgradeVersion RemoveFeatures=All Property=UPGRADE
IgnoreRemoveFailure=yes
@lists.sourceforge.net
Subject: RE: [WiX-users] Quick question on upgrade checking
UpgradeVersion has Minimum and Maximum strings that specify the range of
product versions that you want to look for and upgrade (IncludeMaximum
and IncludeMinimum are involved too). If you don't specify these values
I don't know what
} 1.0.0 2.0.0 260
All
-Jeff
-Original Message-
From: Jeff MacDuff
Sent: Friday, September 22, 2006 1:16 PM
To: 'Wilson, Phil'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Quick question on upgrade checking
Ok I just looked and both of the version fields are null ... I
: [WiX-users] Quick question on upgrade checking
Well that didn't work either.
Here is the old MSI that's installed on the machine (from property
table):
ProductVersion 1.0.0
UpgradeCode {C9BD4428-98AC-4AD0-9646-4E212B1BB770}
And here is the new MSI upgrade table
Yes, it's installed for all users.
-Original Message-
From: Wilson, Phil [mailto:[EMAIL PROTECTED]
Sent: Friday, September 22, 2006 2:23 PM
To: Jeff MacDuff; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Quick question on upgrade checking
Both old and new are installed
PROTECTED]
Sent: Friday, September 22, 2006 3:16 PM
To: Wilson, Phil; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Quick question on upgrade checking
Yes, it's installed for all users.
-Original Message-
From: Wilson, Phil [mailto:[EMAIL PROTECTED]
Sent: Friday, September 22
Of Jeff
MacDuff
Sent: Wednesday, September 20, 2006 5:17 PM
To: Stefan Pavlik
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Quick question on upgrade checking
It's still not working for me... here's what I did:
I looked at the new msi ( the one we are building now ) and in the
upgrade
Ok thanks for the tips.. I will review the
codes again and take a look.
From: Mike Dimmick
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 20,
2006 7:03 AM
To: Jeff MacDuff;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Quick
question on upgrade checking
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 20, 2006 6:32 AM
To: Jeff MacDuff
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Quick question on upgrade checking
Hi,
After reading the MSDN and Wix help (at the end of my email) I think
that you can ommit the ExcludeLanguages
35 matches
Mail list logo
