Skip to main content

Steps To Create, Run And Debug Dotnet Core Application In Visual Studio Code

Introduction:

Microsoft Visual Studio Code is a lightweight editor that supports most of the programming languages. Dotnet Core can be run and debug using Visual Studio Code as we do in Visual Studio editor which is the recommended and famous editor for Dotnet Applications.

Before starting anything, install the latest version of Dotnet Core SDK from the Microsoft DotnetCore website and also download the Visual Studio Code editor which is the free editor.

C# for Visual Studio Code Extensions:

In Visual Studio Code, we can get a lot of extensions plugins which makes development more easy and fast. Similarly to work with C# we need to install the VS Code extension of "C# for Visual Studio Code". Few features of this extension like:
  • .NET Core lightweight development tool.
  • Good C# editing support.
  • Syntax Highlighting.
  • Good Code Intellisense.
  • Nice debugging support.

Create A Dotnet Core Solution:

In Visual Studio solution file automatically get created while creating the .NET Core application, but in Visual Studio Code, we need to create the solution file. It is not mandatory to have a solution file in .Net Core application, but it is an individual choice of having it like a parent of all .Net Core projects. ".sln" is the file extension for the solution file.

.NET Core CLI Commands we can generate a solution file using either Windows Command Prompt or Visual Studio Code Terminal (Powerfull command prompt comes with Visual Studio Code). The following command to create the ".sln" file.
dotnet sln new
To start creating a project let's create a root folder and I'm naming the folder as "TestCore" and then open the visual studio code and go to the "File" menu and select on the "Open Folder" option, then choose our folder to created previously.

Now go to the "View" menu and select on the "Terminal" option, then enter the above CLI command on the Terminal as below.
Now after executing the command ".sln" file gets created with the name of the root folder as below.

.NET Core Application Templates:

.Net core provided all templated options to create applications like MVC, Web API, Blazor, etc. Few of the CLI commands to create projects with their respective templates as follows:

CLI command to create .Net Core Console Application
dotnet new console -n Your_Application_Name
CLI command to create .Net Core MVC Application
dontet new mvc -n Your_Application_Name
CLI command to create .Net Core Class Library
dotnet new classlib -n Your_Application_Name
So to check all types of templates supported by .NET Core run the following command
dotnet new -l 
On running the command it will show different templates as below:
 Let's test our setup by creating MVC template application as below:

Attach Project To Solution File:

Run the following command to add c# project to the solution file
dotnet sln Your_Solution_FileName.sln  add  Your_Project_Folder\Your_Project_Name.csproj

Add Project Reference:

Let's create a .NET Core ClassLibrary project by running the following command
dotnet new classlib -n Your_ApplicationName
Now let's add ClassLibrary project to the solution file as below
Now I'm going to add this ClassLibrary project reference into the MVC project. Adding a reference to the project can be done with the following command.
dotnet add Application_Expecting_Reference_Folder/Application_Expecting_Reference_Project reference Refered_Application_Folder/Refered_Application_Project
Now we can confirm the reference presence by opening the project as below.

Add Build And Debug Configuration Files:

Creating projects in the Visual Studio Code will show a notification to install build tools as below.
On selecting the 'Yes' button, we can observe a couple of JSON files with build settings as below.

Build And Run Project:

Building the project at the solution level will help in building all the projects that are added to the solution file. The command to build the project as below.
dotnet build

 Now go to the folder of an application be run and enter the following command to run the application
dotnet run

 Debugging From Visual Studio Code:

Visual Studio Code editor we can find the "Debug" options in menus as below
From Debug menu select option like "Start Debugging" and then the application will get run as below

Wrapping Up:

Hopefully, this article will help to create, run and build the .NET Core application in Visual Studio Code. I will love to have your feedback, suggestions and better techniques in the comment section.

Follow Me:

Comments

Popular posts from this blog

Endpoint Routing In Asp.Net Core

How Routing Works In  Core 2.1 And Below Versions?: In Asp.Net Core routing is configured using app.UseRouter() or app.UseMvc() middleware. app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller=Home}/{action=Index}/{id?}"); }); Here in Dotnet Core version 2.1 or below versions on the execution of route middleware request will be navigated appropriate controller matched to the route.

An operation or functionality which is dependent on route URL or route values and that need to be implemented before the execution of route middleware can be done by accessing the route path from the current request context as below
app.Use(async (context, next) => { if(context.Request.Path.Value.IndexOf("oldvehicle") != -1) { context.Response.Redirect("vehicle"); } else { await next(); } }); app.UseMvc(routes => { routes.MapRoute( name: "vehicleRoute", template: "vehicle", defaults:new { …

GraphQL API Integration In Asp.Net Core Application

Introduction:
GraphQL is a query language for your API and a server-side runtime for executing queries by using a type system you define for your data. GraphQL can be integrated into any framework like ASP.NET, Java, NestJs, etc and it isn't tied to any specific database or storage engine and is instead backed by your existing code and data.
How GraphQL API Different From Rest API: GraphQL exposes a single end-point or route for the entire application, regardless of its responses or actions.HTTP-POST is the only Http verb recommended by the GraphQL.The client applications (consumers of API) can give instructions to GraphQL API about what type of properties to be returned in the response. Building Blocks Of GraphQL API:The main building blocks of GraphQL API is Schemas and Types. A 'Schema' in GrpahQL API describes the functionality available to the clients connect to API. Schema mostly consists of GraphQL Object Types, Queries, Mutations, etc.Types likely to be called Grap…

ASP.NET Core Web API Versioning

Introduction: An iteration and evolutionary changes of an ASP.NET Core Web API is handled by Versioning. Versioning of an API gives confidence to the clients which consumes API for a long time. Any changes or development of an API will be accessible using the new version and it won't cause issues to the clients consuming the old version of API.
When To Use Versioning:Any API response changes.Developing an API by implementing testing levels like 'Alpha', 'Beta', and 'RC' versions before releasing Production.Deprecating an API which means API going to be removed or upgraded by a version within a short period. Versioning Types:Query String VersioningUrl Path VersioningMedia Type Versioning API Version Nuget: To Configure versioning to AspNet Core Web API Microsoft provided a library(Microsoft.AspNetCore.Mvc.Versioning). So to use the versioning library please install NuGet below.
 Install-Package Microsoft.AspNetCore.Mvc.Versioning -version 4.0.0 Register API V…

.NET Core MVC Application File Upload To Physical Location With Buffered Technique

Buffering Technique In File Upload:The server will use its Memory(RAM) or Disk Storage to save the files on receiving a file upload request from the client. Usage of Memory(RAM) or Disk depends on the number of file requests and the size of the file. Any single buffered file exceeding 64KB is moved from Memory to a temp file on disk. If an application receives heavy traffic of uploading files there might be a chance of out of Disk or RAM memory which leads to crash application. So this Buffer technique used for small files uploading. In the following article, we create a sample for the file uploading using .NET Core MVC application.
Create The .NET Core MVC Project: Let's create a .NET Core MVC project, here for this sample I'm using Visual Studio Code as below.  Check the link to use the Visual Studio Code for .NET Core Application.
IFormFile: Microsoft.AspNetCore.Http.IFormFile used for file upload with buffered technique. On uploading files from the client, then the entire …

Ionic Picker Sample Code In Angular

Introduction: Ionic Picker(ion-picker) is a popup slides up from the bottom of the device screen, which contains rows with selectable column separated items.
The main building block of ion-picker as follows: PickerControllerPickerOptions PickerController: PickerController object helps in creating an ion-picker overlay. create(opts?: Opts): Promise<Overlay> PickerController create method helps in create the picker overlay with the picker options
PickerOptions: PickerOptions is a configuration object used by PickerController to display ion-picker.
Single Column Ionic Picker: single.item.picker.ts: import { Component } from "@angular/core"; import { PickerController } from "@ionic/angular"; import { PickerOptions } from "@ionic/core"; @Component({ selector: "single-column-picker", templateUrl:"single.item.picker.html" }) export class SingleItemPicker { animals: string[] = ["Tiger", "Lion", "Elephant"…

Blazor WebAssembly Dynamic Form Validation

Introduction: In Blazor WebAssembly(client-side framework) form validation can be done with Data Annotations. Using Data Annotations we can validate form either by default validation attributes or by creating custom validation attributes. Using this Data Annotation attribute we can dynamically add or remove validation on a specific field in a form.
Create Blazor WebAssembly Project: To create a Blazor WebAssembly template project need to install the latest version of VisualStudio 2019 for rich intelligence support or we can use VisualStudio code but less intelligence support from the editor. Click here to know about Blazor WebAssembly template creation. Blazor WebAssembly is in preview mode, not yet ready for production.
Create Razor Component: After creating a sample project using the Blazor WebAssembly template, in "Pages" folder add new Razor Component, name it as "UserForm.razor"
Add Route: In Blazor routing can be configured using @page  directive, and URL should b…

Asp.Net Core MVC Form Validation Techniques

Introduction: Form validations in any applications are like assures that a valid data is storing on servers. All programing frameworks have their own individual implementations for form validations. In Dotnet Core MVC application server-side validations carried on by the models with the help of Data Annotations and the client-side validations carried by the plugin jQuery Unobtrusive Validation. jQuery Unobtrusive Validation is a custom library developed by Microsoft based on the popular library jQuery Validate.
In this article, we are going to learn how the model validation and client-side validation works in Asp.Net Core MVC Application with sample examples.
Getting Started: Let's create an Asp.Net Core MVC application project using preferred editors like Microsoft Visual Studio or Microsoft Visual Studio Code. Here I'm using Visual Studio.
Let's create an MVC controller and name it as 'PersonController.cs' and add an action method as below.
PersonController.cs: us…

Blazor Server CRUD Operations

Introduction: Blazor Server is a web framework to develop server-side single-page applications. Blazor is made up of components with the combinations on C#, Html, CSS.  Blazor Server is production-ready from the .Net Core 3.0.  Blazor Server Working Mechanism:Blazor Server is a very light-weight web development framework. In Blazor Server, not all code gets downloaded to the client browsers. Blazor Server made of components these components can be a block of code or page with respective navigation. Blazor server application communicates with the server with a SignalR background connection which is inbuilt functionality. Application click,  form submission, change events, application page navigation every operation is carried out by the SignalR connection by communicating with the server. Blazor updates the Html DOM very gently on every data update without any overhead. Blazor Server application maintains a nice intelligent tree structure to update the required information or changed …

NestJS API CRUD Operations With MongoDB

Introduction: NestJS is a framework used to develop server-side applications. NestJS built on top of Node.js frameworks like Express. It is a combination of Progressive Javascript, Object-Oriented Programming, Functional Programming, and Functional Reactive Programming.
Nest CLI Installation: Using Nest CLI we are able to generate the NestJS starter project with the default template. To install Nest CLI globally over our system open command prompt and run the command
npm i -g @nestjs/cli Now create a sample project by using Nest CLI command  nest new your_project_name package.json: Now open the package.json file from the sample application created, you can observe few properties like "scripts", "dependencies", and "devDependencies".
"dependencies" contains all plugins to be installed and used them to run the application.
"devDependencies" contain all plugins to be installed and used them at the time of application development.
"scrip…

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server.
Main Response Caching Headers are like below
Cache-ControlPragmaVary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response.private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores.max-age - this directive represents a time to hold a response in the cache.no-cache - this directive represents no storing of response and always fetch the fresh response from serverno-store…