Does an Application ever fully close in .NET??

[Ebrahim]

I have made several applications (not all are done yet) using the .NET
framework but none of them seem to close well with the
Application.Exi t function. I use Windows.XP so when i do a Processes
check they still remain in memmory after the function has been called
?
Since they are still bieng read from the .NET env it doesnt matter
much , but if i run the EXE file then there is no way to actually exit
the Application unless I end it manually from the Task Manager.
Does any one have a remedy for this??

[Jon Skeet [C# MVP]]

Ebrahim <eb************ ****@hotmail.co m> wrote:

I have made several applications (not all are done yet) using the .NET
framework but none of them seem to close well with the
Application.Exi t function. I use Windows.XP so when i do a Processes
check they still remain in memmory after the function has been called
?
Since they are still bieng read from the .NET env it doesnt matter
much , but if i run the EXE file then there is no way to actually exit
the Application unless I end it manually from the Task Manager.
Does any one have a remedy for this??

Could you post a short but complete example which demonstrates the
problem? It usually occurs if you have some foreground threads still
running which you don't really want to be running any more.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Michael A. Covington]

Curious. I have not observed this problem.

I assume these are windowed applications that include Application.Run () to
start the action and Application.Exi t() to end it.

Technically, Application.Exi t() ends the message loop which is started by
Application.Run (). Execution then proceeds from Application.Run () to the
end of the program.

"Ebrahim" <eb************ ****@hotmail.co m> wrote in message
news:c5******** *************** **@posting.goog le.com...

I have made several applications (not all are done yet) using the .NET
framework but none of them seem to close well with the
Application.Exi t function. I use Windows.XP so when i do a Processes
check they still remain in memmory after the function has been called
?
Since they are still bieng read from the .NET env it doesnt matter
much , but if i run the EXE file then there is no way to actually exit
the Application unless I end it manually from the Task Manager.
Does any one have a remedy for this??

[Leon Lambert]

Only time i have notice this is when i have other threads still running.
My solution was to follow a ShutDown pattern for all my threads. As part
of the shutdown of any given thread it calls the shutdown method on any
child thread they may have spawned. Do a google search to find out more
about shutdown patterns.

Hope this helps
Leon Lambert

Ebrahim wrote:

I have made several applications (not all are done yet) using the .NET
framework but none of them seem to close well with the
Application.Exi t function. I use Windows.XP so when i do a Processes
check they still remain in memmory after the function has been called
?
Since they are still bieng read from the .NET env it doesnt matter
much , but if i run the EXE file then there is no way to actually exit
the Application unless I end it manually from the Task Manager.
Does any one have a remedy for this??

[Mohamoss]

hi
what prameter do you give the exit function .. try to give it 1 as a
prameter.