Team Foundation Server 2015 Update 2 RC 2 Known Issues and Fixed Bugs

Visual Studio 2015
 

Microsoft released Team Foundation Server 2015 Update 2 RC 2 on March 3, 2016. This article lists the known issues and fixed bugs for Team Foundation Server 2015 Update 2 RC 2.

To see the full list of Team Foundation Server 2015 products and download a product, go to the VisualStudio.com Downloads page.

To discover what's new in Team Foundation Server 2015 Update 2 RC 2, see the Team Foundation Server 2015 release notes.

Download the latest Team Foundation Server 2015 update package now.

This section describes some bugs that are fixed in Team Foundation Server 2015 Update 2 RC 2.

Release Management

  • Issue: Users who have Advanced-level access can access all features in the Release hub. Users who have Basic-level access can create releases and deploy them but can't create or edit release definitions. Stakeholders can only view a summary of releases and approve or reject them.

  • Issue: Releases contain incorrect links to artifacts.

  • Issues that are related to deployments are rejected after they're started. In addition to correcting one possible reason for this, we now report additional information that relates to the failure in the Issues section of a release.

  • Issue: An incorrect release number is displayed on the overview page when a pre-deployment approval is pending.

TFS web access extensions

  • Issue: If you use TFS web access extensions and you upgrade to TFS 2015 Update 2, you may see some issues that affect your extension. This occurs because JavaScript file locations are changed on the TFS server.

    Workaround: To work around this issue, the extensions have to be updated to be able to access the new location (<TFSInstallPath>\Application Tier\Web Services\_static\tfs\Dev14.M95\_scripts\TFS\debug). If you use the Multi-Value control, a new version is available here.

Testing tools

  • Issue: The Tests tab in the Build summary shows the test status (total, passed, failed) for tests that were run in the build. However, the listed tests do not match the test statuses if the tests were run against the same build in Release environments. In addition to test results from the build, test results are displayed on the Tests tab in the build.

    Workaround: To work around this issue, provide an appropriate name for the test run and group tests by test run to view test results from the build. Run title field is available in the Reporting options section in the Visual Studio Test task. Browse the Tests tab Release summary to view test results from the release.

  • Issue: Delete Test Plan does not work in the Test hub:

    On the Tests tab (in web access), you cannot delete a test plan by using the content menu option or by clicking the Delete icon.

    Workaround: After you apply TFS 2015 Update 2 RC2, you can use the "witadmin destroywi" admin tool to delete the test plan. This issue will be fixed in the RTM version of the product.

  • Issue: Intellitrace and TestImpact data collectors do not work in MTM in TFS 2015 Update 2 RC2:

    When you run a manual test case in Microsoft Test Runner and you have configured IntelliTrace or TestImpact data collectors to collect diagnostic data, the data collection causes errors or exceptions when a bug is filed or a session ends. All other information about the test run is saved correctly.

    Workaround: This issue occurs because the Microsoft.DiaSymReader.dll is missing from the "VS Test Professional 2015 U2 RC2" package. You have to copy this DLL from any "VS Enterprise 2015 U2 RC2" computer to the "%programfiles%\Microsoft Visual Studio 14.0\Common7\IDE\PrivateAssemblies" folder. After you copy the file, restart MTM to fix the problem.

    If you do not have a "VS Enterprise 2015 U2 RC2" computer, you can call Microsoft Customer Support to obtain this DLL at no additiional charge.

  • Issue: Code Coverage data collection for .NET code has the following known limitations:

    • Navigating to code does not work when Code Coverage data collection is done together with tools that do IL rewriting (for example, Code Contracts).

    • Code Coverage data collection for .NET code can't be usedtogether with Fakes.

    • Code Coverage data collection can't be used when the tests are run in parallel.

TFS Build

  • Issue: The XAML builds don't run because of connectivity issues in the build controller. This issue occurs because WCF Services don’t have the required HTTP activation installed on the TFS application tier.

    Workaround: To work around this issue, run the following command on your application tier:

    dism /Online /Enable-Feature /FeatureName:WCF-HTTP-Activation45 /all

How to download Microsoft support files

Updates for other products in the Team Foundation Server family can be found on the VisualStudio.com Downloads website.

Requirement

For detailed system requirements, see the TFS requirements and compatibility page.

Restart requirement

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

Software requirement

To apply this update, you must have Team Foundation Server 2015 installed on your computer.

Supported architectures

  • 32-bit (x86)

  • 64-bit (x64) (WOW)

Applies to

  • Team Foundation Server 2015

  • Team Explorer Everywhere 2015

  • Team Foundation Server Express 2015

  • Team Foundation Server for Project Server Extensions 2015

System_CAPS_ICON_caution.jpg Caution

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.

Show: