BuyLog In
Ticket T581264
Visible to All Users

System.Windows.Markup.XamlParseException occurred

created 7 years ago

This error keeps occurring in each version of this application. It happened this time when I added a grid to the app. In other instances it appears when I upgrade the version of Devexpress. Could you shed some light on what is happening and the way to fix it?

System.Windows.Markup.XamlParseException occurred
  HResult=0x80131501
  Message='Set property 'DevExpress.Xpf.Core.DataSources.DataSourceBase.Path' threw an exception.' Line number '22' and line position '13'.
  Source=<Cannot evaluate the exception source>
  StackTrace:
   at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
   at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
   at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
   at OGRoyalities_V._009.MainWindow.InitializeComponent() in D:\Development\DevExpress\OGRoyalties\OGRoyalities V.009\OGRoyalities V.009\MainWindow.xaml:line 1

Inner Exception 1:
InvalidOperationException: Sequence contains no matching element

Comments (1)
Kirill (DevExpress Support) 7 years ago

    Hello,
    Would you please describe the issue and your scenario in greater detail? Where are you trying to use GridControl? How do you bind its source? What type of source are you using?

    Thanks,
    Kirill

    Sign in to comment on this post

    Answers approved by DevExpress Support

    created 7 years ago (modified 7 years ago)

    Hi,
    Although I am unable to prepare a test sample based on your XAML due to missing parts, this exception is usually related to the fact that the data-access layer (ADO.NET entities) cannot obtain the default database engine instance on your machine. A common way to resolve this issue is to adjust the configuration file (in most cases, it is App.config) so that it references your SQL database engine instance. For more information, see Changing EF’s default connection factory from LocalDb to Sql Server.
    If it doesn't help, collect the exception stack as we described at System.Windows.Markup.XamlParseException and share it for review.

      Sign in to comment on this post

      Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

      Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.