Debugger disappear after exiting winform application

Question

1.00/5 (1 vote)

See more:

Dear All,

I have create winform application using c#. Where i'm blocking some application(like: mspaint.exe, notepad.exe, etc...) while running this winform-application.

I debug and run the application, performmed all task. And exit the application. But, still the application is running under the process(displaying in Task-Manager).

And the debugger in VS-2013 was disappeared but stopped.

What I have tried:

How can i search, where the debugger is or/and why it is disappeared.

can any one please help me.

Thanks in advance...

Posted 18-Jun-17 0:33am

abdul subhan mohammed

Updated 18-Jun-17 4:20am

v2

Add a Solution

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)

Dave Kreskowiak · Answer 1 · 2017-06-18T04:20:00

You question doesn't make sense. If the process being debugged terminates, the debugging session also terminates. It didn't "go anywhere" and there is only one reason why "it disappeared", the process being debugged ended.

Also, the point behind writing an application that "blocks" other processes from running is a moot point. First, your code is not preventing the process from launching. It's terminating the process after the fact. AND, Windows also has this functionality built it with policies, actually preventing the identified executables from even launching at all.