Okay, sounds like something to add to the WiX BA.
On Tue, Oct 11, 2011 at 6:35 AM, jhennessey wrote:
> I always grab the binaries (we check them in) but still use the MSI for
> Votive. I have VS2005, VS2008, and VS2010 but only need votive for 2010.
> So,
> I don't install anything but the VS2010
I always grab the binaries (we check them in) but still use the MSI for
Votive. I have VS2005, VS2008, and VS2010 but only need votive for 2010. So,
I don't install anything but the VS2010 integration.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/
What features are you selecting?
On Mon, Oct 10, 2011 at 6:04 PM, jhennessey wrote:
> Is there a way to extract the MSI then?
>
> The problem with providing just the exe right now is that it doesn't
> support
> installing only select features (like the MSI does).
>
> I was thinking that /layout m
Is there a way to extract the MSI then?
The problem with providing just the exe right now is that it doesn't support
installing only select features (like the MSI does).
I was thinking that /layout might work but the WiX BA doesn't support that
switch (not sure if that extracts embedded stuff any
On 08-Oct-11 15:45, John Bergman wrote:
> Is this intentional, or are there issues with these two builds?
Wix36.exe now has the MSI and cabs attached.
--
sig://boB
http://joyofsetup.com/
--
All of the data generated in
Is this intentional, or are there issues with these two builds?
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threat
6 matches
Mail list logo
