Why don't run WPF App on XP

Question

1.00/5 (4 votes)

See more:

, +

Hi guys,

I create a simple window in wpf by VS2010, .net framework 3.5, c# and I run it to win7 x86 that result was mainWindow [^], but I try that's it on XP 32bit by this properties XP pro [^]and result was crash app err1 [^], err2 [^], I also install .net framework packages, DirectX, windows installer and so on... but didn't run!
Where is the problem? Is there a solution?
If was necessary more info about this issue, please tell me.

Thanks in advance

and Viva! Quds Day [^]

Posted 14-Aug-12 9:28am

hzawary

Add a Solution

Comments

Sergey Alexandrovich Kryukov 14-Aug-12 15:35pm

Sorry, your information is insufficient to discuss this problem. You need to check up many things, but you do have your code, we don't.
--SA

hzawary 14-Aug-12 15:43pm

Is necessary the code? but tell us in the image of 'err2' about system.window.markup.xamlparse

Sergey Alexandrovich Kryukov 14-Aug-12 15:54pm

At least you would need to catch all exceptions on top of every thread and provides us with real exception information. The error information you show is pretty much useless, taken too late.
--SA

[no name] 14-Aug-12 15:38pm

Just for your information, I know that it real convenient to take a screenshot and post it somewhere but not everyone has access to the pictures. For instance, I can't see the pictures so I do not know what the errors are and I cannot help you. And people searching for this same question in the future might not have access to the pictures.

hzawary 14-Aug-12 15:47pm

So I can upload the images where?

[no name] 14-Aug-12 15:52pm

It does not matter where, I will still not have access to them. What happens when where ever your upload them to deletes them? Or changes domains? Gets sold? Goes bankrupt?

Sergey Alexandrovich Kryukov 14-Aug-12 15:56pm

In this very case, error information is majorly textual, OP could copy it and provide in the question in a text form. But this is pretty much useless. I explained the importance of providing exception dump.
--SA

[no name] 14-Aug-12 15:58pm

Agreed. I do not think he understands what I am telling him.

Sergey Alexandrovich Kryukov 14-Aug-12 16:00pm

Let's just tell him: no, we do not need those images at all. They are not informative.
--SA

hzawary 14-Aug-12 16:08pm

Yes! I understand your goal, But I haven't energy (pep) to explain, sorry! So I will improve my question later:)

Christian Amado 14-Aug-12 16:10pm

What are you talking about? @hzawary Come on! Write a little, images isn't needed here. You can copy/paste error log if you don't want to write.

hzawary 14-Aug-12 16:15pm

So thanks and agree with you, now! I'm tired, improve it later:)

Christian Amado 14-Aug-12 16:16pm

We'll here for help ;)

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)

Philip Stuyck · Accepted Answer · 2012-08-14T11:29:00

To debug this a little better and get proper information add an eventhandler to the app.xaml like in this example

XML

<application x:class="interMASTER.App" xmlns:x="#unknown">
             xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
             xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
             xmlns:vm="clr-namespace:InterstoneViewModel;assembly=InterstoneViewModel"
             StartupUri="MainWindow.xaml" DispatcherUnhandledException="Application_DispatcherUnhandledException">
    <application.resources>
		<!-- Resources scoped at the Application level should be defined here. -->
        
        
        
    </application.resources>
</application>

Then in the partial class App.xaml.cs do this :

C#

public partial class App : Application
    {
        private void Application_DispatcherUnhandledException(object sender, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs e)
        {
            MessageBox.Show(e.Exception.Message+" "+e.Exception.StackTrace);
        }
    }

This way a nice dialog will appear when something is wrong and post that informaton iso those nasty bitmaps.