I see what the three means but that doesn't change the fact that the
install fails when the custom action is fired. I figured this would be
so simple someone could just answer it for me. Should I use Orca to
figure out the error? I haven't installed it yet because other than the
my installer
On 24/11/2011 02:45, Michael Janulaitis wrote:
> What does '=3' mean?
See
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012%28v=vs.85%29.aspx
--
Bruce Cran
--
All the data continuously generated in your
I added the following to my custom action and my install failed:
$cbsmui=3
On 11/23/2011 12:43 PM, jhennessey wrote:
> You should condition the CA based upon the installation state of the
> component containing your EXE. Check
> http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012%28
What does '=3' mean?
On 11/23/2011 12:43 PM, jhennessey wrote:
> You should condition the CA based upon the installation state of the
> component containing your EXE. Check
> http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012%28v=vs.85%29.aspx
> MSDN for full details but let's say y
You should condition the CA based upon the installation state of the
component containing your EXE. Check
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012%28v=vs.85%29.aspx
MSDN for full details but let's say your component id is
"componentA"...then the condition on your CA would
I have a feature which installs my UI exe. At the end of the install a
CA launches the exe. Earlier in the install the user is offered the
option to not install the UI exe. In this case, I don't want to call
the CA. How do I add the condition?
--
6 matches
Mail list logo