416.467.9100 | Dundas Data Visualization | Login
Welcome Guest
This is the support page for the legacy Dundas Dashboard application. For assistance with the current Dundas BI application please click here.
Dashboard v5.0

This site makes extensive use of JavaScript.

Please enable JavaScript in your web browser and reload the page before proceeding.

XAML Error: xClassCanOnlyBeUsedOnLoadComponent

Hide navigation
Modified on Mon, 12 May 2014 04:19 PM Categorized as Error Message, Errors, Maps, Troubleshooting




[0] Parser internal error: Object writer 'xClassCanOnlyBeUsedOnLoadComponent'. [Line: 1 Position: 292]
[System.Windows.Markup.XamlParseException] at MS.Internal.XcpImports.CreateFromXaml(String xamlString, Boolean
createNamescope, Boolean requireDefaultNamespace, Boolean allowEventHandlers, Boolean expandTemplatesDuringParse)
at MS.Internal.XcpImports.CreateFromXaml(String xamlString, Boolean createNamescope, Boolean requireDefaultNamespace,
Boolean allowEventHandlers)
at Dundas.Controls.DataVisualization.Map.Importers.XamlDiagramImporter..ctor(Stream shapeFileStream)
at Dundas.Dashboard.Wizards.MapDataImportWizardViewModel.FireWizardFinished()
at Dundas.Dashboard.Wizards.MapDataImportWizardView.MapDataImportWizard_Finished(Object sender, EventArgs e)
at Dundas.Dashboard.Controls.Wizard.FinishedButton_Click(Object sender, RoutedEventArgs e)
at System.Windows.Controls.Primitives.ButtonBase.OnClick()
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
at System.Windows.Controls.Control.OnMouseLeftButtonUp(Control ctrl, EventArgs e)
at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, Int32
actualArgsTypeIndex, String eventName, UInt32 flags)


This error is seen when importing a XAML file into the map resources.


The error might arise when x:Class used in the file is not correct or the code behind (xaml.cs) has the wrong namespace.


Check whether the namespace specified in X:Class is correct and the code behind (xaml.cs) also uses the same namespace. If you are using a XAML file only without a code behind file (xaml.cs), then you do not need the x:Class tag in your XAML file. Remove this and the exception should go away.

Download a sample XAML file from here: Maps XAML file sample

Related Topics

About Dundas | Contact Us Follow us on Twitter! | Privacy Statement | Report Site Issues

Copyright © 2009-2014 Dundas Data Visualization, Inc.