Visual Studio 2015 Preview fixed bugs and known issues

Visual Studio 2015 Preview cannot be installed on a computer that has a previous version of Visual Studio "14" CTP installed. To install this release version, you must first uninstall any currently installed CTP.

↑ Back to the top

Visual Studio 2015 Preview fixed bugs and known issues

This article lists the fixed bugs and known issues for the Microsoft Visual Studio 2015 Preview.

Visual Studio 2015 Preview is a pre-release version of the next major release of Visual Studio. Preview provides early adopters with an opportunity to test the new and improved product features, and the ability to share feedback with the product team. This release is not intended for use on production computers or to create production code.

The goal of this Preview version is to collect your feedback. To report a bug, please use Connect. You can also share your ideas and suggestions on UserVoice. Your quick thoughts can be shared by using Send-a-Smile through the Visual Studio IDE.

More information is also available at VisualStudio.com.

Notes

This release is unsupported and is intended to be used for testing, trial, and feedback only.
This release has not been subjected to final validation. It is not meant to be run on production workstations or servers, or used to create production code. The installation of this release on a production server will put the server into an unsupported state.
Although this release is intended to be installed side-by-side with earlier versions of Visual Studio, complete compatibility is not guaranteed.

↑ Back to the top

Visual Studio 2015 Preview details

To discover what is new in Visual Studio 2015 Preview, see the Visual Studio Preview release notes.

Fixed bugs

Debugger

Assume that you set a breakpoint in an auto-implemented properties in a C# application. When you run the application, you receive the following error message:

A breakpoint could not be set at this location.

Known issues

The Visual Studio 2014 CTP3 had an issue that causes F# 3.1 builds to fail that includes when you compiled from Visual Studio 2014. This issue was fixed in Visual Studio 2015 Preview. However, if Visual Studio 2014 CTP was installed on your computer, Visual Studio 2015 Preview cannot replace it with the correct file.

To work around this issue, delete the following directory:
%Program files%\Reference Assemblies\Microsoft\FSharp\.NETFramework\v4.0\4.3.1.0
Then, repair the Visual Studio 2015 Preview installation.

Visual Studio IDE

When you use Windows Presentation Foundation (WPF) applications in Visual Studio 2015 Preview, you may experience intermittent performance, reliability, or rendering issues that are caused by bugs in your graphics drivers.

To work around these issues, follow these steps:
1. Make sure that the latest graphics drivers are installed because outdated drivers are a common source of WPF rendering issues.
2. Switch to software rendering by turning off hardware graphics acceleration. To do this, use one of the following methods:
  - Use the Visual Studio visual experience settings. To do this, click Tools, click Options, expand Environment, and then click General. The following screen shot shows this settings page.
    
    The status text underneath the settings check boxes describes the current visual experience configuration. This text is updated only after changes are applied. To override Visual Studio automatic settings, follow these steps:
    1. Clear the Automatically adjust visual experience based on client performance check box.
    2. Clear the Use hardware graphics acceleration if available check box to block the use of hardware graphics acceleration when it is available.
    Select or clear the Enable rich client visual experience check box to make sure that rich visuals are always on or off, respectively. If you select this option, rich visuals are used independent of the computer environment. For example, rich visuals are used when the application runs locally on a rich client and through Remote Desktop.
  - You can change specific Visual Studio registry entries to disable Auto Adjust visual experience settings. To do this, locate the following subkey:
    
    [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\General]
    Under this subkey, locate the following entries:
    "AutoAdjustExperience"=dword:00000000
    "VisualEffectsAllowed"=dword:00000000
    If you prefer to make changes that are computer-wide, locate the following registry subkey:
    
    [HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics]
    Under this subkey, locate the DisableHWAcceleration entry, and then change the DWORD value from 00000001 to 00000000.
    
    If you override these settings, you should also revert to the default settings (select the Automatically adjust visual experience based on client performance check box) if the issues that you are trying to resolve persist or if you experience new rendering performance issues.
    
    Note By default, Visual Studio does not use hardware graphics acceleration and not provide a rich client visual experience when you run in virtual machine environments on servers that have Hyper-V enabled.
    
    For more information about how to troubleshoot graphics issues, see Guidelines for troubleshooting graphic issues in WPF applications .

Web Platform and Tools

When you publish an ASP.NET 5 project and use the Precompile option, the content will be skipped if it was previously published with the same version. To work around this issue, change the version property in project.json.
ASP.NET 5 web projects need a wwwroot element in project.json. For existing projects, you can add "wwwroot":".\". For more information, see Introduction of Project.json. If the wwwroot element is missing and web publish is invoked, an error is returned that states that kpm pack has existed with code 1.
When you publish an ASP.NET 5 project, the build is not verified before publish starts. To work around this issue, build your project before publishing.
After you scaffold an empty ASP.NET 5 project from the command line, the readme file that is displayed has old content. The contents should not be used directly in your projects.
For ASP.NET 5 projects, the IntelliSense project list does not associate code files in subfolders with the project. Instead, Miscellaneous Files is displayed.
When you publish or browse Server Explorer, you may not be able see your Azure Websites resources. Even though you are signed into Visual Studio by using the correct account. To work around this issue, go to Server Explorer. Right-click on the Azure node and select Manage Subscription…. Now, check the checkbox that tells Visual Studio to use the account that you are logged in with.

Debugger

Expression evaluation fails when you stop in a method that contains references to embedded PIA types. The Locals window will be empty, and expressions in data tips and in the Watch, Autos, and Immediate windows will report the following error message:

error CS1748: Cannot find the interop type
To work around this issue, use the legacy Expression Evaluator (EE) when you debug C# or VB methods that reference PIA types. To switch to the legacy EE, click Tools, click Options, expand Debugging, and then click General. The following screen shot shows this settings page.

In the Details pane, select the Use the legacy C# and VB expression evaluators check box.
Debugger PerfTips can report values that are lower than they are supposed to be when many first-chance exceptions or module loads occur in between breakpoints or during a step.

Visual C++

The Blank Page template In the Add New Item dialog box for Visual C++ Windows Phone 8.1 and Shared projects is missing.

To work around this issue, use one of the following methods:
- For a solution that contains Windows Store 8.1 projects:
  1. Create the Blank Page through the Windows Store 8.1 project.
  2. Drag the blank page item from the Windows Store 8.1 to the desired project.
- For a phone only project:
  1. Create any other page template.
  2. Remove any unwanted template code.

Testing Tools

If you have created Coded UI tests for automated testing of Windows Store apps in Windows 8.1. When you try to run the same tests on Windows 10 Technical Preview, you may experience one or more of the following issues:
- Items in a grid view control inside a semantic zoom control cannot be highlighted by using Coded UI test builder. UI actions against these grid view items may be unsuccessful and tests will fail. There is no workaround for this issue.
- Toggling a ToggleSwitch control on and off may crash the application. There is no workaround for this issue.
- If you have added a tile control to the UIMap, using the control to launch XAML applications does not work. To work around this issue, use the XamlWindow.Launch() API to start the application instead.
- If you have added controls that are located in flyouts associated with controls in the AppBar to the UIMap, then using these controls to access application functionality does not work. There is no workaround to this issue.
- If you have added FilePicker controls to the UIMap, then using these controls to select files does not work. There is no workaround to this issue.
- If your Coded UI automation on Windows 8.1 is opening Start menu to start applications, that may not work on Windows 10 Technical Preview . There is no work around for this issue.
- For a hand-coded Coded UI automation scenario, using XamlWindow.Launch to start a Windows Store application under test may fail to locate controls. To work around this issue, add a search property on the application window title as follows:
```
// For example you are launching a app
XamlWindow BVTAut = XamlWindow.Launch("MyAppUnderTest_8wekyb3d8bbwe!App");
 
// Add an additional search property on application window name
BVTAut.SearchProperties[XamlWindow.PropertyNames.Name] = <You Application title>; 
```
- If you have added Charms window controls to the UIMap, you cannot use these controls to access charms bar. There is no workaround to this issue.
When you work with Smart Unit Tests in Visual Studio 2015 Preview, duplicate tests may be generated when the .NET Framework 3.5 is not installed on the computer. To work around this issue, modify C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Pex\Microsoft.Pex.x86.exe.config to following:
```
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0"/>
  </startup>
  <runtime>
    <gcConcurrent enabled="false"/>
  </runtime>
</configuration> 
```
You cannot build existing or create new Visual C++ test projects of type Unit Test Library (Window) and Unit Test App (Windows Phone) in Visual Studio 2015 Preview. To work around this issue, install Visual Studio 2013 Update 3 on the same computer.

Visual Studio Tools for Apache Cordova

There are some known issues when you install and use the Visual Studio Tools for Apache Cordova, such as debugging or deploying Apache Cordova applications. For the full list of issues, see Tools for Apache Cordova Known Issues and the FAQ.

SQL Server database tooling

When you debug Transact-SQL objects from SQL Server Object Explorer, Visual Studio may crash. To work around this issue, open a VB or C# Console application project before initiating Transact-SQL debugging.

Breaking changes

Visual C++

You can no longer use char16_t or char32_t as aliases in a typedef, because these types are now treated as built-in. It was common for users and library authors to define char16_t and char32_t as aliases of uint16_t and uint32_t respectively. For example:
```
    typedef uint16_t char16_t; //C2371
    typedef uint32_t char32_t; //C2371

    uint16_t x = 1; uint32_t y = 2;
    char16_t a = x; //C2440
    char32_t b = y; //C2440 
```
Improvements to the compiler’s error reporting may result in warnings that differ in order and specifics from those reported by earlier versions of the compiler.
User-defined literals are a new syntactic form, and may prevent some existing macros from being expanded. For example, "foo"_bar will be treated as a user-defined literal, even if _bar was defined as a macro.
The concatenation of adjacent wide or raw string literals (L"Hello"L"World") will require a space to be inserted (L"Hello" L"World"), because the prefix for the second string is now treated as a user-defined literal suffix.
/CLR:pure and /CLR:safe are deprecated. The compiler will warn you about the use of these flags.
/CLR:OldSyntax, /Wp64, and /Zg flags have been removed.
You can no longer run unit tests with C++/CLI from the command-line with mstest.exe. Instead, use vstest.console.exe.

More information

How to download Microsoft support files

Updates for other products in the Visual Studio family can be found on the Microsoft download site for Visual Studio.

Requirements

For detailed System Requirements see Visual Studio 2015 Compatibility.

On Windows 8.1 and Windows Server 2012 R2, update 2919355 (also available through Windows Update) is required for the Visual Studio 2015 Preview to install successfully.

Restart requirement

You may have to restart your computer after you install this package.

Supported architectures

32-bit (x86)
64-bit (x64) (WOW)
ARM

Third-party applications

Visual Studio 15 Preview installs a Secondary Installer that lets you install third-party applications. When Visual Studio 15 Preview is uninstalled, or when the Secondary Installer is uninstalled, it does not uninstall the third-party applications. These third-party applications may or may not have entries in the Programs and Features item in Control Panel.

The following are the third-party applications that the Secondary Installer lets you deploy to your computer, and the method by which they can be uninstalled:

Google Chrome: Chrome has an entry in Programs and features, and it can be uninstalled from there.
Android SDK: Android has an entry in Programs and Features, and it can be uninstalled from there.
Git: Git has an entry in Programs and Features, and it can be uninstalled from there.
Apache Ant: Ant does not have an entry in Programs and Features. To uninstall it, you must follow these steps:
1. Find the Ant folder on disk.
2. From a command line environment, type set ant to see the Ant environment variable. The variable points to the folder.
3. Locate the folder, and then delete it.
Joyent Node.js: Joyent Node has an entry in Programs and Features, and it can be uninstalled from there.
Apple iTunes: iTunes has an entry in Programs and Features, and it can be uninstalled from there.
Oracle Java Development Kit: Java has an entry in Programs and Features, and it can be uninstalled from there.
SQLite for Windows Runtime: SQLite is installed as an extension in Visual Studio. To remove it, follow these steps:
1. Start Visual Studio.
2. On the Tools menu, click Extensions and Updates.
3. Locate SQLite for Windows Runtime, and then click uninstall.
Websocket4Net: Websocket4Net is installed as a DLL to your operating system (only on Windows 7). To remove it, locate the Visual Studio 14.0 installation folder. By default, the program is installed to %ProgramFiles%\Microsoft Visual Studio 14.0. In the root Visual Studio folder, locate the Common7\IDE\CommonExtensions\Microsoft\WebClient\Diagnostics\ToolWindows subfolder. In that folder, delete WebSocket4Net.dll.

Third-party information disclaimer

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top

Keywords: kbsurveynew, kbexpertiseadvanced, atdownload, kbgraphic, kb

↑ Back to the top

Article Info

Article ID	:	2996229
Revision	:	1
Created on	:	1/7/2017
Published on	:	1/8/2015
Exists online	:	False
Views	:	71

Microsoft KB Archive Search

Visual Studio 2015 Preview fixed bugs and known issues

Visual Studio 2015 Preview fixed bugs and known issues

Visual Studio 2015 Preview details

Requirements

Restart requirement

Supported architectures

Third-party applications