Showing results for May 2016 - Page 2 of 2 - Azure DevOps Blog

There are times when searching for something, when a simple term just won’t do. Whether it is when you are ordering some coffee or sifting through your inbox, sometimes you know exactly what you are looking for and you just need a way to do it. Well, with our query language constructs you can now do exactly that while discovering extensions on the ...

< p>In the continuation of SonarLint 2.1 for Visual Studio, last week, SonarSource and Microsoft released SonarLint 2.2, providing in-IDE analysis results consistent with analysis builds. Here is a description of the scenarios covered by these new improvements: Notifications when the quality of the solution is not consistent with the Quality p...

This morning we will begin rolling out a new image across the hosted build pool with the following updates:

Of late, we have heard that several people are interested in trying out the capabilities of Visual Studio load test offering, but they are not sure how to go about it if they don't already have an Enterprise license. This post illustrates how to use Visual Studio Enterprise trial to learn about load test capabilities in the VS IDE, and how you can...

We are happy to announce the availability of a Cloud Foundry build extension on the Visual Studio Team Services Marketplace. The extension provides a build task to deploy your applications to any Cloud Foundry instance. It also includes a utility task to run any Cloud Foundry CLI command as part of your build/release process. Check out this video ...

To share and explain our current Java feature set and capabilities with Visual Studio Team Services and Team Foundation Server (TFS), we have produced and published two new 30-minute videos available on our Java team’s YouTube channel. The first video provides an overview presentation of our current Java feature set and capabilities for both Team ...

On the Package Management team, we’re frequently asked how to think about versioning packages. Conceptually, it’s simple: NuGet (like many package managers) prefers semantic versioning (SemVer), which describes a release in terms of its backwards-compatibility with the last release. But for teams that have adopted continuous delivery, there’s tensi...