BuyLog In
Ticket T583774
Visible to All Users

System.Windows.Markup.XamlParseException

created 7 years ago (modified 7 years ago)

I get "System.Windows.Markup.XamlParseException" error message frequently. It is related to the Initialize Component function under MainWindow().  I have no idea what the problem is or how to find a solution. It will generally occur when upgrading versions and applies to existing applications. In this instance I get the following message:

Set property "DevExpress.Xpf.Core.DataSource.DataSourceBasePath" threw an exception. Line number 48 and line position 13.
2.0f 2 Inner Exceptions
Win32Exception: The network path was not found

I would like to understand what is causing the problem and how to approach finding a solution. It is very frustration to keep running into the same Initialize Component error time after time. I wish I could say I was an expert and understood all of the internals of WPF and DevExpress, but I am a self taught programmer that is struggling to get his apps to work and to keep the working after they are finished and a new iteration of DevExpress arrives every three weeks. I haven't written a new app in the last three months because I have been going back and redoing existing apps to make them work again after a new release comes out. I think I should  be able to do better than this and am asking for your assistance with my current issue and with having to redo existing apps when a new version of your library comes out and I use your Project Converter to upgrade an existing app.
Tom

Comments (1)
DevExpress Support Team 7 years ago

    Hello Tom,

    I regret to hear that you faced such difficulties while upgrading your application. I have thoroughly iterated through our database but was not able to associate it with a known issue. In order to help to determine why this error occurs, please share the following details:

    1. What version of our components you're using before upgrading?
    2. Collect and provide the entire call stack of this exception (see Collecting a call stack to track down the cause of VS crash or freeze issues and How to obtain the exception's call stack).
    3. Confirm whether you're using one of our Server Mode data sources (if so, clarify how they are defined and configured).

    I look froward to your reply.

    Thanks,
    Michael

    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.