February is coming to a close and it has been the best month on record for the Team Services Extension ecosystem. We’ve set new records for customer installs and our community of publishers continues to grow. One of my favorite parts of this job is the relationship I get to build with our publishers.
MSTest V2 has crossed 100K downloads. It has been but just a few months since we shipped it on NuGet. Over this course of time, you have reported issues and given us feedback, and we have tried to address them as fast as we can,
[This is the 4th post in a 4-part series on evolving the Visual Studio Test Platform. You can read the earlier parts here:
Evolving the Visual Studio Test Platform – Part 3,
Evolving the Visual Studio Test Platform – Part 2,
Wiki has gone to public preview and you can check it out today!
We’re firm believers that a vibrant extension ecosystem is critical to having a best-in-class DevOps product. Not only does it organically bring new technologies and solutions that our customers are looking for,
With the right DevOps tools, developers can run continuous integration builds that automate testing, analysis and verification of their projects, and streamline continuous deployment to get innovative applications into user’s hands quickly. Along with the release of Visual Studio 2017 RC.3 update,
Here at Microsoft we have teams of all shapes and sizes, and many of them are already using Git or are moving that way. For the most part, the Git client and Team Services Git repos work great for them. However,