Hi all,

I am creating an installer test application which uses SetExternalUI to run
the installer silently, processing all the messages it fires in the
background.

I am starting the install using Session.DoAction("INSTALL");

what I would like to be able to do is examine the Session properties before
and after each custom action fires.

Is this approach a valid one? Is it even possible to look at the session
properties between each action?
How do other people approach testing their Custom Actions and installers in
general?

Basically I started looking into this area after seeing this post:

http://n2.nabble.com/How-do-I-execute-deferred-CAs-(for-unit-testing-custom-actions)--td692162.html
http://n2.nabble.com/How-do-I-execute-deferred-CAs-(for-unit-testing-custom-actions)--td692162.html
 

I decided to follow John Nannenga's approach. However, I am a little unclear
by what he means by 'pausing the installation to perform unit tests'..
Obviously the installation will pause if you put a break point in using
MmsiBreak on a certain action, but how do you actually 'get into' that part
of the process and examine it in an automated way?

I am still relatively inexperienced with .NET in general, so if anyone can
point me in the right direction I'd be very appreciative!

Thanks
Lewis
-- 
View this message in context: 
http://n2.nabble.com/Accessing-session-object-BETWEEN-custom-Actions-tp2868591p2868591.html
Sent from the wix-devs mailing list archive at Nabble.com.


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs

Reply via email to