Visual Studio 2012 Readme

Date Published: August 15, 2012

For the latest version of the Readme click here

1. System Requirements

1.1 Upgrading from pre-release versions of Visual Studio 2012

For information about how to upgrade from a pre-release version of Visual Studio 2012 - for example, RC or Beta - see the Compatibility page on the Visual Studio website.

2. Known Issues

2.1 Installing

There are no known issues.

2.2 Uninstalling

There are no known issues.

2.3 Product Issues

2.3.1 General Issues

2.3.1.1 WINMDEXP WME1108 error might occur when you build a solution that has both C++ and C# projects

When you build an application from a solution that has both C++ and C# projects, you might encounter an error that resembles this:

WINMDEXP : error WME1108: Windows Runtime type 'Windows.Foundation.Point' was found in multiple referenced winmd files. Please remove either 'D:\Program Files (x86)\Microsoft SDKs\Windows\v8.0\ExtensionSDKs\Microsoft.VCLibs\11.0\References\CommonConfiguration\neutral\platform.winmd' or 'D:\Program Files (x86)\Windows Kits\8.0\References\CommonConfiguration\Neutral\Windows.winmd' from the list of referenced files.

This error occurs because the C Runtime Library (CRT) and Windows.winmd have duplicate types, but in the CRT the definitions for those types are specific to C++ -- for example, Windows.Foundation.Point.

To resolve this issue:

In Solution Explorer, in each C# project, expand the References node and then remove Microsoft.VCLibs.

2.3.1.2 After upgrade to the release version of Visual Studio 2012, cross-compilation, command-line build shortcuts don't work

After an upgrade to the release version of Visual Studio 2012, cross-compilation command-line build shortcuts don't work because these files are removed:

To resolve this issue:

After you upgrade to the release version of Visual Studio 2012, run Repair on it:

  1. On the installed programs page of the Control Panel, open the shortcut menu for the Visual Studio 2012 edition that you want to repair, and then choose Change.
  2. When Visual Studio Setup opens, choose Repair.

2.3.2 Debugging and Diagnostics

There are no known issues.

2.3.3 Developing for Windows 8

2.3.3.1 In Blend and the XAML Designer in Visual Studio, incorrect markup may be generated when you create an empty control template

In Blend and the XAML Designer in Visual Studio, when you create a new, empty control template for a control (selecting the Create Empty command from Edit Template), a <VisualStateManager.VisualStateGroups> element is added to the XAML markup. The content of this element is not correct, and the result is that the control template does not function correctly at run time (for example, in the case of Button, the control would not return to the Normal visual state).

To resolve this issue:

After selecting the Create Empty command, you can manually delete the <VisualStateManager.VisualStateGroups> element. You can then use the States panel in Blend to edit visual states. By doing so Blend will generate the correct markup.

Alternatively, you can select the Edit a Copy command from Edit Template, and then delete the root element in the control template. This will result in the correct markup.

2.3.3.2 IntelliSense tooltips for Windows Library for JavaScript are not localized in Chinese Traditional or Chinese Simplified

When Visual Studio is set to use Chinese Traditional or Chinese Simplified, the IntelliSense tooltips for Windows Library for JavaScript appear in English. This issue affects Visual Studio 2012 Ultimate, Visual Studio 2012 Premium, Visual Studio 2012 Professional, and Visual Studio Express 2012 for Windows 8.

To resolve this issue:

  1. In the %Program Files%\Microsoft SDKs\Windows\v8.0\ExtensionSDKs\Microsoft.WinJS.1.0\1.0\DesignTime\CommonConfiguration\Neutral\Microsoft.WinJS.1.0\js\metadata\ folder, change these subfolder names: change zh-Hans to zh-CN and change zh-Hant to zh-TW.
  2. Restart Visual Studio.

2.3.3.3 C++ app for the Windows Store won't build after an upgrade to the release version of Visual Studio 2012 and then an upgrade to Windows 8

On a system that was upgraded to the release version of Visual Studio 2012 and then was upgrade from Windows 7 to Windows 8, a C++ app for the Windows Store won't build because these files were removed:

To resolve this issue:

After you upgrade to the release version of Visual Studio 2012 and then upgrade to Windows 8, run Repair on Visual Studio 2012:

  1. On the installed programs page of the Control Panel, open the shortcut menu for the Visual Studio 2012 edition that you want to repair, and then choose Change.
  2. When Visual Studio Setup opens, choose Repair.

2.3.3.4 When the XAML Designer in Visual Studio is used with a C++ project that's configured for x64 or ARM, the Designer might become unresponsive

The XAML Designer in Visual Studio does not support x64 and ARM configurations, and in most cases, the Designer displays a message that reports this fact. However, when an x64 or ARM configuration is used in a C++ project, the Designer might stop responding and appear to hang.

To resolve this issue:

There is no workaround except to avoid the use of the XAML Designer for x64 and ARM configurations.

2.3.3.5 For a control template in an Extension SDK, the Edit a Copy command in Blend and in the XAML Designer creates a blank copy

In Blend and in the XAML Designer in Visual Studio, when you use the Edit a Copy command on the Edit Template menu to create a copy of a control template in an Extension SDK, the copy is empty.

To resolve this issue:

  1. In the Extension SDK installation folder, open \Redist\CommonConfiguration\neutral\Themes\Generic.xaml.
  2. In Generic.xaml, in the default style, locate the default template for the Extension SDK and copy it.
  3. In the blank copy of the control template, paste the default template information. Change the xmlns names as appropriate for the control template, and change the attribute on the control instance to a Style attribute.

2.3.4 Web Development

There are no known issues.

2.3.5 Database Development

There are no known issues.

2.3.6 SharePoint Development

There are no known issues.

2.3.7 Team Explorer

There are no known issues.

2.3.8 Test Tools

2.3.8.1 Unhandled System.DllNotFoundException when using web test recorder for the first time on a machine with 64 bit Internet Explorer 10

After a successful installation using Visual Studio Ultimate for the first time to record web tests, the following error may be seen when web test recording is stopped:

Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue. Unable to load DLL "Microsoft.VisualStudio.QualityTools.RecorderBarBHO100.dll". The specified module could not be found.

Internet Explorer instance used for recording the web test is not automatically closed.

To resolve this issue:

When this exception occurs, close the Internet Explorer window and delete the recorded web test. This issue does not occur again on subsequent attempts of recording web tests; it is seen only during the first usage of the web test recorder.

2.3.9 Windows SDK

There are no known issues.

2.3.10 Lab Management

There are no known issues.

2.3.11 Windows Presentation Foundation (WPF) Tools

There are no known issues.

2.3.12 Windows Workflow Foundation (WF) Tools

There are no known issues.

2.3.13 Other Areas

There are no known issues.

3. Related Links

3.1 Release Notes

The Visual Studio 2012 Redist.txt file can be found at: http://go.microsoft.com/fwlink/?LinkId=247624

The HelpViewer 2.0 Readme can be found at: http://go.microsoft.com/fwlink/?LinkId=255960


© 2012 Microsoft Corporation. All rights reserved.

Terms of Use | Trademarks | Privacy Statement