e
>> the VS2012 beta had over 110 separate packages in it's bundle.
>>
>> -Original Message-
>> From: Chinnappa, Sarvesh [Audatex - Americas] [mailto:
>> sarvesh.chinna...@audatex.com]
>> Sent: Monday, March 18, 2013 6:58 PM
>> To: General discuss
gt; To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] ProductFeature registry entry.
>
> I was afraid you were going to say that, I am actually in the process of
> trying to distribute components across features since reducing them is not
> a
al Message-
From: Chinnappa, Sarvesh [Audatex - Americas]
[mailto:sarvesh.chinna...@audatex.com]
Sent: Monday, March 18, 2013 6:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] ProductFeature registry entry.
I was afraid you were going to say that, I am a
I was afraid you were going to say that, I am actually in the process of
trying to distribute components across features since reducing them is not
an option. What is the best practice in this scenario? The number of
components is rather large and this would result in a lot of registry
write operat
Its the Feature Component mapping. Reduce the number of Components to
succeed. You can also try to distrbute the Components across more Features
but that only works to a certain degree.
On Mon, Mar 18, 2013 at 3:42 PM, Chinnappa, Sarvesh [Audatex - Americas] <
sarvesh.chinna...@audatex.com> wrote
Hi,
I am facing an unusual problem with my installer. I will try explain in detail,
may be there is a workaround for this issue.
1. The installer is rather large >5GB with a lot of files, mostly data files
used by the application (a separate installer)
2. I am using heat to harvest the fi
6 matches
Mail list logo
