Paul,
I tried what you suggested with the debugger and the
automation application terminates immediately even if the
debugger is stopped at a break point on the next line.
For example I added the following code directly after the
application is started:
Thread.Sleep(10000);
When the debugger hits this line the app has already
shutdown, but the variable is still in scope (as I can see
it in the watch & locals window).
Mike
>-----Original Message-----
>
[quoted text clipped - 14 lines]
>Microsoft MVP (Visual Basic)
>.
Paul Clement - 06 Jan 2004 14:00 GMT
¤ Paul,
¤ I tried what you suggested with the debugger and the
¤ automation application terminates immediately even if the
¤ debugger is stopped at a break point on the next line.
¤ For example I added the following code directly after the
¤ application is started:
¤
¤ Thread.Sleep(10000);
¤
¤ When the debugger hits this line the app has already
¤ shutdown, but the variable is still in scope (as I can see
¤ it in the watch & locals window).
¤ Mike
Well this is new to me. Typically the problem is that the automation server won't shut down. ;-)
I have one other idea you may want to try. Can you use Process.Start to launch your automation
server and then use GetObject to set a variable instance to that object for automation?
I don't know much about your automation server (custom? third-party?) but I'm wondering whether it's
looking for something that's being provided by Visual Basic or your Visual Basic application and not
by VB.NET.
Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)