Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: An InvalidOperationException exception occurs in a WPF application when you set the Visibility property of a Window object that is loaded by using the Application.LoadComponent method


View products that this article applies to.

Symptoms


Consider the following scenario:
  • You have a .Net Framework 3.5 Service Pack 1-based Windows Presentation Foundation (WPF) application.
  • You call the Application.LoadComponent method to load an Extensible Application Markup Language (XAML) file.
  • You set the Application.StartupUri property of the XAML file.
  • You set the Visibility property of the window object in the XAML file.
In this scenario, the application crashes when you try to run it. Additionally, if you try to debug the application, you find that an InvalidOperationException exception was thrown.

↑ Back to the top


Cause

This problem occurs because the object of the XAML file is closed before the Visibility property is set.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites


You must have .NET Framework 3.5 Service Pack 1 (SP1) installed to apply this hotfix.

Restart requirement


You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information


This hotfix does not replace any other hotfixes.

File information


The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the
Time Zone
tab in the
Date and Time
item in Control Panel.

x86-based versions of Windows XP and of Windows Server 2003
File nameFile versionFile sizeDateTimePlatform
presentationframework.dll3.0.6920.40005,283,84029-Jan-200923:46x86

x64-based versions of Windows XP and of Windows Server 2003
File nameFile versionFile sizeDateTimePlatform
presentationframework.dll3.0.6920.40004,636,67229-Jan-200923:23x64

x86-based versions of Windows Vista and of Windows Server 2008
File nameFile versionFile sizeDateTime
Presentationframework.dll3.0.6920.40005,283,84005-Feb-200900:20

x64-based versions of Windows Vista and of Windows Server 2008
File nameFile versionFile sizeDateTime
Presentationframework.dll3.0.6920.40004,636,67205-Feb-200900:26

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about the Application.StartupUri Property class, visit the following Microsoft Web site:
For more information about the InvalidOperationException exception, visit the following Microsoft Web site:

↑ Back to the top


Keywords: kbhotfixserver, kbqfe, kbsurveynew, kbpubtypekc, kbnotautohotfix, kbexpertiseadvanced, kb, kbhotfixdev

↑ Back to the top

Article Info
Article ID : 967056
Revision : 4
Created on : 3/30/2017
Published on : 3/30/2017
Exists online : False
Views : 251