Click here to Skip to main content
15,390,470 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
When i try to run my application on a test OS, i always get an error with the error signatures saying mscorlib and xamlparse. Does anyone have any idea why im getting this?

Here is the full report:

Problem signature:
   Problem Event Name: CLR20r3
   Problem Signature 01: bodyflex.exe
   Problem Signature 02:
   Problem Signature 03: 5275afa2
   Problem Signature 04: mscorlib
   Problem Signature 05: 4.0.30319.17929
   Problem Signature 06: 4ffa561c
   Problem Signature 07: 43c4
   Problem Signature 08: 105
   Problem Signature 09: System.Windows.Markup.XamlParse
   OS Version: 6.1.7600.
   Locale ID: 2057
   Additional Information 1: 0a9e
   Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
   Additional Information 3: 0a9e
   Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

 Read our privacy statement online:

 If the online privacy statement is not available, please read our privacy statement offline:

Its developed on a windows 7 x64 machine, intended to run on a vista or 7 machine, 32 or 64 bit is unknown. Its in C#, and is a customer management program using a database created in SQL Server compact
I would say, not enough information. You should do testing on some different machines, create some logs and study them.
brucey_D 3-Nov-13 12:58pm
I have done, and it keeps coming up with the same error when I start it. have tried it on xp, vista and 7
Well, add more detail to the logs. Honestly, if you don't get more information, hard to come up with something...
tgrt 3-Nov-13 14:59pm
You need to catch the unhandled exception that is being reported, so that you can get more information.
Richard MacCutchan 4-Nov-13 4:37am
The first thing you need to do is to find out exactly where this occurs and show us the offending lines of code.
cigwork 5-Nov-13 16:51pm
Have you tried:
0 - Checking that the target machine has a version of the .Net framework that matches or supersedes the one on your dev. machine?

1 - Building a single "hello world" window/page WPF app and seeing if that will run on a test machine? If it doesn't then you can _probably_ rule out problems in the main app.

If "hello world" runs then have you considered:

2 - Replacing the initial start view/page with a simple "It Lives" with no/minimal property bindings and no additional namespace references?

3 - Checking that any DLLs required/used in the failing start page/window are actually built/installed on the test machine?

4 - Tracing the startup sequence in the Windows Application event log?
Francisco T. Chavez 13-Nov-13 6:44am
I like this one. I think cigwork should move it to the solution section so that I can give it a 4 or 5 star rating.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900