Showing results for Continuous Integration/Continuous Delivery - Visual Studio Blog

We have an update for the Configure Continuous Delivery feature in Visual Studio. For Solutions with an ASP.NET or ASP.NET Core projects you can right click on the solution node and select “Configure Continuous Delivery…"with and without container support. You can always configure Continuous Delivery for solutions under source control in GitHub and...

A year ago, we released the first preview of the Continuous Delivery Tools for Visual Studio (CD4VS) with support for configuring a continuous integration and continuous delivery pipeline for ASP.NET and ASP.NET Core projects with and without container support. With CD4VS you can always configure Continuous Delivery for solutions under source contr...

In our earlier post “Continuous Delivery Tools Extension for Visual Studio 2017” , we introduced failure notifications for a single tracked Continuous Integration (CI) build on Visual Studio Team Services (VSTS). In subsequent releases of the Continuous Delivery Tools for Visual Studio extension, our notification model evolved, to provide no...

At //BUILD 2017, we shipped an update to the Continuous Delivery Tools for Visual Studio. This update has support for configuring a Continuous Integration and Continuous Delivery pipeline for ASP.NET Core projects with container support to an existing Azure Service Fabric cluster directly from Visual Studio 2017. To configure continuous delivery...

We are looking to improve your experience on the Visual Studio Blog. It would be very helpful if you could share your feedback via this short survey that should take less than 2 minutes. Thanks! At //BUILD 2017, we shipped an update to the Continuous Delivery Tools for Visual Studio with support for configuring a Continuous Integration and Conti...

We are looking to improve your experience on the Visual Studio Blog. It would be very helpful if you could share your feedback via this short survey that should take less than 2 minutes. Thanks! In the earlier post “Committing with Confidence: Getting Code Quality Information at Commit Time” , we introduced the new Build and Code Analysis Result...

Many developers tell us that they are under pressure to deliver software on an ever-faster cadence. This pressure for increased speed makes building your software at high quality from the start even more important – you want to make sure that any commits you make to your codebase are at the right quality, to avoid costly remediation of errors later...

Last week at //BUILD, the Continuous Delivery Tools for Visual Studio shipped a new update. As always we are continuing to expand the extension’s set of features guided by your feedback. The enthusiasm and feedback has validated just how much opportunity there is to help you continuously deliver value to your users. Apart from bug fixes, our latest...

[UPDATE: 28th Nov 2017] Continuous Delivery Tools for Visual Studio now supports TFVC. You can configure continuous delivery for TFVC or Git repositories in a VSTS team project. Check out this blog post (http://aka.ms/cd4vsblog9) DevOps is all about getting your applications into customers’ hands quickly. The Continuous Delivery Tools for Visual...