How to Kill the Application in Mobile device

Question

1.00/5 (3 votes)

See more:

VB

Hi,

Can anyone help me with the code of killing the application on exit.

Thanks in advance.

Posted 23-May-11 0:34am

Saumyavemula

Add a Solution

Comments

Fabio V Silva 23-May-11 7:32am

Which mobile device?

Legor 23-May-11 7:56am

Please improve your question.
Thanks in advance.

Sergey Alexandrovich Kryukov 23-May-11 9:49am

Why killing it? What kind of application, UI library you used (if any).
--SA

Saumyavemula 24-May-11 2:10am

I am exiting application but when application is runned 2nd time and closed that time it is showing an error of Memory full. So i need to kill the application when clciked on exit.

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-05-23T03:57:00

When you successfully exit any application, its process will be terminated, so it should not be killed. There is no such concept as "kill application" for all kinds of application I ever saw. You can only kill the process you're running.

In .NET it's calling System.Diagnostics.Process.GetCurrentProcess.Kill(). If you really need to do it, it means you are in deep trouble — you process keeps hanging after you exit the application (whatever it means; you did not share this information).

On reason for that could be unfinished threads. It does not happen to background threads, so this problem won't appear if you're using the thread pool, but decent application should better correctly exit or abort all threads before exiting from the application. There could be other reasons for hanging the process after exit of the application, often related to 3rd-party code referenced or P/Invoked, due to incorrect clean-up or just a bug. In all such cases, this is the indication of that you're in big trouble.

—SA