I recently made some changes to installer code, and now it doesn't install
properly. Investigations show that if I install without /qn option at command
line, everything works as expected. If installed with /qn option (which also
requires installer to run as admin), the variable INSTALLFOLDER mysteriously
becomes null in my custom action. In my custom action, I have:
string oldString = session["INSTALLFOLDER"];
session.Log("string value = {0}, oldString);
and it's invoked right after CostInitialize (non-deferred) stage. Log shows
that oldString has a value of null, but log also shows that INSTALLFOLDER is
set correctly elsewhere.
If I don't use /qn option, then oldstring has correct value. I'm guessing that
/qn somehow corrupts the memory, but not sure how at the moment.
I will try to back out my changes to try and isolate this, but has anyone else
seen anything like this?
Thanks,
George
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
