Seems reasonable.
On Fri, Sep 14, 2012 at 10:57 AM, vchauras wrote:
> Yes, I want a single unified installation. The flow of UI would be
> something
> like:
>
> 1- Welcome
> 2- Ask for user inputs (checkbox, filling some values)
> 3- The user inputs can now be passed to m1 and m2 if they need tha
Yes, I want a single unified installation. The flow of UI would be something
like:
1- Welcome
2- Ask for user inputs (checkbox, filling some values)
3- The user inputs can now be passed to m1 and m2 if they need that specific
info
4- m1 runs with its input
5- m2 runs with its input
6- finish
I wr
Do you want a single unified installation experience for the two MSIs? If
no, then you don't want Burn.
On Thu, Sep 13, 2012 at 3:28 PM, vchauras wrote:
> Hello all,
>
> I want to know if there are any guidelines (best practices) to care about
> before clubbing 2 MSI s together using burn. For
Hello all,
I want to know if there are any guidelines (best practices) to care about
before clubbing 2 MSI s together using burn. For e.g. I have m1 and m2 as
two msi s.
Both the msi have their own LaunchConditions (which may overlap) where they
check before install (like .NET framework version,
4 matches
Mail list logo
