Visual Studio 11 RC Readme

Date Published: May 31, 2012

For the latest version of the Readme click here.

1. Known Issues

1.1 Installing

1.1.1 PreEmptive Analytics and SQL Server Data Tools fail to install in an encrypted folder

If you install Visual Studio in an encrypted folder, these two packages will not be installed:

To resolve this issue:

Ensure that your \Program Files\ directory is unencrypted, or install Visual Studio in a different folder, which is unencrypted.

1.1.2 Earlier versions of Windows SDK and LocalEspC files aren't removed on upgrade to Visual Studio 2012 RC

When you upgrade to Visual Studio 2012 RC, the Windows SDK and LocalEspC files that were installed with Visual Studio 11 Beta are not removed and are not upgraded.

To resolve this issue:

Before you upgrade to Visual Studio 2012 RC, at an elevated command prompt, run the following commands to uninstall the earlier versions of the Windows SDK and LocalEspC files.
msiexec /x {43AF7ECD-64CD-7F87-F07C-2FC9C5FA65C6} IGNOREDEPENDENCIES=ALL /q
msiexec /x {760103C7-F471-589B-B430-EC48E14F6B4C} IGNOREDEPENDENCIES=ALL /q
msiexec /x {6413F6CE-E598-81D9-76B7-59DE02B75B67} IGNOREDEPENDENCIES=ALL /q
msiexec /x {DC50D000-D49D-5729-82CB-C429A7EC5AEF} IGNOREDEPENDENCIES=ALL /q
msiexec /x {57DA16B2-1506-6AE0-7C65-54C1046DC4E0} IGNOREDEPENDENCIES=ALL /q
msiexec /x {95DE5EFF-251C-3029-6727-40C128DB02FE} IGNOREDEPENDENCIES=ALL /q
msiexec /x {1D2F87F3-452E-BEA7-289A-D497CA405D46} IGNOREDEPENDENCIES=ALL /q
msiexec /x {E3B82F29-A209-7006-5652-3B91D08BC6FE} IGNOREDEPENDENCIES=ALL /q
msiexec /x {46869DE6-AF4A-0D11-F1D5-5692D1B66289} IGNOREDEPENDENCIES=ALL /q
msiexec /x {3F835874-1C6A-CD11-D369-7D6D1BB15CBC} IGNOREDEPENDENCIES=ALL /q
msiexec /x {1867A9CA-17B3-8CC2-C97A-3A26D0C00F9C} IGNOREDEPENDENCIES=ALL /q
msiexec /x {79701A48-EB19-E3B2-A400-5E7C0BA2DC48} IGNOREDEPENDENCIES=ALL /q

1.2 Uninstalling

1.2.1 Uninstalling a Lang Pack removes some of the .NET Framework 3.5 SDK Tools

If you install Visual Studio 2012 RC Professional, Premium, or Ultimate, then install one or more Lang Packs, and then uninstall a Lang Pack, the following .NET Framework SDK tools are uninstalled:

Program Files\Microsoft SDKs\Windows\v7.0A\bin\dasmhlp.cnt
Program Files\Microsoft SDKs\Windows\v7.0A\bin\dasmhlp.hlp
Program Files\Microsoft SDKs\Windows\v7.0A\bin\fuslogvw.exe
Program Files\Microsoft SDKs\Windows\v7.0A\bin\gacutil.exe
Program Files\Microsoft SDKs\Windows\v7.0A\bin\gacutil.exe.config
Program Files\Microsoft SDKs\Windows\v7.0A\bin\ildasm.exe
Program Files\Microsoft SDKs\Windows\v7.0A\bin\ildasm.exe.config
Program Files\Microsoft SDKs\Windows\v7.0A\bin\peverify.exe
Program Files\Microsoft SDKs\Windows\v7.0A\bin\peverify.exe.config
Program Files\Microsoft SDKs\Windows\v7.0A\bin\sn.exe
Program Files\Microsoft SDKs\Windows\v7.0A\bin\sn.exe.config

To resolve this issue:

To restore the tools after a Lang Pack is uninstalled, use the installed-programs page in the Control Panel to repair Visual Studio. Or, if another Lang Pack is still installed, you can repair it instead.

1.3 Product Issues

1.3.1 General Issues

1.3.1.1 Adding a file in more than one project causes the file name to be changed

If you add to a project a file from a location that is accessed by a URI, and then use the Add Existing Item menu command to add the file to another project, the file name may be changed in the second project. For example, Example.png might be changed to Example[1].png.

To resolve this issue:

In the project that has the misnamed file, open the shortcut menu for the file, choose Rename, and then enter the original file name.

1.3.2 Debugging and Diagnostics

1.3.2.1 Capture Frame command causes a DirectX-not-supported error

In a Graphics Diagnostics session, the following error might be generated when you run the Capture Frame command:

The Graphics Diagnostics engine couldn't provide the results, most likely because the vsglog is making DirectX calls not supported on this machine.

This error might occur even if supported hardware is available.

To resolve this issue:

Close the solution, restart Visual Studio, and then try again.

1.3.3 Developing for Windows 8

1.3.3.1 Simulator doesn't show the current state of a Metro style HTML app in Blend

Blend might not display the current state of a Metro style HTML app in the Simulator when it's already open and you press F5.

To resolve this issue:

Close the Simulator and then press F5 again.

1.3.3.2 Display in the simulator isn't updated when a project is redeployed

When a project is redeployed to a running simulator, success is reported but the simulator display isn't updated. This problem occurs only on redeployment, not when a different project is deployed.

To resolve this issue:

Exit the simulator before you redeploy a project.

1.3.3.3 When a delegate that has more than four parameters is invoked, error C3481 occurs

If you try to invoke a delegate that has more than four parameters, this error (C3481) occurs:
1>c:\program files\microsoft visual studio 11.0\vc\include\vccorlib.h(2300): error C3481: '____arg4': lambda capture variable not found (Blankpage.xaml.cpp)
1> d:\svn\demo\20120509_dp7 \app1\app1\ blankpage.xaml.h(28) : see reference to function template instantiation 'void Platform::EventSource::InvokeVoid<App1::Test1,bool,bool,bool,bool,bool>(Platform::Details::EventLock *,__TArg0,__TArg1,__TArg2,__TArg3,__TArg4)' being compiled
1> with
1> [
1> __TArg0=bool,
1> __TArg1=bool,
1> __TArg2=bool,
1> __TArg3=bool,
1> __TArg4=bool
1> ]
This occurs because vccorlib.h contains too many underscores.

To resolve this issue:

Open \Program Files(x86)\Visual Studio 11.0\VC\include\vccorlib.h and remove the two extra underscores in arg4 where the error message is displayed.

1.3.4 Web Development

There are no known issues.

1.3.5 Database Development

1.3.5.1 Upgrade of Visual Studio 2008 database projects to SSDT is not supported

When a Visual Studio 2008 database project is opened in Visual Studio 2012 RC, the user is prompted to upgrade. Completion of the upgrade steps appears to succeed, but the project still cannot be loaded because an upgrade to SQL Server Data Tools (SSDT) is not supported.

To resolve this issue:

There is no workaround.

1.3.6 SharePoint Development

1.3.6.1 Profiling doesn't work when a SharePoint project is switched from farm solution to sandboxed solution

When you change a SharePoint project from farm solution to sandboxed solution, the SharePoint project assemblies are not profiled.

To resolve this issue:

  1. Make the existing project a farm solution, and then create a new sandboxed solution.
  2. Migrate the existing project to the new one and then use it for profiling.

1.3.7 Team Explorer

There are no known issues.

1.3.8 Test Tools

1.3.8.1 Code coverage for native C++ doesn't work

Code coverage for native C++ doesn't work in Visual Studio 2012 RC.

To resolve this issue:

There is no workaround.

1.3.9 Windows SDK

There are no known issues.

1.3.10 Lab Management

There are no known issues.

1.3.11 Windows Presentation Foundation (WPF) Tools

There are no known issues.

1.3.12 Windows Workflow Foundation (WF) Tools

Exception occurs when expressions are modified in a Visual Basic workflow project in Visual Studio 2012 RC

When you modify an expression in a Visual Basic workflow project, you might encounter an InvalidCastException. When you close the exception message, IntelliSense stops working even though highlighting and expression validation continue to work and you can still author and run workflows.

This problem might also occur in Visual C# workflow projects if you target the .NET Framework 4.

To resolve this issue:

         Download the update.

1.3.13 Other Areas

There are no known issues.

2. Related Links

2.1 ASP.NET MVC 4 Release Notes

The release notes for ASP.NET MVC 4 are available at http://go.microsoft.com/fwlink/?LinkID=249020

2.2  RC Release Notes

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

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


© 2012 Microsoft Corporation. All rights reserved.

Terms of Use | Trademarks | Privacy Statement