Re: Starting a new process after process.close() - C# Discussion Boards

6-Sep-09 5:14

Hi All,

I have a c# winforms application.
I want to give the relogin feature with a full logout and
relogin again.

so I need to start a process after I close the current process.

Today I implement this code:

<br />
Process process = Process.GetCurrentProcess();<br />
<br />
process.Close();<br />
<br />
Process reloginProcess = new Process();<br />
<br />
reloginProcess.StartInfo.Arguments = string.Format("{0} {1}", _userName, _password);<br />
<br />
reloginProcess.StartInfo.FileName = AppDomain.CurrentDomain.BaseDirectory + @"g2gg2.exe";<br />
<br />
// call start process<br />
reloginProcess.Start();<br />
<br />

In some stations(all win xp) I get exception, I think its because the first process fail to close.

Do you have a better way to start the second process (File + Arguments )

Thanks!!!
Ronen

OriginalGriff6-Sep-09 6:03

OriginalGriff

6-Sep-09 6:03

I think it would be a good idea if you read up on what a process is. And then changed your plan somewhat.

Member 3722261 wrote:
Process process = Process.GetCurrentProcess();

process.Close();

Process reloginProcess = new Process();

Doesn't this strike you as at all unlikely to work?
What happens when you stop the current process?
What should execute any further instruction when the process which is executing the instructions is no longer running?

Please, do not go near any buttons marked "Do not, under any circumstances, and I mean any circumstances, press this button. I mean it. The world will end if this button is pressed. So don't press this button." - you strike me as the kind of person who views that as a challenge... Laugh | :laugh:

No trees were harmed in the sending of this message; however, a significant number of electrons were slightly inconvenienced.

This message is made of fully recyclable Zeros and Ones

Member 37222616-Sep-09 19:15

6-Sep-09 19:15

Thanks! or something...

So what is the best implementation to start a new process at the
end of the current one?

Thanks again.
Ronen

OriginalGriff6-Sep-09 21:36

OriginalGriff

6-Sep-09 21:36

Member 3722261 wrote:
what is the best implementation to start a new process at the end of the current one?

Did you find out what a process is?
What happens when you stop the current process?
I'll give you a hint: In the previous question, replace "stop" with "saw off" and "current process" with "branch you are sitting on".

Re-think what you are trying to do. Stopping a process (particularly the current one) is not a solution to your problem, it is a whole new world of pain all of it's own. Think about what you are trying to achieve, and how you would do it in the real world - ignore computers. If you want to read a different book, you don't start by burning down the library to get rid of the previous one, do you?

No trees were harmed in the sending of this message; however, a significant number of electrons were slightly inconvenienced.

This message is made of fully recyclable Zeros and Ones

Member 37222616-Sep-09 23:24

6-Sep-09 23:24

I guess I dont know much about process as you... but still!!!!!

Thanks for your help!

Member 37222616-Sep-09 23:41

6-Sep-09 23:41

OriginalGriff,

I'm using close not Kill.
Close - Frees all the resources that are associated with this component.

so what is so wrong by opening a new process as the last action of current process. I dont think its like your library folk tale .

Thanks!

OriginalGriff6-Sep-09 23:52

OriginalGriff

6-Sep-09 23:52

Kill is intended for non-gui processes, and for abnormal termination. See documentation[^]
Close[^] does much the same thing (normally after CloseMainWindow) but does not loose resources.
You still cannot close or kill your own process! You can restart it, but if you close or kill it it stops existing.

No trees were harmed in the sending of this message; however, a significant number of electrons were slightly inconvenienced.

This message is made of fully recyclable Zeros and Ones

Member 37222617-Sep-09 0:09

7-Sep-09 0:09

You can restart it, but if you close or kill it it stops existing. <br />

You will be amazed by the things you can do after calling currentProcess.close().

Check it out...

Thanks!

Alan N6-Sep-09 22:16

Alan N

6-Sep-09 22:16

Hi,
I think System.Windows.Forms.Application.Restart() is what you are looking for. The docs explain the intended usage.

Alan.

Member 37222616-Sep-09 23:26

6-Sep-09 23:26

Hi,

but I think that Application.Restart wont help me because my process has alot of static "junk" that I want to clear. that the reason I need to start a new process.

Am I right?

Thnaks!

Alan N7-Sep-09 3:45

Alan N

7-Sep-09 3:45

Hi,
I've no idea what you mean by static junk. Please clarify.

Alan.

Member 37222617-Sep-09 9:56

7-Sep-09 9:56

Hi,

Static members on some objects.
Static cntor
...

All static belong to the process so my Q is if all will initialize again?

Thnaks!
Ronen

Alan N7-Sep-09 10:59

Alan N

7-Sep-09 10:59

Hi,
Yes, it would do that as it terminates the old process and starts a new instance.

Alan.

Using Code in a DLL

Bram van Kampen6-Sep-09 4:27

Bram van Kampen

6-Sep-09 4:27

Hi,

Is it possible to call a function from an external DLL from C#.NET code. If needed I would use LoadLibrary and GetProcAddress. It would be better if it could be linked at Program Loading.

Regards Smile | :)

Bram van Kampen

Eric Haddan6-Sep-09 4:37

Eric Haddan

6-Sep-09 4:37

You would want to P/Invoke
http://msdn.microsoft.com/en-us/magazine/cc164123.aspx[^]

Bram van Kampen6-Sep-09 5:29

Bram van Kampen

6-Sep-09 5:29

Thanks, that is much help. What is not entirely clear is, Where does the C# app look for the DLL. On the Server, or on the Remote Machine. I would require it to look for it on the server. The DLL I have in mind produces a Datablock in a buffer provided by the C# code. The C# Code will not have an understanding of the contents, All it will have to do with it is to store it in an SQL Database held on the server.

Regards, Smile | :)

Bram van Kampen

Eric Haddan6-Sep-09 6:48

Eric Haddan

6-Sep-09 6:48

You can try adding the path of the dll. I'm not totally sure if that works.