The March 10th update to Visual Studio Online illustrates some of the important relationships between it and Team Foundation Server. These two products share most of the same code and feature set, but their release cycles couldn’t be more different.
Today felt like a day of housekeeping. Mostly it was about promoting products from preview/beta to production status. There were some big revelations around opening sourcing Roslyn the formation of the .NET Foundation, but even these were just doing what the community has been asking for all along.
Less than 9 months after the release of Visual Studio 2012, Microsoft has announced that Visual Studio 2013 will be released this year. InfoQ looks at what has been announced so far.
Windows Azure experienced a 9 hour outage on February 22 that affected all users who relied on the storage system, including those using Team Foundation Service. InfoQ examines the details that have emerged surrounding the root causes of the failure.
Git, the popular open source distributed version control system is now natively supported by Visual Studio 2012 and the Team Foundation Service. Microsoft's new plug in provides native support and provides an alternative to the centralized source control model.
Microsoft released Team Explorer Everywhere Update 1 for Team Foundation Server with Chinese language pack and support for public workspaces.
Buck Hodges argues that long release cycles lead to unhealthy development practices for the Team Foundation Server team, but there is more to short release cycles than just shipping with each sprint. Other changes in how software is planned and developed is needed, including the ability to disable new features rather than fixing them.
Visual Studio 2012 simplifies the code review task with the ability to compare code files, annotation, comments from reviewers and status updates.
At this week's VS Live conference, Microsoft announced a new Build Service for Team Foundation Service, the Azure-based version of Team Foundation Server. The build service will automatically compile and run unit tests every time files are checked in.