News

TFS 2015 Update 4 Preview Is All About Squashing Bugs

Team Foundation Server 2017 is out, but that doesn't mean there isn't important work to be done with TFS 2015. The VS team has released a preview of a TFS 2015 update that rolls up about 25 fixes for mostly customer-reported issues.

Even with Team Foundation Server 2017 now out with the release of Visual Studio 2017, the VS team continues to work on TFS 2015 improvements. Just last week, the group released a TFS 2015 Update 4 preview that rolls up with a slew of bug fixes.

"Update 4 only contains bug fixes," notes Microsoft's Brian Harry, in a short blog about it. "It has about 25 bug fixes, all or most of which, have been reported by customers. They were all selected because they seemed likely enough and problematic enough to warrant issuing a proactive fix."

The release notes categorize the bug fixes by the following types: agile, version control, build, release management, testing, administration, and marketplace. Here are some highlights:

  • Agile: @Today and @Me macros fixed to work correctly in non-English in the Kanban board card style rules; Batch API now returns correct results even when called with many strings; work item tracking warehouse sync issues have been fixed for field name conflicts and link comments with special characters.
  • Version control: Fixed issues with rollbacks upon destruction of very large team projects and branch relationship breaks when renaming branch objects that span projects.
  • Build: Fixed issue with initial check-ins that crashed after configuring a build definition's Gated Check-in trigger; error no longer displayed with loading build tasks or queuing builds; Windows build agent now works with Subversion repos on 32-bit machines; build tasks are now updated with extension updates.
  • Release management: "In a release environment, if the All users in sequential order option is chosen and the approver order is changed, the definition is not marked dirty and cannot be saved."
  • Testing: Users now allowed to deploy standalone test agent; when using the test runner, test cases can be restarted when marking a test case as paused, and then saved and closed.
  • Administration: Admin console no longer crashes during upgrades; email alerts now working for non-English code reviewers; Jenkins Service Hook now supports newer Jenkins versions.
  • Marketplace: "Installations of MS.TFS.Server are now supported."

The release notes are here.

About the Author

Michael Domingo is a long-time software publishing veteran, having started up and managed several developer publications for the Clipper compiler, Microsoft Access, and Visual Basic. He's also managed IT pubs for 1105 Media, including Microsoft Certified Professional Magazine and Virtualization Review before landing his current gig as Visual Studio Magazine Editor in Chief. Besides his publishing life, he's a professional photographer, whose work can be found by Googling domingophoto.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube