Visual Studio 2015 fixed bugs and known issues

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

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

We recommend you install the latest Visual Studio 2015 Update, you can see the known issues for Visual Studio 2015 Update 3.

Visual Studio 2015 details

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

For a list of Windows 10 SDK and Tools known issues, see the Known Issues for Windows SDK and Tools forum.

Fixed bugs

Profiler
  • The Diagnostic Tools window shows the message "The Diagnostic Tools failed unexpectedly" with "A cluster resource failed" or "Unable to Start Standard Collector" in the Diagnostics Hub output in the Output window.
  • UI delay occurs in Visual Studio when the Diagnostic Tools window is open.
Team Foundation Server (TFS)
  • The Publish fails with error message "date is not within permissible limits" when you use TFS in Turkish.
  • Distributed Test Automation and Cloud Load Testing tasks fail when project collection or project name has a space.
Others
  • Windows 8.1 acquisition breadcrumb template does not display after you install Visual Studio 2015.
  • Create ClickOnce Publishing optional feature to obtain required Windows 8.1 SDK tools.
  • The information in the error message that about failing to add Application Insights is not comprehensive.

Known issues

Installation
  • Sign up now

    As part of the release of Visual Studio 2015, we have integrated several additional connected experiences into the product. Many of these experiences require an account to connect to a service, and Visual Studio offers embedded credential prompting for either Microsoft Accounts or Work or School Accounts. As part of the Microsoft Account workflow, you can create an account directly from Visual Studio by clicking the "Sign up now" link. This is next to the "Don't have a Microsoft account?" text. Currently, there is a known issue that affects this link. You may notice this issue in either of the following ways:
    • The link may return a 404 (content not available) error page.
    • You may be correctly taken to a form that let you create a Microsoft Account. However, when you complete that form, you might find that you are not signed in.
    If you encounter a 404 error, you can create an account in your browser at the following website:

    After you create the account, you can sign in to Visual Studio by using the user name and password of the Microsoft Account that you created.

    If the sign-in dialog box closes after you complete the “Create an account” form, you must still sign in even though the account actually was created. To do this, reopen the dialog box, and then enter your credentials to correctly sign in to the account.

    These issues are scheduled to be fixed in the future.
  • The installation of Visual Studio 2015 on Windows 8.1 or Windows Server 2012 R2 fails when you do not install the update KB 2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update: April 2014. For more information see Visual Studio 2015 System Requirements.

    You can verify that KB2919355 is installed on your computer by going to Control Panel > Programs and Features > View Installed updates and looking for "Update for Microsoft Windows (KB2919355)."
    If you cannot find the KB2919355 update installed on your computer, you can check through Windows Update.

    Note KB2919355 itself has other prerequisites that must be installed first. Therefore, you may have to "Check for Updates" on Windows Update and install the offered updates multiple times in order to be fully up-to-date.
  • If you do not set the Windows Update option to automatically update the root certificates, and you choose to install optional components, you receive the following Visual Studio setup warning at the end of the process:
    PowerShell Tools for Visual Studio: This product did not download successfully: Signature verification failed on downloaded file.
    If the automatic update is turned off, your computer will not have the latest root certificates. Therefore, Visual Studio setup will not recognize the certificates that are used to sign the VSIX files as valid certificates and will not install the components.

    Workaround

    To work around this issue, turn on the automatic update for root certificates by following these steps:
    • Open the Run dialog box by pressing Windows logo key+R.
    • Run Gpedit.msc.
    • Locate Local Computer Policy > Administrative Templates > System > Internet Communication Management > Internet Communication settings > Turn off Automatic Root Certificates Update.
    • Select Disabled or Not configured to turn on the option.
    • Force a Windows Update to obtain the latest root certificates.
  • The AdminDeployment.xml file is not included in Setup.

    Workaround
    You can create the AdminDeployment.xml file by using the /CreateAdminFile <file location> command-line parameter.
  • Sometimes, items that users include as selected in the AdminDeployment.xml file are not installed.

    Workaround
    Add the items that are marked "Selected="yes"" at the end of the AdminDeployment.xml file.
Visual Studio IDE
  • Azure subscriptions cannot not appear in Visual Studio automatically if you are not a member of an Azure Active Directory that contains the subscriptions.
  • When you try to insert snippets from the XAML Editor, you receive an empty list instead of the snippet that is added for the XAML language.

    Workaround
    • Copy "C:\Program Files (x86)\Microsoft Visual Studio 14.0\DesignTools\Snippets\SnippetsIndex.xml" to C:\Program Files (x86)\Microsoft Visual Studio 14.0\DesignTools\Snippets\XAML"
    • Create a new snippets folder in "C:\Program Files (x86)\Microsoft Visual Studio 14.0\DesignTools\Snippets\XAML\1033\"
    • Copy C:\Program Files (x86)\Microsoft Visual Studio 14.0\DesignTools\Snippets\XAML\1033\Tag.snippet" to "C:\Program Files (x86)\Microsoft Visual Studio 14.0\DesignTools\Snippets\XAML\1033\Snippets"
  • Microsoft Visual Studio 2015 crashes with a System.UnauthorizedAccess exception

    Symptoms
    A dialog box randomly pops up with "Microsoft Visual Studio 2015 has stopped working". Expand problem details and scroll to Signature 09 points, you can see the System.UnauthorizedAccess exception.

    Workaround
    Give the current user full control permission to the "%tmp%\VSRemoteSettings" folder:
    • Open Windows Explorer and type %tmp% in the location bar to go to the temp directory.
    • Select the "VSRemoteSettings" folder and press and hold Properties.
    • Go to the Security tab and then click Edit.
    • Click Add… on the resulting Permissions dialog box.
    • Type your username and then click Check Names to check that it’s correct. Click OK.
    • Select your user name in the list and check the Full control check box in the list of permissions. Click OK to close the Permissions dialog box.
    • Click OK to close the Folder Properties dialog box.
Testing Tools
  • Cannot enable debugging of a Visual C++ Managed Test Project.

    Workaround

    To Work around this issue, visit the Tools->Options->Debugging->General pane, and cancel the selection for Enable Just My Code option.
  • The Visual C++ Unit Test Application (Windows Phone Silverlight 8.0) project will not build when you retarget the project Windows Phone Silverlight 8.1 by using Retarget Project.
  • Coded UI Test Projects for Windows Store and Windows Phone are available but do not work in Professional Edition.
    Coded UI should not be available in Professional Edition.
Web Platform and Tools
  • Cannot add service reference to WCF service in Visual Studio 2015.

    Symptoms

    When this issue occurs, you can receive the following error message:
    Error: Could not load file or assembly 'Microsoft.Owin.Security, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

    Workaround

    To work around this issue, cancel the selection for Reuse types in referenced assemblies option in Service Reference->Advanced (this behavior is turned on by default).
  • Warning occurs even though the build for a project that contains Azure API App Client is successful.

    Symptoms

    The build is successful. However, you receive the following error message:
    Consider app.config remapping of assembly "Newtonsoft.Json, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed" from Version "4.5.0.0" [] to Version "6.0.0.0" [] to solve conflict and get rid of warning.
    C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1819,5): warning MSB3276: Found conflicts between different versions of the same dependent assembly. Please set the "AutoGenerateBindingRedirects" property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190.

    Workaround

    To work around the issue, add binding redirects to your application's config file (App.config or Web.config) according to the following method:
    <runtime><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" /><bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" /></dependentAssembly><dependentAssembly><assemblyIdentity name="System.Net.Http.Primitives" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" /><bindingRedirect oldVersion="0.0.0.0-4.2.28.0" newVersion="4.2.28.0" /></dependentAssembly></assemblyBinding></runtime>
  • When you use the Typical installation of Visual Studio 2015 Professional or Visual Studio 2015 Community Edition, the LocalDB component is not installed.

    Symptoms

    If you select the Individual Authentication option with the ASP.NET project templates, and try to register a user by pressing F5, you receive the following SqlException error message at runtime:
    Cannot find the Local Database Runtime installed

    Workaround

    To work around this issue, repair the installed SKU to enable the "Microsoft SQL Server Data Tools" option.
  • ASP.NET 5: On Windows 7 SP1, DNX SDK cannot be installed without Powershell 3.0.

    Symptoms

    When you create an ASP.NET 5 project, you receive the following error message:
    DNX SDK version 'dnx-clr-win-x86.1.0.0-beta5' failed to install. The solution will use DNX SDK version 'dnx-clr-win-x86-1.0.0-beta5' for this session

    Workaround

    To work around this issue, install Windows Powershell 3.0 and try to create the project again.
  • ASP.NET 5: Cannot load all the references in Solution Explorer when you create a new ASP.NET 5 Web Application project or open an existing one on a virtual machine.

    Workaround

    To work around this issue, restart Visual Studio and reopen the project, references load correctly.
  • ASP.NET 5: The publish operation works incorrectly when the Use Powershell script option is not checked in the Settings tab of the Publish dialog.

    Symptoms

    Assume that you use the Host in the Cloud option when you create a new ASP.NET 5 application. When you publish the project to Azure, and the Use Powershell script option is not selected in the Settings tab of the Publish dialog box, the publish operation works incorrectly.

    Workaround

    To work around this issue, select the Use Powershell script option in the Settings tab of the Publish dialog box.
  • ASP.NET 5: When you add a package by using Bower in the bower.json file of an empty ASP.NET 5 application, the Dependencies node indicates that the package is not installed even though the package is successfully installed by using Bower.

    Workaround


    To work around this issue, close and reopen the solution, and the Dependencies node can select the new package.
  • ASP.NET 5: When you open an ASP.NET 5 beta 4 project by using Visual Studio 2015 RTM, and the project is created by Visual Studio 2015 RC, you receive the following error message:
    The process cannot access the file '...\project.lock.json' because it is being used by another process.

    Note This is an issue in the ASP.NET 5 beta 4 runtime. It is exposed by Visual Studio 2015 RTM tooling, and this issue is fixed in ASP.NET 5 beta 5.

    Workaround

    To work around this issue, close and reopen the solution.
  • ASP.NET 5: When you build and run an ASP.NET 5 beta 4 Web Application project in Visual Studio 2015 RTM, and the project is created by Visual Studio 2015 RC, you receive the following error message:
    app.UseBrowserLink()" in Startup.cs :
    Could not load file or assembly 'Microsoft.AspNet.Http.Abstractions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

    Workaround

    To work around this issue, comment out the line "app.UseBrowserLink()" or update your project to beta 5.
  • ASP.NET 5: When you search for References by using the Search functionality in Solution Explorer, Visual Studio 2015 stops responding in some cases.

    Workaround

    To work around this issue, expand the nodes in the References tree instead of using Search functionality.
  • When you debug a Windows Workflow Project, the debug break points cannot be hit as expected when the Suppress JIT optimization on module load (Managed only) option is not check.

    Workaround

    To make sure all the debug break points are hit as expected, check the Suppress JIT optimization on module load (Managed only) option in Tools-> Options-> Debugging-> General pane.
Release Management
  • Reconfigure of existing deployer (that is auto-updated to VS2015) does not work when you upgrade the Release Management Server to Visual Studio 2015 RTM.

    Workaround

    To work around this issue, uninstall Microsoft Deployment Agent from the deployer and reinstall the latest Microsoft Deployment Agent for Visual Studio 2015.
  • Release Management shows "license expired" within 90 days of upgrade, unexpectedly. This issue occurs after you upgrade to Visual Studio 2015 RTM by using the packages downloaded from visualstudio.com or downloads.microsoft.com

    Workaround

    To work around this issue, download Release Management for Visual Studio 2015 from your MSDN subscription and upgrade again.
Diagnostic Tools
  • When you run the Diagnostic Tools without Debugging targeting any of the following:
    • Windows Phone 8.1 applications that set the build configuration to Release.
    • Windows Store applications that are NGEN'ed (This happens automatically after a day).
    • C++ Universal Windows Projects that set the build configuration to Debug mode.
    • C++ projects running on Windows 7.
    The CPU Usage and Memory Usage tools will not display function names for code in your application.

    Workaround

    For Windows Phone 8.1 applications, set the build configuration dropdown on the standard toolbar from Release to Debug.
    For Windows Store applications, make a change to the application and then recompile.
    For C++ Universal Windows applications, set the build configuration to Release. If Debug mode is desired, you can change Configuration Properties -> Debugging -> Generate Debug Info in project settings from "Optimize for faster linking (/DEBUG:FASTLINK)" to "Optimize for debugging (/DEBUG)".
    For C++ projects on Windows 7, click "Create Detailed Report…" and view function names in the detailed report instead.
Application Insights
  • Cannot add Application Insights to an existing Windows 8.1 project or Universal Windows project, it does not add a configure file. The SDK Package is installed into the project, but Application Insights does not work.

    Workaround

    Add an existing ApplicationInsights.config from another project (or create one by hand), set "BuildAction=Content" & "Copy to Output=Copy If Newer", and then follow the normal Add to existing project flow: Open Project context menu and then click "Configure Application Insights…"
    If you add a new project by hand, make sure that you do the following:
    • Name the file "ApplicationInsights.config"
    • Add the following content:
      <ApplicationInsights xmlns="http://schemas.microsoft.com/ApplicationInsights/2013/Settings"></ApplicationInsights>

NuGet 3.0
Note NuGet 3.0 add the support for project.json files, new JSON-based protocol, and updated support for new target frameworks. For more information, see NuGet 3.0 release notes.
  • Translation is not provided for the "Do not show this again" label on the preview window and the "Authors" label in the package description window.

    Workaround

    Install the updated NuGet package manager from the extension gallery.
  • When you working on a project by using TFS source control, NuGet cannot present the package manager user interface if the nuget.config file is marked as read-only.

    Workaround
    • Check out the file from TFS.
    • Install the updated NuGet package manager from the extension gallery.
  • Text in the yellow "restart bar" in the NuGet Powershell window is not visible when you use the Visual Studio dark theme.

    Workaround
    • Use the Visual Studio light theme.
    • Install the updated NuGet package manager from the extension gallery.
Cordova and JavaScript
  • In certain install scenarios after you install the tools for Universal Windows applications, the JavaScript language service and project system can be uninstalled. This can result in the following issues:
    • Visual Studio will freeze when you create a new Cordova project.
    • Visual Studio will display a package load failure when you create a new JavaScript-based Universal Windows application project.
    • When you edit a JavaScript file, IntelliSense will not work.
    • When you debug a JavaScript-based Universal Windows application, you receive the following error message:
      The debugger cannot continue running the process.  Unable to start debugging.

    Workaround:
    • Make sure your computer has an internet connection, and
      • If the Tools for Universal Windows Apps Development are still installed:
        1. Go to Programs and Features, select Visual Studio 2015, click Change.
        2. In Visual Studio setup, click Modify.
        3. Deselect the feature Tools for Universal Windows App Development.
        4. Select Tools for Universal Windows App Development again, and click Update.
      • If you have already uninstalled the Tools for Universal Windows Apps Development:
        1. Reinstall Tools for Universal Windows App Development.
        2. Or, take the following steps to reinstall the JavaScript project system and language service:
          • Download the installer for your edition of Visual Studio, such as, vs_community.exe.
          • Open a command window, and run the following command: 
            vs_community.exe /modify /installselectableitems JavaScript_Hidden /passive
          • Change directories to C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE.
          • Run the following commands
            • devenv /updateconfiguration
            • devenv /clearcache
Others

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.

Software requirement

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

Supported architectures

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

Third-party applications


  • Visual Studio 2015 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 , check out KB Article 3060693.
  • Visual Studio 2015 uninstall does not uninstall the third-party applications. For information on how to uninstall third-party applications that installed with Visual Studio 2015, check out KB Article 3060695.
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.
Properties

Article ID: 3025135 - Last Review: 07/21/2016 03:37:00 - Revision: 13.0

Visual Studio Community 2015, Visual Studio Professional 2015, Visual Studio Enterprise 2015, Visual Studio Express 2015 for Desktop, Visual Studio Express 2015 for Web, Visual Studio Express 2015 for Windows 10

  • kbsurveynew kbexpertiseadvanced atdownload KB3025135
Feedback