Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How do you debug a XamlParseException?

I'm trying to use a 3rd party component in my Silverlight application and when I try to create an instance of the control, I get a XamlParseException:

{System.Windows.Markup.XamlParseException: **Set property 'System.Windows.FrameworkElement.Style' threw an exception.** [Line: 0 Position: 0] 
---> System.Windows.Markup.XamlParseException: **Elements in the same ResourceDictionary cannot have the same x:Key** [Line: 1739 Position: 47]    
at MS.Internal.XcpImports.CreateFromXaml(UnmanagedMemoryStream stream, String sourceAssemblyName, boolean createNamescope, Boolean requireDefaultNamespace, Boolean allowEventHandlers)    
at System.Windows.Controls.Control.GetBuiltInStyle(IntPtr nativeTarget, IntPtr& nativeStyle)    
--- End of inner exception stack trace ---    
at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)    
at SpellCheckerSample.StandardSpellDialog.InitializeComponent()    
at SpellCheckerSample.StandardSpellDialog..ctor()}

How can I debug this? How do I know what file line 1739, Position 47 is in?

like image 999
Craig Shearer Avatar asked May 21 '10 02:05

Craig Shearer


2 Answers

Could be a bit of a bugger to find. Basically try to gather as many details as possible from the debugger.

  1. Set the debugger to break on XamlParseException.
  2. Have a look at the callstack. It could be possible that the offending control's constructor is on the callstack.
  3. When paused go to the Locals debug window to see if any parameters to the function reveal more about which component this is.
  4. If not double-click the next stack entry down and go to step 3.
  5. Repeat steps 3 and 4.

After I wrote this I realised that the control's constructor is indeed on the callstack and it is SpellCheckerSample. Very likely it is .XAML page for that control. If you can get access to the source, the file name is most likely something like SpellCheckerSample.xaml.

The error itself is pretty straight forward, looks like there multiple things defined with the same key in the same ResourceDictionary. The below code will cause this to happen:

<Window.Resources>
  <myConverters:BananaToCarrotConverter x:Key="StupidestConverterEver" />
  <myConverters:BananaToAppleConverter x:Key="StupidestConverterEver" />
<Window.Resources>
like image 96
Igor Zevaka Avatar answered Nov 20 '22 15:11

Igor Zevaka


Turns out my specific problem was that the ComponentOne component only works under Silverlight 4. Once I changed to target SL4 it all worked.

like image 2
Craig Shearer Avatar answered Nov 20 '22 15:11

Craig Shearer