With the expanding number of tools to help you become more productive or to improve the functionality of your app, you may have a requirement for a custom tool or specific version to be used during the build process in a Continuous Integration build.
In the 1.116.0 release of the Visual Studio Team Services extension for Visual Studio Code, we have added support for Team Foundation Version Control (TFVC). TFVC support works for both Team Foundation Server 2015 Update 2 (or later) as well as Team Services.
You can now migrate code from an existing TFVC repository to a new Git repository within the same account. To start migration, select Import Repository from the repository selector drop-down.
Individual folders or branches can be imported to the Git repository,
I hear this particular question frequently as a reason teams are concerned about adopting Visual Studio Team Services when their applications still run on-premises. The good news is that it is typically a quick walkthrough on how build & deployment pipelines work.
The goal of DevOps is to continuously deliver value. Using deployment slots can allow you to do this with zero downtime. In the Azure Portal, in the Azure App Service resource blade for your Web App, you can add a deployment slot by navigating to “Deployment slots,” adding a slot,
As part of the #SpringIntoDevOps series, Gopinath Chigakkagari – GPM of the Release Management team at Microsoft joined the most recent episode of Radio TFS with MVP’s Greg Duncan and Josh Garverick to talk about the latest news around Visual Studio Team Service and Team Foundation Server as well as dive into release management and DevOps in general.
If you remember back to 2013 (and before), we released standalone installers for Team Explorer. In VS 2015, we did not release a standalone Team Explorer since customers had free options with Express SKUs and Community, which included Team Explorer functionality.
Your continuous delivery pipeline typically consists of multiple environments. You may want to deploy changes first to a test or staging environment before deploying to a production environment. Furthermore, your production environment may itself comprise of multiple scale units, each of which you may deploy in parallel or one after the other for a gradual roll out.
As promised, we announced the open sourcing of MSTest Test Framework “MSTest V2”. The community now has a fully supported, open source, cross-platform implementation of the MSTest V2 portfolio with which to write tests targeting .NET Framework, .NET Core and ASP.NET Core on Windows,
We’re really glad to have Abel Wang help us out for #SpringIntoDevOps with this awesome blog contribution about verifying whether your deployment finished successfully by integrating smoke tests into your pipeline. Thank you Abel! — Ed Blankenship
Having a Continuous Integration (CI) and Continuous Delivery (CD) pipeline in Visual Studio Team Services enables us to build and release our software quickly and easily.