Programmatically launching a .NET assembly

[dvestal]

How can I launch a .NET executable (a windows app written in VB.NET)
from within another .NET assembly, and be able to tell when the user
receives control?

I could just kick it off with System.Diagnostics.Process.Start, but it
has a lengthy loading sequence, and I wouldn't know when it was loaded.
So, is it be possible to launch the app and trap the main form's
Activate event? Is there an easier way?

 

[Nicholas Paldino [.NET/C# MVP]]

You would need to have some sort of indication on the program you are
running when it was started up. I would use a named event for this, which
fires when the app is done loading.

Hope this helps.

 

[Guest]

You could use the Reflection namespace, Use the Assembly and type attributes
to set up your external exe ie: Assembly.LoadFrom("path");
Type t = Assembly.GetType("Object.Type");
Then use Activator.CreateInstance
Hope this helps



--
threetoes

You would need to have some sort of indication on the program you are
running when it was started up. I would use a named event for this, which
fires when the app is done loading.

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

How can I launch a .NET executable (a windows app written in VB.NET)
from within another .NET assembly, and be able to tell when the user
receives control?

I could just kick it off with System.Diagnostics.Process.Start, but it
has a lengthy loading sequence, and I wouldn't know when it was loaded.
So, is it be possible to launch the app and trap the main form's
Activate event? Is there an easier way?

 

[Nicholas Paldino [.NET/C# MVP]]

That's not going to work for an executable, and it doesn't address the
issue of knowing when the program reaches a certain point.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

You could use the Reflection namespace, Use the Assembly and type
attributes
to set up your external exe ie: Assembly.LoadFrom("path");
Type t = Assembly.GetType("Object.Type");
Then use Activator.CreateInstance
Hope this helps



--
threetoes

You would need to have some sort of indication on the program you are
running when it was started up. I would use a named event for this,
which
fires when the app is done loading.

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

How can I launch a .NET executable (a windows app written in VB.NET)
from within another .NET assembly, and be able to tell when the user
receives control?

I could just kick it off with System.Diagnostics.Process.Start, but it
has a lengthy loading sequence, and I wouldn't know when it was loaded.
So, is it be possible to launch the app and trap the main form's
Activate event? Is there an easier way?

 

[Crash]

Hi,

Check docs for: Process.WaitForInputIdle()

This function blocks the caller until the target program has
initialized, displayed its main window, and is ready to process
messages...