By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,294 Members | 1,568 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,294 IT Pros & Developers. It's quick & easy.

Launching one c# application from another

P: n/a

Excuse the novice aspects of this question, but:

What techniques are available to me for launching one c# application (
console .exe) from another?

For example, I know there is the Process and ProcessInfo classes, but
these seem designed for launching non-CLR applications.

Should I access the .exe as a reference?

Or dynamically invoke it, or just invoke its methods?

Should I use Reflection?

Is there a way to "launch" it so that once its running, it's entirely
detached from the calling application?

Is that what Reflection.Emit is for?

Is there a proper way to load a new Application space for a second
application, and is this the way to do what I am asking?

Can you direct me to any good references on the topic...I've been
Googling all weekend and everything seems to talk about launching a DOS
application (using Process) not about a c# app launching another c#?
--
RSS Feed/Incognito Blog
http://blog.360.yahoo.com/rss-siXzkM...bTlKkOL5SWLA--
Jan 16 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a

Maybe this answers my question, or part of it(?):

http://msdn.microsoft.com/library/de...emblyTopic.asp
class Test {
public static void Main() {
AppDomain currentDomain = AppDomain.CurrentDomain;
AppDomain otherDomain = AppDomain.CreateDomain("otherDomain");

currentDomain.ExecuteAssembly("MyExecutable.exe");
// Prints "MyExecutable running on [default]"

otherDomain.ExecuteAssembly("MyExecutable.exe");
// Prints "MyExecutable running on otherDomain"
}
}
John A. Bailo wrote:

Excuse the novice aspects of this question, but:

What techniques are available to me for launching one c# application (
console .exe) from another?

For example, I know there is the Process and ProcessInfo classes, but
these seem designed for launching non-CLR applications.

Should I access the .exe as a reference?

Or dynamically invoke it, or just invoke its methods?

Should I use Reflection?

Is there a way to "launch" it so that once its running, it's entirely
detached from the calling application?

Is that what Reflection.Emit is for?

Is there a proper way to load a new Application space for a second
application, and is this the way to do what I am asking?

Can you direct me to any good references on the topic...I've been
Googling all weekend and everything seems to talk about launching a DOS
application (using Process) not about a c# app launching another c#?

--
RSS Feed/Incognito Blog
http://blog.360.yahoo.com/rss-siXzkM...bTlKkOL5SWLA--
Jan 17 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.