You're reading from Developing Multi-Platform Apps with Visual Studio Code Get up and running with VS Code by building multi-platform, cloud-native, and microservices-based apps

Product type Paperback

Published in Sep 2020

Publisher Packt

ISBN-13 9781838822934

Length 334 pages

Edition 1st Edition

Languages

Tools

Visual Studio

Concepts

Application Development

Authors (2):

Khusro Habib

Ovais Mehboob Ahmed Khan

View More author details

Table of Contents (15) Chapters

Preface

1. Section 1: Introduction to Visual Studio Code

2. Chapter 1: Getting Started with Visual Studio Code FREE CHAPTER

3. Chapter 2: Extensions in Visual Studio Code

4. Section 2: Developing Microservices-Based Applications in Visual Studio Code

5. Chapter 3: Building a Multi-Platform Backend Using Visual Studio Code

6. Chapter 4: Building a Service in .NET Core and Exploring Dapr

7. Chapter 5: Building a Web-Based Frontend Application with Angular

8. Chapter 6: Debugging Techniques

9. Chapter 7: Deploying Applications on Azure

10. Chapter 8: Git and Azure DevOps

11. Section 3: Advanced Topics on Visual Studio Code

12. Chapter 9: Creating Custom Extensions in Visual Studio Code

13. Chapter 10: Remote Development in Visual Studio Code

14. Other Books You May Enjoy

Leave a review - let other readers know what you think

Branching in VS Code and Azure DevOps

To create a new branch in VS Code, click on the master branch in the bottom-left corner. The command palette will show an option to Create new branch. Select this and create a branch from the currently selected branch. You can also use Create new branch to use another branch. Next, enter a name of the branch, we'll use feature1, and press Enter. The new branch is created and selected as well. In the bottom-left corner, you will see the active branch is feature1. Change the title in index.html, Commit the changes, and Push to the remote repository. VS Code will prompt you to publish the new branch since no upstream branch exists. Click OK to continue:

Figure 8.18 – feature1 branch pushed to Azure DevOps with commit history

Let's assume that your changes are complete and ready to be merged with the master branch. Instead of directly merging the feature branch into your master branch, in a real-world scenario...