Home Dashboard Directory Help
Search

Type 'System.Windows.Markup.XamlParseException' in assembly 'System.Windows, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' is not marked as serializable. by dsandor


Status: 

Resolved
 as By Design Help for as By Design


3
0
Sign in
to vote
Type: Bug
ID: 499458
Opened: 10/22/2009 7:06:37 AM
Access Restriction: Public
0
Workaround(s)
view
2
User(s) can reproduce this bug

Description

See images for evidence. Simple XAML file. Worked find until I tweaked the button margins, then the designer stopped rendering with the error below. I can open the XAML in Blend 3 without a problem and the app compiles and runs fine.
Details
Sign in to post a comment.
Posted by Andy J Meyers on 2/22/2012 at 8:03 AM
I had version System.Windows.Interactivity.dll in my gac. Once I removed it everything worked fine.
Posted by Ewart on 1/17/2010 at 1:09 AM
I have the same problem also - would be great if there could be more of a stack trace or something to help determine the root cause.
Posted by Microsoft on 12/9/2009 at 8:45 AM
Cumars3,

The problem that we have corrected is the way the error is being reported to the developer.

If you are seeing this error now, you can find the problem by opening the UserControls that are in the XAML file that you can't load in the designer. One of the other UserControls has an error that is not be reported correctly. For example, we have seen animations that have type'os in the target name that causes this.

We have also seen cases of VisualStates being set on controls that are not in the UserControl.

We are sorry you run into this problem and hope the above information helps you locate the XAML error that is causing the problem.

Visual Studio Product Team
Posted by Microsoft on 12/9/2009 at 8:44 AM
Cumars3,

The problem that we have corrected is the way the error is being reported to the developer.

If you are seeing this error now, you can find the problem by opening the UserControls that are in the XAML file that you can't load in the designer. One of the other UserControls has an error that is not be reported correctly. For example, we have seen animations that have type'os in the target name that causes this.

We have also seen cases of VisualStates being set on controls that are not in the UserControl.

We are sorry you run into this problem and hope the above information helps you locate the XAML error that is causing the problem.

Visual Studio Product Team
Posted by cumars on 12/8/2009 at 5:01 PM
Is there a workaraud? What is causing this error? I have the same problem!
Posted by Microsoft on 10/27/2009 at 5:40 PM
dsandor,

We have duplicated your issue and are working on this. It is currently being tracked in another work item.

I'm closing this issue for now and this fix will be in a future version of Visual Studio.

Thank you again for reporting this issue.

Visual Studio Product Team
Posted by Microsoft on 10/27/2009 at 10:15 AM
dsandor,

Sorry you are having a problem with your control.

Do you have a repro that does not involve an Infragistics control?

If not, please contact Infragistics Support and explain the problem you are having with their control.

Please let us know if you have a repro that does not use a 3rd party control.

Have a great day,

Visual Studio Product Team
Posted by Microsoft on 10/27/2009 at 10:15 AM
dsandor,

Sorry you are having a problem with your control.

Do you have a repro that does not involve an Infragistics control?

If not, please contact Infragistics Support and explain the problem you are having with their control.

Please let us know if you have a repro that does not use a 3rd party control.

Have a great day,

Visual Studio Product Team
Posted by Microsoft on 10/27/2009 at 10:14 AM
dsandor,

Sorry you are having a problem with your control.

Do you have a repro that does not involve an Infragistics control?

If not, please contact Infragistics Support and explain the problem you are having with their control.

Have a great day,

Visual Studio Product Team
Posted by Microsoft on 10/27/2009 at 10:14 AM
dsandor,

Sorry you are having a problem with your control.

Do you have a repro that does not involve an Infragistics control?

If not, please contact Infragistics Support and explain the problem you are having with their control.

Please let us know if you have a repro that does not use a 3rd party control.

Have a great day,

Visual Studio Product Team
Posted by Microsoft on 10/27/2009 at 10:13 AM
dsandor,

Sorry you are having a problem with your control.

Do you have a repro that does not involve an Infragistics control?

If not, please contact Infragistics Support and explain the problem you are having with their control.

Please let us know if you have a repro that does not use a 3rd party control.

Have a great day,

Visual Studio Product Team
Posted by Microsoft on 10/27/2009 at 10:12 AM
dsandor,

Sorry you are having a problem with your control.

Do you have a repro that does not involve an Infragistics control?

If not, please contact Infragistics Support and explain the problem you are having with their control.

Please let us know if you have a repro that does not use a 3rd party control.

Have a great day,

Visual Studio Product Team
Posted by Microsoft on 10/27/2009 at 4:16 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you
Posted by Microsoft on 10/25/2009 at 8:29 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted.
Posted by Microsoft on 10/25/2009 at 8:29 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted.
Posted by Microsoft on 10/25/2009 at 8:29 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted.
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
vs2010-2.PNG (restricted) 10/22/2009 -
vs2010.PNG (restricted) 10/22/2009 -
AdminMain.xaml (restricted) 10/22/2009 -