Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Visual Studio 2015 RC fixed bugs and known issues


Visual Studio 2015 RC fixed bugs and known issues

This article lists the fixed bugs and known issues for the Microsoft Visual Studio 2015 Release Candidate (RC).

Visual Studio 2015 RC is a release candidate for the next major release of Visual Studio. The Visual Studio 2015 RC products offered on this page are “go-live.” This means that customers can use these builds in production environments. These are still prereleases, so there may be some bugs that will be fixed for the final release.

To see the full list of Visual Studio 2015 RC products and to select a product for download, check out Visual Studio Downloads.

↑ Back to the top


Visual Studio 2015 RC details

To discover what is new in Visual Studio 2015 RC, see the Visual Studio RC release notes.
 
Known issues
Installation
Before you install
  • During Visual Studio 2015 RC Setup, if you select a non-Windows drive on which to install Visual Studio, most of the program is still installed to the system drive. Only a small part of the program is installed to the non-Windows drive.
  • Remove Visual Studio Tools for Windows 10 Insider Preview before you install Visual Studio 2015 RC. If you have installed Visual Studio 2015 CTP6 and the Visual Studio Tools for Windows 10 Insider Preview, you must uninstall Tools for Windows 10 before you install Visual Studio 2015 RC.
  • When you install Visual Studio 2015 RC on a computer that is running Windows 7 SP1, the authenticode certificate in the Dotfuscator installer fails to verify whether the computer is disconnected from the Internet.

    To work around this issue, use one of the following methods:
    • Click Skip Package when this issue occurs to skip the Dotfuscator installation. Visual Studio 2015 Setup will continue as usual. However, Dotfuscator will not be installed.
    • Connect the computer to the Internet.
Upgrading from previous releases
  • When you install Visual Studio 2015 RC, you do not see the progress bar move for some time in the Progress dialog box. Therefore, you might think that Visual Studio Setup is not responding.

    To work around this issue, use Task Manager to examine the activity behind the setup interface. Look for processes that are using lots of network bandwidth or hard disk time. Setup programs typically use lots of network bandwidth to download packages and lots of hard disk time to decompress and copy files. If programs have installation-related names, you can see the work occurring even though it is not sent to the setup interface. If these programs do not resemble installation programs, they could be competing with Setup for use of these computer resources.
  • When you upgrade from Visual Studio 2015 CTP to Visual Studio 2015 RC, the shortcuts for Microsoft Test Manager 2015 CTP and Feedback client 2015 CTP are not removed. However, the shortcuts for the RC counterparts are added. You can safely delete the shortcuts from CTP to avoid confusion. If you choose instead to ignore the CTP shortcuts, no functionality is lost because the CTP shortcuts also open the RC version of the product.
  • Assume that you upgrade to Visual Studio 2015 RC from a Visual Studio 2015 version. You select either the Typical or Custom installation type. After the upgrade, you may find that some features in the earlier Visual Studio version are not present in Visual Studio 2015 RC.

    To work around this issue, follow these steps:
    1. In Control Panel, open the Programs and Features item before you start the RC installation.
    2. Click the entry for the earlier Visual Studio 2015 release, and then click Custom.
    3. In the maintenance mode dialog box, click Modify.
    4. Note the selected check boxes in the UI.
    5. In the RC installation, click Custom.
    6. Use you notes to match the check box selections for the earlier release.
  • When a Visual Studio 2013 deployment agent is automatically upgraded to work against Visual Studio 2015 RC server, and the deployment agent is enabled to use Through Release Management Server over HTTP(s) for copying the components, you may experience one of the following issues:
    • Your release may fail at Deploy step and you receive the following error message:
      Could not load file or assembly 'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
    • The following error is logged in the event viewer log on deployment agent computer:
      Timestamp: <DateTime>Message: Could not load file or assembly 'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040): \r\n\r\n at Microsoft.TeamFoundation.Release.Data.Proxy.RestProxy.BaseDeploymentControllerServiceProxy.GetPackageFileInfos(String packageLocation)
      at Microsoft.TeamFoundation.Release.DeploymentAgent.Services.Deployer.HttpPackageDownloader.CopyPackageAndUnpackIt(String packageSourceLocation, String filesDestinationLocation)
      at Microsoft.TeamFoundation.Release.DeploymentAgent.Services.Deployer.ComponentProcessor.CopyComponentFilesImplementation(Action`2 copyFolder, Func`2 packageFileInfo, Func`4 downloadFile, Action`1 downloadCompleted)
      at Microsoft.TeamFoundation.Release.DeploymentAgent.Services.Deployer.ComponentProcessor.CopyComponentFiles()
      at Microsoft.TeamFoundation.Release.DeploymentAgent.Services.Deployer.ComponentProcessor.DeployComponent()Category: General
      Priority: -1
      EventId: 0
      Severity: Error
      Title:
      Machine: NVM30682
      Application Domain: DeploymentAgent.exe
      Process Id: 4668
      Process Name: C:\Program Files\Microsoft Visual Studio 12.0\Release Management\bin\DeploymentAgent.exe
      Win32 Thread Id: 4876
      Thread Name:
      Extended Properties:


    To work around these issues, use one of the following methods:
    • Option 1:

      Copy Newtonsoft.Json.dll from any Visual Studio 2015 RC deployment agent to Visual Studio 2013 upgraded agent and restart Microsoft Deployment Agent service.

      Source path on Visual Studio 2015 RC deployment agent: "%ProgramFiles(x86)%\Microsoft Visual Studio 14.0\Release Management\bin\Newtonsoft.Json.dll" or "%ProgramFiles%\Microsoft Visual Studio 14.0\Release Management\bin\Newtonsoft.Json.dll" (according to the location of the deployment agent is installed).

      Destination path on Visual Studio 2013 deployment agent: "%ProgramFiles(x86)%\Microsoft Visual Studio 14.0\Release Management\bin\Newtonsoft.Json.dll" or "%ProgramFiles%\Microsoft Visual Studio 14.0\Release Management\bin\Newtonsoft.Json.dll" (according to the location of the deployment agent is installed).
    • Option 2:
      1. Uninstall the existing Visual Studio 2013 deployment agent.
      2. Install Visual Studio 2015 RC deployment agent.
After you install
  • After a successful installation of Visual Studio, you may receive the following message when you try to start up Visual Studio:
    Install operation did not finish successfully. Please reinstall or repair Visual Studio
    To work around this issue, find the following key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\14.0\Setup\VS\[enterprise | professional | community]
    If the value for InstallResult is 3010, change it to 0. Otherwise, perform a repair of the product as requested.
  • If you choose to repair Visual Studio Test Professional installation as part of your install or repair process, you receive the following error message in a dialog box:
    VSTestConfig.exe has stopped working
    You can safely ignore this error message because it does not impact the repair operation. Click Close the program to resume the repair operation. If you encounter any issues with Microsoft Test Manager post repair, reach out to customer support.
Issues that affect installing from an ISO
  • Assume that you install Visual Studio 2015 RC from an ISO file, and then you select the Apache Cordova tools. After you repair Visual Studio, a dialog box appears and asks for the source for JSBreadcrumbRes.msi. If you skip the package, Setup will complete and return a "Tools for Apache Cordova - Templates. The system cannot find the file specified" warning message.

    To work around this issue, select Skip package during the repair. The package is not necessary, and the warning can be safely ignored.

    For more known issues that are related to Visual Studio Tools for Apache Cordova, see Tools for Apache Cordova Known Issues.
  • Visual Studio Setup file includes features that are not contained in the ISO file. To enable the acquisition of the latest versions of new platform features, and to enable more customization of your Visual Studio installation to minimize the installation time and size, Visual Studio Setup includes features that are not included in the ISO files.

    To work around this issue, create a folder with the files necessary for an offline install experience:
    1. Save the Visual Studio installer to your local computer.
    2. At a command prompt, run the .exe file by using the /layout switch. For example, run the following command:
       
      
      vs_community.exe /layout 
    3. Specify the folder to which the setup files should be downloaded. For example, specify the following folder:
       
      c:\Users\YourName\Downloads\VSCommunity
    4. After the download is complete, run the .exe file from the specified folder location. For example, open the VSCommunity folder in your Downloads library, and run Vs_community.exe.

    Note Because of an issue in the RC release, the /layout download option does not download all the software that is required by some Visual Studio features. Some components require an Internet connection to install.
  • After a successful installation of Visual Studio, you may receive the following message when you try to start up Visual Studio:
    Install operation did not finish successfully. Please reinstall or repair Visual Studio
    To work around this issue, find the following key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\14.0\Setup\VS\[enterprise | professional | community]
    If the value for InstallResult is 3010, change it to 0. Otherwise, perform a repair of the product as requested.
Windows App Development Tools
  • To install the development tool for Windows 10 universal applications in Visual Studio Setup, click Custom, click Next, and then select the Windows Universal App Development Tools feature. Windows 10 Insider Preview no longer uses a separate installer.
  • The Windows Emulators require a physical computer that runs Windows 8.1 (x64) Professional edition or a later version and a processor that supports Client Hyper-V and Second Level Address Translation (SLAT). The emulators do not run when Visual Studio is installed in a Virtual Machine (VM).
Miscellaneous Issues
  • When you install Visual Studio 2015 RC, after you click Cancel and Yes in the Progress dialog box, the Progress bar continues for a long time.

    If you wait, the cancellation request is respected at the next package transition. However, this can take many minutes. Wait for the current processing to end in the usual manner to make sure that you have the best possible partial installation.

    If you must stop Setup immediately, you can use Task Manager to locate and end the setup process task.

    Warning This may the put the final setup operation into an indeterminate state. If you choose to terminate an installation before it is completed, we recommend you restart Setup as soon as it is convenient, and then either repair the installation or uninstall the program.
Visual Studio IDE
  • If you have disabled JavaScript in Internet Explorer, you cannot sign in to Visual Studio and sync settings together with other devices.

    To work around this issue, enable JavaScript for Internet Explorer. To do this, follow these steps:
    1. On the Tools menu, click Internet Options, and then click the Security tab.
    2. Click the Internet zone.
    3. If you do not have to customize your Internet security settings, click Default Level. Then, go to step 4. If you have to customize your Internet security settings, follow these steps:
      1. Click Custom Level.
      2. In the Security Settings – Internet Zone dialog box, click Enable for Active Scripting in the Scripting section.
    4. Click the Back button to return to the previous page, and then click the Refresh button to run scripts.
    For more information, see How to enable JavaScript in a web browser.
  • When you enable Enhanced Security in Internet Explorer, you cannot sign in to Visual Studio on Windows Server because Enhanced Security blocks the online service URI that is required by Visual Studio to sign in to the online service. Restrictions that disable JavaScript or cookies also prevent Visual Studio from signing in correctly.

    To work around this issue, click Add to add the required URLs into the Windows Server exclusion list if you see the following dialog box.
    Add


    Then, restart Visual Studio and try to sign in again.

    Another workaround is to turn off Internet Explorer Enhanced Security Configuration.
  • C++ and JavaScript applications that are referencing a managed Windows Runtime Metadata (.winmd) file is not optimized by having .NET Native because .NET Native is not enabled for those projects. To enable .NET Native, you must modify the JSProj or VCXProj file.

    To work around this issue, use one of the following methods:
    • For C++ applications:
      1. Close the project that you want to modify.
      2. Open the VCXProj file in a text editor.
      3. Find the PropertyGroup element that does not contain a Condition attribute.
      4. Add "<EnableDotNetNativeCompatibleProfile>true</EnableDotNetNativeCompatibleProfile>" in the PropertyGroup element.
      5. Find the PropertyGroup elements that contain Condition="'$(Configuration)|$(Platform)'=='Release|<arch>'" for which <arch> is Win32, ARM, or x64.
      6. Add "<UseDotNetNativeToolchain>true</UseDotNetNativeToolchain>" inside each PropertyGroup element.
      7. Save the VCXProj file.

       
    • For JavaScript applications:
      1. Close the project you want to modify.
      2. Open the JSProj file in a text editor.
      3. Find the PropertyGroup element that does not contain a Condition attribute.
      4. Add "<EnableDotNetNativeCompatibleProfile>true</EnableDotNetNativeCompatibleProfile>" in the PropertyGroup element.
      5. Find the ProjectConfiguration elements that contain Include="Release|<arch>" for which <arch> is ARM, x64, or x86.
      6. Add "<UseDotNetNativeToolchain>true</UseDotNetNativeToolchain>" inside each ProjectConfiguration element.
      7. Save the JSProj file.
  • The AnyCPU platform configuration is not supported for Windows 10 Insider Preview applications that are built by using C# and Visual Basic. This release of Visual Studio uses the .NET Native to build Windows 10 applications. The .NET Native compiles C# and Visual Basic code to native code and is not CPU-agnostic.
  • When you debug C# or Visual Basic Windows 8.1 applications, DataTips might not be displayed when you hover over expressions. Also, evaluating expressions in debugger windows may fail and return an error message that resembles the following:
     
    error CS0012: The type 'Windows.UI.Core.Dispatcher’ is defined in an assembly that is not referenced. You must add a reference to assembly 'Windows.UI.winmd, ...

    To work around the issue, enable the legacy C# and VB expression evaluators.
    nable the legacy C# and VB expression evaluators

     
  • Static Code Coverage files are not collected if you use Visual Studio 2013 agents that are configured against Visual Studio 2015 or TFS 2015 and if you receive the following error message:
     
    System.DllNotFoundException: Unable to load DLL 'VSCover 140': The specified module could not be found. (Exception from HRESULT:0x8007007E)

    Note
    This issue occurs only when you are running tests on a remote computer and you try to collect static code coverage data.
  • When you reference a portable class library in a project, some operations may cause errors that are reported in the Visual Studio Error List, even though build succeeds.

    To work around this issue, follow these steps:
    1. Right-click the project in which the errors are reported in Solution Explorer, and then click Unload Project.
    2. Right-click again on the project in Solution Explorer, and then click Edit <ProjectName>.

      Note In this command, <ProjectName> represents the actual project name.
    3. In the <PropertyGroup> entry at the top of the project file that has no Condition attribute, add the following:
       
      <CheckForSystemRuntimeDependency>true</CheckForSystemRuntimeDependency>
    4. Save and close the file.
    5. Right-click the project name in Solution Explorer, and then click Reload Project.


Web platform and Tools
  • In Visual Studio 2015 RC, you cannot configure your build settings when you use TypeScript in an ASP.NET 5 or Cordova project.

    To work around this issue, follow these steps:
    1. Right-click the project, and then click Unload project.
    2. Right-click the project, and then click Edit <Project>.

      Note In this command, <Project> represents the actual project name.
    3. In the XML file for your project, you can define the MSBuild settings that are used by the TypeScript editor by following these guidelines:
    The following is an example of the MSBuild settings that you can configure in the project file:
     
    
    <PropertyGroup>
        <TypeScriptTarget>ES5</TypeScriptTarget>
        <TypeScriptCompileOnSaveEnabled>true</TypeScriptCompileOnSaveEnabled>
        <TypeScriptNoImplicitAny>false</TypeScriptNoImplicitAny>
        <TypeScriptModuleKind>none</TypeScriptModuleKind>
        <TypeScriptRemoveComments>false</TypeScriptRemoveComments>
        <TypeScriptOutFile></TypeScriptOutFile>
        <TypeScriptOutDir></TypeScriptOutDir>
        <TypeScriptGeneratesDeclarations>false</TypeScriptGeneratesDeclarations>
        <TypeScriptSourceMap>true</TypeScriptSourceMap>
        <TypeScriptMapRoot></TypeScriptMapRoot>
        <TypeScriptSourceRoot></TypeScriptSourceRoot>
        <TypeScriptNoEmitOnError>true</TypeScriptNoEmitOnError>
      </PropertyGroup> 
    See the values for TypeScript MSBuild settings.

    For more known issues that are related to Visual Studio Tools for Apache Cordova, see Tools for Apache Cordova Known Issues.
  • In the Visual Studio 2015 RC, Project Spartan (desktop or mobile) is not displayed as a debug target in the F5 list for web-based projects such as ASP.NET.

    To work around this issue, change the default browser in Windows 10 Insider Preview from Project Spartan to Internet Explorer. To do this, open the Start menu, point to Settings, point to System, and then click Default Apps. Under Web browser, click Project Spartan, and then click Internet Explorer.
  • Web Essentials CTP version is not disabled when you upgrade to Visual Studio 2015 RC. Older versions of Web Essentials are expected to be disabled when Visual Studio upgrades are installed, however, this mechanism is broken in Visual Studio 2015 RC. No incompatibilities with Web Essentials for CTP6 in Visual Studio 2015 RC. We strongly recommend that you uninstall or upgrade versions of Web Essentials other than the Visual Studio RC version.
  • Knockout IntelliSense is disabled by default. Knockout IntelliSense does not work in Visual Studio 2015 RC until a .jsx file is opened. There is no item template for JSX, just add a JavaScript file and change its extension for .js to .jsx. The file can be opened, closed, and ignored. Opening the .jsx file will trigger the code necessary to make KnockOut features work as in previous releases.Installing Web Essentials for Visual Studio 2015 RC will fix this issue. Therefore, you do not have to open a JSX file.
ASP.NET and Web Development
  • When you create a Web Forms 4.5 WAP and open a Web Form page, you receive the following errors in the Errors List window:
     
    The project will run without any issues. Error CS0234 The type or namespace name 'global_asax' does not exist in the namespace 'ASP' (are you missing an assembly reference?)
    Error CS0234 The type or namespace name 'Linq' does not exist in the namespace 'System' (are you missing an assembly reference?)
  • Assume that you use new language features for C# and VB in Visual Studio 2015 RC. You receive a runtime error when you use C# or VB in a Web Form page or in Razor Views.

    To work around this issue, install Microsoft.CodeDom.Providers.DotNetCompilerPlatform NuGet package. This package will substitute the Roslyn-based provider for the in-box CodeDom providers for ASP.NET.
Agile testing
  • The Coded UI Test (CUIT) does not work for UAP Phone applications on Windows 10 Insider Preview.
  • VSTest task in Build.VNext does not upload test results to the TFS server. Instead, you can retrieve the test results from a .trx file that is stored on the execution computer.
Unit testing
  • The Run All command in the Test Explorer does not work when you try to run all tests for a Universal applications by having the deployment target set to a phone device or the emulator.

    To work around this issue, select all the tests in Test Explorer, and then run them on these deployment targets.
  • Debugging a unit test by having the deployment target set to a phone device or the emulator is not supported in Visual Studio 2015 RC.
  • When you run the Create Unit Tests command from the context menu, and then you run the Save command from the IntelliTest Exploration Results window, an Android Unit Test project is created.

    To work around this issue, follow these steps:
    1. Rename UnitTestProject.zip in "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Xamarin\Xamarin\[Version]\T\PT\Android" to UnitTestProject2.zip.
    2. Open the "Developer Command Prompt for Visual Studio 2015" as an administrator.
    3. Run the following command:

      
      devenv /InstallVSTemplates 
Visual Studio Tools for Windows 10 Insider Preview
  • The Visual Studio Tools for Windows 10 Insider Preview will be available soon. To check for availability, see https://insider.windows.com.
  • For known issues and installation instructions, see the Windows App Development Forums.
  • Express for Windows 10 Does Not Support Windows 8.1, Windows Phone 8.1, or Windows Phone 8.0. Although this RC release of Visual Studio Express 2015 for Windows 10 includes support for creating and maintaining apps for Windows 8.1, Windows Phone 8.1, and Windows Phone 8.0, the final release of Visual Studio Express 2015 for Windows 10 will not.

    To work around this issue: Use Visual Studio Community 2015 instead. Visual Studio Community, Visual Studio Professional, and Visual Studio Enterprise will continue to support Windows Store apps for Windows 8.1, Windows Phone 8.1, and Windows Phone 8.0.
Diagnostic Tools
  • When you start debugging for the first time, the Diagnostic Tools window fails to open, and you receive the following error message:
     
    The Diagnostic Tools failed unexpectedly

    However, the Diagnostic Tools window opens correctly in subsequent debugging sessions or after you restart Visual Studio.

    For more information about the tools, search on "Known Issues for Windows 10 SDK and Tools" at the following MSDN forums website:

     
Others
  • Source control may show some characters in Chinese instead of English. In order to fix this problem please do a Repair for Visual Studio 2015 RC in Program and Features.
  •  "Collection type must derive from ICollection<T>" error occurs when you execute some operations in the Visual Studio 2015 RC UI

    Assume that you upgrade from an earlier Windows 10 Preview Build to Flight 10122 or later versions. When you open, create projects, or perform other actions in Visual Studio 2015 RC UI, you receive the following error message: 
    Collection type must derive from ICollection<T>

    To repair this issue, use the following method:
    • Open a Visual Studio Developer command prompt as administrator.
    • Type devenv.exe /setup into the command prompt, and press Enter.
    • Repair Visual Studio.
Breaking changes
Cloud platform
  • Previously, you could version a Windows application by using four different numbers: major version, minor version, build version, and revision version. This version is specified in the AppxManifest.xml file. The revision number of Windows 10 Insider Preview applications is the fourth part of a x.x.x.x version string and is reserved for use by Microsoft use. Applications should always use "0" as the revision number. Windows App Certification Kit (WACK) and the Windows Store will reject an application that does not use a revision number of "0."
  • The .NET Native for Visual Studio 2015 no longer supports Windows 8.1 or Windows Phone 8.1 applications. Only Windows 10 Insider Preview applications are supported in this release and in future releases.
Agent
  • By using the Agents for Visual Studio 2015, you do not require a separate test controller because agents can handle the orchestration by communicating to the TFS 2015 or Visual Studio Online. In all the new Visual Studio 2015 and TFS 2015 scenarios, we recommend that you use Agents for Visual Studio 2015. For other Test Controller required scenarios, we recommend that you use Agents for Visual Studio 2013 Update 5. Test Controller is fully compatible with TFS 2013 and TFS 2015 products.

    The following table summarizes our recommendations.

     
    Remote automated testing via Build.Preview build system or Release Management Agents for Visual Studio 2015
    Remote automated testing via MSTest and .testsettings files
    Load testing
    Remote Automated testing via Lab environments
    Automation Tests targeting TFS 2013
    Agents for Visual Studio 2013 Update 5
Visual C++
  • The __declspec(align) struct is not allowed in functions in Visual Studio 2015 RC.
  • Exception objects have to be either copyable or movable. The following code compiles in Visual Studio 2013, but does not compile in Visual Studio 2015:
     
    
    struct S {
    public:
    S();
    private:
    S(const S &);
    };
     
    int main()
    {
    throw S(); // error
    }
     
    or
     
    struct S {
    S();
    explicit S(const S &);
    };
     
    int main()
    {
    throw S(); // error
    } 
  • Capturing the exception by value requires the exception object to be copyable. The following code compiles in Visual Studio 2013, but does not compile in Visual Studio 2015:
    
    struct B {
    public:
    B();
    private:
    B(const B &);
    };
     
    struct D : public B {
    };
     
    int main()
    {
    try
    {
    }
    catch (D) // error
    {
    }
    } 
  • The mutable specifier can be applied only to names of class data members(9.2). They cannot be applied to
    names that are declared const or static, and also cannot be applied to reference members. For example:
    
         class X {
           mutable const int* p; // OK
           mutable int* const q; // ill-formed
         }; 
    To work around this issue, simply remove the redundant "mutable" instance.
  • We used to generate a ctor or dtor for the anonymous union that is non-conformant in either C++03 or C++11. These are now deleted.
  • The non-trivial constructor is no longer invoked for any anonymous struct members within a union. For example:
    
    #include <stdio.h>
    struct S {
     ~S(){ printf("~S()");}
    };
    union U{
      struct {
       S s;
      };
      ~U(){}
    };
    int main()
    { 
      U u;
      return 0;
    } 
    In versions that are earlier than Visual Studio 2015 RC, the struct prints ~S(). After Visual Studio 2015 RC, it prints nothing. Additionally, you receive the following warning message:
     
    warning C4588: 'U::s': behavior change: destructor is no longer implicitly called
  • The type of the explicit non-type template argument should match the type of the non-type template parameter. However, Visual Studio 2015 RC sometimes fails to validate this. For example, the following code is no longer allowed:
    
    struct S2
    {
     void f(int);
     void f(int, int);
    };
    struct Sink
    {
     template <class C, void (C::*Function)(int) const> void f();
    };
    void f()
    {
     Sink sink;
     sink.f<S2, &S2::f>();
    } 
  • Data members of unions can no longer have reference types.
  • When you use the /Zc:forScope- command in Visual Studio 2015 RC, you receive the following warning message:
     
    cl : Command line warning D9035: option 'Zc:forScope-' has been deprecated and will be removed in a future release
  • Macros that immediately follow a string without any white space between the string and the macro are now interpreted as user-defined literal suffixes. For example:
    
    //Before compiled
    #define _x "there"
    char* func() {
      return "hello"_x;
    }
    int main()
    {
     char * p = func();
     return 0;
    } 
    When you compile the code, you receive the following error message:
     
    test.cpp(52): error C3688: invalid literal suffix '_x'; literal operator or literal operator template 'operator ""_x' not found
    test.cpp(52): note: Did you forget a space between the string literal and the prefix of the following string literal?
  • The non-trivial constructor is no longer invoked for any anonymous struct members within a union. For example:
     
    
    #include <stdio.h>
    struct S {
     S(){ printf("S()");}
    };
    union U{
      struct {
       S s;
      };
      U(){}
    };
    int main()
    { 
      U u;
      return 0;
    } 
    In versions that are earlier than Visual Studio 2015 RC, the struct prints S(). In Visual Studio 2015 RC, it prints nothing. Additionally, you receive the following warning message:
     
    warning C4587: 'U::s': behavior change: constructor is no longer implicitly called.
  • In Visual Studio 2015 RC, the implicitly-declared copy constructor is deleted if there is a user-defined move constructor or a move-assignment operator.
  • The concatenation of adjacent wide or raw string literals now requires 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. For example:
    • const wchar_t *s = L"Hello"L"World"; // emits error C3688: invalid literal suffix 'L'; literal operator or literal operator template 'operator ""L' not found
    • const wchar_t *t = L”Hello” L”World”; // compiles without error
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 website.

Requirements

For detailed system requirements, see Visual Studio 2015 Compatibility.
 

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 2015 RC install lets you install third-party applications. For information on which third-party applications are required when you install Cross Platform Mobile Development tools from Visual Studio 2015 RC, check out KB Article 3060693.
  • Visual Studio 2015 RC uninstall does not uninstall the third-party applications. For information on how to uninstall third-party applications that installed with Visual Studio 2015 RC, check out KB Article 3060695.
Third-party information disclaimer
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, kb

↑ Back to the top

Article Info
Article ID : 3025133
Revision : 4
Created on : 11/6/2017
Published on : 11/6/2017
Exists online : False
Views : 487