Updated Aug 30, 2015: Improved sample gulpfile and added sections to answer common questions. vscode folder.Updated Sept 16, 2015: Improved sample gulpfile. Visual Studio Code support project-level settings via the file settings.json in the. You should see a webpage with the following response (default for webapi scaffold): Go ahead and press F5 or the debug icon to launch your application. The launchBrowser section tells VSCode to open the page once the application is running. src/bin/Debug/netcoreapp2.0/WebApp.dll', We'll start by creating a task to build our project. vscode folder, you can always add it yourself. If VSCode doesn't prompt you to automatically create the. vscode folder in the root of your project: ├──. Launchers are used to launch your application with a debugger attached.īoth are defined in the. They can be used to automate any process that you may need builds with gulp, building docker containers, pushing code to NuGet, etc.

Say Yes and you should see a folder structure similar to the following: │ WebApp.slnĪs stated earlier, Tasks allow you to easily call commands and scripts from within the IDE. The IDE should ask you if you'd like to add default folders. Go ahead and open your project in VSCode. Next, let's create a webapi application in the /src folder. To get started, let’s create a basic web-api solution from the command line: dotnet new sln -name WebApp We are going to create a simple solution with a web-api project and then create some basic tasks to help us build and debug the application. Combined with debug launchers, tasks can supercharge your environment and help you automate any process. You can easily fire of a task without trying to remember what command to type, all while staying within the IDE. VS Code provides a built-in way of organizing all of these various workflows with Tasks. As developers, we are always leveraging various tools to help automate our day-to-day tasks.

Visual studio code debug gulp task