FIX: April 2012 Update for Visual Studio 11 Beta

Supported operating systems:

• Windows 7 (x86 and x64)
• Windows 8 Consumer Preview (x86 and x64)
• Windows Server 2008 R2 (x64)
• Windows Server 8 Beta (x64)

Software requirements

To apply this update, one of the following supported Visual Studio 11 Beta programs must be installed on your computer:

• Visual Studio 11 Ultimate Beta
• Visual Studio 11 Premium Beta
• Visual Studio 11 Professional Beta
• Visual Studio 11 Express Beta for Windows 8
• Visual Studio 11 Express Beta for Web
• Team Explorer for Visual Studio 11 Beta

Installation notes

This update will take additional time for each Language Pack that is installed. If all Language Packs are installed on a computer, this update may take almost an hour. We are addressing this in a future update.

The update applies to all localized versions of Visual Studio, although some strings in the Setup installer and strings that are updated in the update are not localized. Additionally, the Setup installer may incorrectly be in English in some configurations. This can be ignored and will be addressed in a future release.

The installer will incorrectly show that it is updating Visual Studio 11 Beta to version 50216.0. The correct version of this update is 50323.1.

Added technology improvements and issues that are fixed in Visual Studio 11 Beta

Feature improvements in the Unit Test Explorer

The Unit Test Explorer grouping system was changed as follows:

• No more confusing child pages
• Simple, easy-to-understand list and grouping that displays all your tests

Feature improvements in IntelliTrace

IntelliTrace Summary now includes Web Request Information. This data is available when you use the IntelliTrace Collector to collect data from applications that are hosted in Internet Information Services. This process is described in the instructions found on MSDN.

Stability improvements

• Fixed a crash that occurs when you use the Find Dialog drop-down menu by using the mouse.
• Fixed an issue in which the XAML Designer in Visual Studio 11 Beta crashes as soon as you try to open an XAML document. This crash happens because the dependencies for the XAML Designer are in folders that do not have their permissions set correctly. Incorrect permissions occur because of an error in Visual Studio Setup. The conditions where you are likely to experience this crash are as follows:
  • You installed Visual Studio into a nondefault location. For example, Windows was installed to C:\Windows, and you install Visual Studio to D:\MyFolder.
  • You upgraded your system to Windows 8 Consumer Preview from an existing Windows 7 installation.
  • You are working on a Windows Store app, in any language (C#, Visual Basic, C++), and you are trying to open an XAML file.
• Fixed a hang or crash when you edit a Razor file that uses either the .cshtml or .vbhtml file name extension together with the HTML indenting option set to Block. The default HTML indenting option is Smart. But because Block is the option for earlier versions of Visual Studio, if a user has an earlier version of Visual Studio that is installed side by side with Visual Studio 11 Beta, the Block option is migrated and will also cause this crash.
• Fixed a crash that occurs when you browse to the Fonts and Colors dialog box. This crash occurs because of an invalid cache.

Performance improvements

• Removed long delays when you try to scroll a C# file immediately after you open it.
• Removed a freeze that lasted up to five seconds in the UI when you are typing in C# projects that use SupportsAysncPattern.

Team Explorer

Corrected an issue in which the Connect to Team Project Dialog in Dark Theme would display black text on a black background.

C++ projects

Corrected an issue in Visual Studio 2010 or a Visual Studio 11 Beta project that uses the Visual Studio 2010 platform tool set. This is the default for Visual Studio 2010. However, the tool set can be selected in Visual Studio 11 Beta. The issue occurred when the tool set was loaded in Visual Studio 11 Beta, and the tool set would not run when you used the keyboard command Ctrl+F5 or F5.

Extensibility and VSIP control fixes

• Windows Presentation Foundation (WPF), Winforms, and web controls that depend on assemblies that are registered in AssemblyFoldersEx may not be displayed in the Visual Studio toolbox after installation. The assemblies that are registered in AssemblyFoldersEx affected controls that are installed from the following:
  
  • AssemblyFoldersEx
  • The following registry subkey:
    HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\11.0\ToolboxControlsInstaller
  • The Choose Toolbox Items dialog box
  • The assemblies that are dragged to the toolbox from Windows Explorer
  
  Unfortunately, the controls that were authored by using Silverlight still have this issue. This issue is being addressed for a later release.
  
• Fixed an issue in which Assemblies that have many WPF controls took a long time to load into the toolbox.
• Corrected an issue in which WPF controls that were installed into the global assembly cache (GAC) could not be used in the toolbox.