[App-name] has encountered a problem and needs to close. We...

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi

Under what circumstances do this dialog box apper in a .Net 2.0 application?
I have never noticed this dialog box before I installed the KB924895 fix for
..Net framework 2.0.
 
Hello Daniel,

Which behavior leads to this dialog box?
Do u have the latest updates installed?

DC> Under what circumstances do this dialog box apper in a .Net 2.0
DC> application? I have never noticed this dialog box before I installed
DC> the KB924895 fix for .Net framework 2.0.

---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangel
 
Daniel,

This is at least the 2nd time you've asked this question - someone tried
helping you the last time you asked and you've not bothered to reply to
them. Basically I'd say that something in your code (again, I'm guessing
that this is a program that you've written) is doing something unexpected
and quitting. You need to run the program in the debugger and find out
where, at which point people will be able to help you further.

Regards,

- Paul.
 
What does the debugger say?

It's very easy to crach an application - .Net or no .Net.

Here's how:

int divisor = 0;

int result = 5 / divisor;


Voila, it'll crash.

Ashot
 
Daniel Carlson said:
Under what circumstances do this dialog box apper in a .Net 2.0
application?
I have never noticed this dialog box before I installed the KB924895 fix
for
.Net framework 2.0.
Click to expand...

This typically means you've got an unhandled exception. It's meant that
since the earliest days of .Net development.

Put an event on the AppDomain.UnhandledException and see if it hits.
Alternativly, attach a debugger and see the exception.

This is actually the behavior you WANT to have happen, so that you can track
things down.
 
Chris Mullins said:
This typically means you've got an unhandled exception. It's meant that
since the earliest days of .Net development.

Put an event on the AppDomain.UnhandledException and see if it hits.
Alternativly, attach a debugger and see the exception.

This is actually the behavior you WANT to have happen, so that you can track
things down.
Click to expand...

Hello Chris!

I have an event handler connected to AppDomain.UnhandledException but this
is never trigged. Is this a guarantee that no unhandled exception is thrown?

Another thing: I have built two diferent test applications, one in Fw1.1 and
one in Fw2.0, that throws an unhandled exception. the one bulit in 1.1 does
only show a dialog saying: "An unhandled exception has occ..." and the one
bulit in 2.0 generates the dialog this thread is all about.

The difference between the dialog that my test application generates is that
this one has generated an "error report". Mine does not...!

Thanks for you reply!

Regards Daniel Carlson
 
That's not the exception you wanted to see.

Along with "Out of Memory", "Thread Abort" and "Stack Overflow" exceptions,
that's one that you really can't do much about.

I would suggest using ADPlus to capture the exception, and then poke at the
resulting dump file. That should tell you quite a bit more about what's
going on. Information on how to do (most) of this can be found at:
http://www.coversant.net/Default.aspx?tabid=88&EntryID=28

I added the "debugging" group to this post, as that's where it's going to
end up.
 
Back
Top