Application has stopped working when running outside of visual studio.

Question

3.00/5 (2 votes)

See more:

Hi Guys,

I have a bit of an odd scenario and was wondering if you could shed any light on it.
I've written a WPF application that works as a data importer. It uses the MVVM approach and works very nicely.

During development I have implemented try catch's for error handling which catch errors that occur and should display them into the activity log within the application.

The oddness is this:

When the application is running from within Visual Studio, the try catch's are catching errors with no problem. Reading the error message(s) and displaying them to the user as I would expect.
However, when I compile the program and run it on its own by executing the exe file, when the error(s) occur, instead of handling them nicely and cleanly I get a ### has stopped working where ### is the name of the application. It attempts to look for solutions but never succeeds.

Why would my try catches not be working in compiled exe when not run from within visual studio?

Thanks in advance.

Posted 24-Feb-14 4:48am

Pheonyx

Add a Solution

Comments

govardhan4u 24-Feb-14 11:29am

Have a look on the below article once, if it is useful

http://www.codeproject.com/Articles/90866/Unhandled-Exception-Handler-For-WPF-Applications.aspx

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 · Accepted Answer · 2014-02-24T05:42:00

It's not that your existing try/catch blocks are not catching the new error. It's the you don't have a try/catch block around the code that is causing the new error. Something in your code is making as assumption that is no longer valid when running outside of the project environment.

I would suggest reading this[^] and, as another example of the technique, this[^].