Article ID: 946539
Article Last Modified on 1/3/2008
APPLIES TO
- Microsoft Visual Studio 2008 Team Suite
- Microsoft Visual Studio 2008 Team Edition for Database Professionals
- Microsoft Visual Studio 2008 Team Edition for Software Architects
- Microsoft Visual Studio 2008 Team Edition for Software Developers
- Microsoft Visual Studio 2008 Team Edition for Software Testers
- Microsoft Visual Studio 2008 Standard Edition
- Microsoft Visual Studio 2008 Academic Edition
- Microsoft Visual Studio 2008 Professional Edition
SYMPTOMS
When you use the Windows Presentation Foundation (WPF) Designer to edit an XAML file in Windows Vista, you may encounter the following problems:
- Microsoft Visual Studio 2008 may stop working.
- The Devenv.exe process may exit, and a System.MissingMethodException exception may be thrown in the PresentationCore namespace.
- You see an entry that resembles the following in the event log:
- You receive unhandled exceptions in the WPF Designer. For example, you may receive the following exception:
RESOLUTION
To resolve this problem, install Windows Vista Service Pack 1 (SP1) Release Candidate (RC).
Note This method may not resolve this problem in all scenarios. If this problem still occurs after you install Windows Vista SP1 RC, contact Microsoft Customer Support Services. For a complete list of Microsoft Customer Support Services telephone numbers and for information about support costs, visit the following Microsoft Web site:
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
If you encounter the problems that are mentioned in the "Symptoms" section, run the .NET Framework 3.5 Installation validation tool to determine whether your computer is in a known problem state. To do this, visit the following Microsoft Developer Network (MSDN) Blogs Web site:
http://blogs.msdn.com/aaronru/archive/2007/11/29/net-framework-3-5-installation-validation-tool.aspx
If this diagnostic tool reports that your computer is in a known problem state, run the Collect tool to collect Visual Studio 2008 Setup log files. This will help Microsoft find the source of the problem. To do this, visit the following MSDN Blogs Web site:
Notice that the Collect tool may take several minutes to start. After you run this tool, post the results to the following MSDN Forums Web site:
You can also submit a new bug by using Microsoft Connect. Make sure that you attach a compressed copy of the log files that are captured by the capture tool.
At this point, we do not have an authoritative fix that resolves the problem in the most common scenarios. Microsoft is working on a resolution for this problem.
Keywords: kbtshoot kbexpertiseinter kbprb KB946539
