has stopped working windows is checking for a solution to the problem

Question

Hi there,

I have WPF app installed on my machine.. everytime i close the app, it yields "[applicationName] has stopped working. windows is checking for a solution to the problem.. " and after few seconds the message gone.. can anyone please explain what would cause this? i was trying to dispose all the managed resources but still no luck..

Answer 1

Hi,

Are you running your WPF application on windows vista machine?

Answer 2

no.. windows 7 professional

Answer 3

Hi,

I think in Windows Vista/ Window 7, when a .NET executable hit an unhandled exception, it shows like "...has stopped working. Windows is checking for a solution." instead of showing the exception message like in Windows XP.

May be there is some unhandled exception when you close the WPF window.

Please go through the following link

http://bytes.com/topic/c-sharp/answers/830409-error-messages-unhandled-exceptions

You may have to write DispatcherUnhandledException in the application (App.xaml.cs) to know more information about the exception.

regards,

Vimal

---

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

 

 

Answer 4

i have implemented the DispatcherUnhandledException.. However the error always occurs while closing the application so i think it does not have a chance to trigger the DispatcherUnhandledException event.

Answer 5

ok. But make sure that you run the exe (Release mode) instead of debugging. In the DispatcherUnhandledException event, display the error as message or in a window.

regartds,

Vimal

---

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Answer 6

did you mean the release mode on Visual studio?

Answer 7

when I run in release mode in VS.. the error never comes up.. so wierd..