Bug Report T328978
Visible to All Users

Export of GridControl from a separate UI thread throws "The calling thread cannot access this object because a different thread owns it" exception

created 9 years ago (modified 9 years ago)

Hi,

Export works correctly for the first instance of the grid control but fails for the second one with "The calling thread cannot access this object because a different thread owns it." exception.

Steps to reproduce.

  1. Run the application
  2. Click "Open new GridControl" button. New window will open.
  3. Click "Export" button at the top of the component. Export works correctly.
  4. Click "Open new GridControl" button. New window #2 will open.
  5. Click "Export" button at the top of the component. Export fails.

If I remove "ShowTotalSummary="True"" from the TableView definition in the .xaml file then everything works correctly. I'm sure it uses some kind of shared static resource that is causing this issue.

This issue is a "showstopper" as we can't release our product because of this.

Thank you,

Eugene

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

    Hello,
    I've reproduced this issue and forwarded it to our R&D team for further research. Follow our notifications to be informed about our progress.

    Thanks,
    Kirill

    Answers approved by DevExpress Support

    created 9 years ago (modified 9 years ago)

    We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

    Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

      Comments (3)

        When do you expect 1.11 to be released? We're currently on 1.8.
        Thank you,
        Eugene

          1.10 is not available for download… The highest version is 1.9 (released on December 7th). Please advice.
          Eugene

          DevExpress Support Team 9 years ago

            Hi,

            The current 15.1 version is 15.1.9. And, you do not need to wait for v15.1.10 to resolve the issue - just install the hotfix from this thread. You can request it as described in the How to request a hotfix article.

            Regards,
            Alex

            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.