Freigeben über

Workaround: Installing Windows SDK after VS2008 breaks WPF Intellisense

  • Artikel

UPDATE: the official Windows SDK Workaround to this issue has been posted on the Windows SDK Blog.  

Scenario: VS 2008 and Windows SDK customer Karl has used the XAML functionality in VS2008 for several weeks. He uses autocomplete extensively. Karl installed the Windows SDK for Server 2008 and discovered that XAML autocomplete (Intellisense) no longer works (see repro steps below).

The Windows SDK Team has been able to repro the issue. We are investigating the cause now. It looks like one Visual Studio registry value is being incorrectly reset after the Windows SDK is installed, causing this failure. We are working with others in Visual Studio to further understand the problem and develop appropriate workarounds.

In the meantime, we have found that repairing Visual Studio 2008 allows XAML autocomplete to work correctly again. No side issues are apparent at this time, although you will lose all of your custom settings and any patches you've made since installing VS.

 

Workaround #1: repair Visual Studio 2008:

1. From the Start button, open the Control Panel

2. Click on Program and Settings (Add/Remove Programs on non-Vista machines)

3. Click to select Visual Studio 2008 and click Change (at the top of the window)

4. When the change dialog box launches, select Repair

Workaround #2:

Register TextMgrP.dll manually (my choice forthe best solution)

On an X86 machine:

1. Open a Windows CMD window as an Administrator (On Vista: Start, All Programs, Accessories, right-click on command prompt and choose to Run as Administrator)

2. Type: regsvr32 "%CommonProgramFiles%\Microsoft Shared\MSEnv\TextMgrP.dll”

On an X64 machine:

1. Open a Windows CMD window as an Administrator (On Vista: Start, All Programs, Accessories, right-click on command prompt and choose to Run as Administrator)

2. Type: regsvr32 "%CommonProgramFiles(X86)%\Microsoft Shared\MSEnv\TextMgrP.dll”

 Restart Visual Studio and Intellisense should be working correctly again.

 

Another workaround is to fix the Registry Key. This is recommended for experienced users only.  (Please review the article, Windows registry information for advanced users before using regedit.)

Brett Kitty describes how to fix the issue using regedit.

These are the repro steps we’re working with. If you have a different scenario, or find that these workarounds do not resolve your problem, please let me know .

 

Setup:

1. Vista Ultimate X86 or X64

2. Install VS 2008 Pro

3. Install 338649_ENU_i386_zip.exe hot fix for VS Editor (see https://weblogs.asp.net/scottgu/archive/2008/02/08/vs-2008-web-development-hot-fix-roll-up-available.aspx for more info)

(Machine was fully patched and update via MU day before installing SDK)

4. (Build XAML Project and use autocomplete – works fine)

5. Install Windows SDK for Server 2008 (build .367) default settings

 

 Steps to Repro

1. Open VS2008

2. Create a new Windows, WPF solution.

3. Open the window1.xaml file and edit the XAML.

4. By default a <Grid> </Grid> is the root element.

5. Add a child Button object.

a. After <Grid> press enter to get a new line between the two Grid markup elements.

b. Type < at that point Intellisense autocomplete should open up and give you list of objects. It won’t.

Comments

  • Anonymous
    February 15, 2008
    Scenario: VS 2008 and Windows SDK customer Karl has used the XAML functionality in VS2008 for several

  • Anonymous
    February 22, 2008
    Karin, Nice fix to use regsvr32 over the registry editing. Have a great day, Karl