Continuous Integration for ASP.NET Web App with VSTS and Git

Continuous Integration(CI) is not a new topic to the Software Developers, yet there are companies picking up the trend. CI will help you to commit and push your code at the convenience of your IDE (Visual Studio 2017 in my case) to Visual Studio Team Services Code Repository and trigger a build. Your build can be defined in the manner you want it to be by adding different tasks such as restoring NuGet Packages, running unit tests etc. You can order your build to copy the build output to a given path. This is much easier when you have a team working on the same project as it avoids last minute integrations.

CI History
Build history in VSTS

If you are totally new to CI/CD you can read this to get an understanding about the topic. You can read this to get CI running for your ASP.NET web app, using Git and Visual Studio Team Services.

Git and Team Services made easy with Visual Studio 2017

Git distributed version control system can be used to manage code in the Visual Studio Team Services repository. Visual Studio 2017 IDE provides easy access to Git and VSTS.

Here are some important information to begin with.

If you come across error 400 when you are cloning, first of all check whether you have spaces in the git repository URL and replace the spaces with %20 as suggested here.