WPF Application exits automatically

Question

0.00/5 (No votes)

See more:

Hi Guys,

I have a problem with WPF Applications. It exits automatically. I am using VS 2010.

Steps :

1. Created new Visual Studio Solution.
2. Added new WPF Project to the solution.

Now when I try to run the application. It exists automatically and does not display any window.

But, when I take a remote connection, It displays window on remote machine.

Why am I not able to show window on simple WPF application with new solution and added new WPF project to it?

It that a problem of thread or what I am not getting it. Please help me out with this problem.

Posted 3-May-11 19:56pm

Sanjay J Patolia

Add a Solution

Comments

Sergey Alexandrovich Kryukov 4-May-11 2:30am

It always works if you follow steps 1, 2. It is not clear what you do.
--SA

Sanjay J Patolia 4-May-11 2:34am

I followed the same specified steps, though it is not working.. I think of Naming Convetion, Threads or few properties to be set. It is not working.

Sergey Alexandrovich Kryukov 4-May-11 2:39am

OK, it means you not just added new WPF project but did something else. What you suggested for the reason of the problem looks very unlikely. What code did you add/change after the project was automatically pre-created for you? Can you post it (keep it minimal, please)?
--SA

Perry Bruins 4-May-11 4:29am

What do you mean by "remote connection"? Default WPF projects do not have any "remote" capabilities

Sanjay J Patolia 4-May-11 4:31am

I am using it on other machine by mstsc, working remotly, accessing my machine from other machine - A typical Windows Xp remote connection facility.

Perry Bruins 4-May-11 4:40am

Can you try running your project in the debugger to see if any errors or exceptions are occurring. If that does not help, can you post a zip file of the solution including the project, so I can see if it occurs on my box too?

Sanjay J Patolia 4-May-11 4:41am

Sure I will upload right a way

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)

Pete O'Hanlon · Accepted Answer · 2011-05-04T01:21:00

It sounds like you have an unhandled exception going on there. In your App.xaml.cs, add an override for OnStartup and add the following line into it:

C#

DispatcherUnhandledException += app_DispatcherUnhandledException;

Then add in the app_DispatcherUnhandledException method:

C#

static void app_DispatcherUnhandledException(object sender, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs e)
{
  // Log/inspect the inspection here
}

Also, check your Output window in Visual Studio. This is an excellent location for identifying issues that cause crashes, invalid bindings, etc.