c#.net +.exe integration by process function

Question

1.00/5 (1 vote)

See more:

.NET3.0

hi..

I have a very simple problem tht needs attention. I have 2 .net projects pro1, pro2. Now in pro1 I have a menu "connect" where I wish to execute the output of pro2 and I choose the pro2.exe and paste it in the pro1 folder and from pro1 i add reference and I call the .exe by Process.Start("Pro2.exe"). Now its running fine when pro1 is debugged. BUT it only runs for 1 time and for any other time it shows an win32 exception. Or if there is any state change(like if I open a file in the editor of any state change) then its giving exceptions. What may go wrong?

Posted 28-Feb-11 4:17am

Supratik sadhuka

Updated 28-Feb-11 4:21am

#realJSOP

v2

Add a Solution

Comments

#realJSOP 28-Feb-11 10:22am

What exception are you getting? Which application is throwing the exception, Pro1 or Pro2?

Supratik sadhuka 28-Feb-11 10:31am

"Win32Exception: The system cannot find the file specified"
the debugging thing shows error on the line

private void ReceivefilemenuItem3_Click(object sender, EventArgs e)
{
Process myProc;
myProc = Process.Start("pro2.exe");<-------this line is showing the error

}

Sergey Alexandrovich Kryukov 28-Feb-11 10:56am

More detail, please. See my answer. Are you able to run second instance manually (through Shell) when first instance run from pro2.exe is already running?
Please explain why and how are you doing that.
--SA

Supratik sadhuka 28-Feb-11 11:11am

Thnx for your answere and your interest in my question...
See its like i have 2 projects and i want to integrate them like the when i click on a menu in a form of project1 i am directed to a form of project 2..this is what i want to do actualy...

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2011-02-28T04:53:00

It seems to me the major problem is running the second instance of the process started by running pro2.exe. There can be many reasons for that as you did not provide enough detail, but this is very usual, especially when you try to organize inter-process communication between processes: many ways of doing that imply uniqueness of one of the participating process.

For experimental purpose, try to terminate first instance — you have access to the instance of the started Process returned by Process.Start, so you can use Process.Kill.

I cannot tell you how to "fix" this problem, because this is not a problem unless you share the purpose of all this activity. What you're trying to do is very weird and usually are not done at all. If you want to have a host process which is able to "run" dynamically code of other .NET assemblies playing the role of plug-ins or "applications" using their executable files, you're not using right way. You don't have to run then in different process. You can run them in the same process (albeit possibly in a separate thread) if you load assembly dynamically using System.Reflection.Assembly. If you need to do in more than once, you should load it in a new Application Domain (see System.AppDomain), because you can unload AppDomain, but there is no a way to unload assembly from the process. Again, I'll no more exactly what to do, is you explain your purpose in detail.

Sorry if this did not answer your question. In this case, you need to provide more information. Please show the code of starting the process and getting its "output" (as well as all other ways you're trying to use to communicate between processes). Catch exception you got, make a full dump (including its stack and all inner exceptions, recursively), save the dump in file and post in in your question.

Important! Do not post your follow-up information as Answer. Use "Improve question" or "Add comment" instead.

—SA