Does anyone know if there is a limit to the number of packages that can be
applied at once with MsiApplyMultiplePatches() or
Installer.ApplyMultiplePatches() in DTF? I've run into an issue where 84
packages will apply fine, but 85 and above results in a 1601 error code.
I've tried varying the leng
Is there a method for getting the currently executing custom action name
from within a custom action?
So if custom actions ca1 and ca2 call a dll function func1, I want to be
able to determine from within func1 if it was called by ca1 or ca2.
Thoughts?
Matt
-
rceforge to track this issue?
>
>
>
> *From:* Matt Ziegler [mailto:idaho...@gmail.com]
> *Sent:* Wednesday, January 07, 2009 11:35 AM
> *To:* Windows Installer XML toolset developer mailing list; General
> discussion for Windows Installer XML toolset.
> *Subject:* [WiX
I'm having the same issue as this thread (data size limitation for
customactiondata in DTF)
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg20675.html
Has there been any progress on determining the actual root cause of this or
is using a temp file about the only method at this point
Any insight from anyone?
On Wed, Nov 19, 2008 at 2:58 PM, Matt Ziegler <[EMAIL PROTECTED]> wrote:
> I've been playing around with installing multiple instances of an
> application used the element, works quite well. I'm
> trying to create a patch between 2 versions an
I run a continuous integration server and run multiple installer builds at
the same time and haven't received this error before. Are the 2 projects in
the same working directory? What version of WiX are you running?
Matt
On Thu, Nov 20, 2008 at 12:32 PM, Chris Eldredge
<[EMAIL PROTECTED]>wrote:
I've been playing around with installing multiple instances of an
application used the element, works quite well. I'm
trying to create a patch between 2 versions and apply that one patch to
multiple installed instances and according to
http://msdn.microsoft.com/en-us/library/aa369528(VS.85).aspx<
Is there a method to change the name attribute of the file element during the
execution of the MSI? I'm trying to set the name attribute to
"[SomeProperty]-filename.exe" where [SomeProperty] is a number. Instead of
the file being named on the system 1-filename.exe it is named
[SomeProperty]-file
8 matches
Mail list logo