Learn Command Line Interface (CLI) for Build, Run and Publish in .NET Core | Infologs

#infologs #AspNetCore #tutorial
The .NET Core command-line interface (CLI) is a new cross-platform tool for creating, restoring packages, building, running and publishing .NET applications.

We created our first ASP.NET Core application using Visual Studio in the previous tutorial. Visual Studio internally uses this CLI to restore, build and publish an application. Other higher level IDEs, editors and tools can use CLI to support .NET Core applications.

The .NET Core CLI is installed with .NET Core SDK for selected platforms. So we don't need to install it separately on the development machine. We can verify whether the CLI is installed properly by opening command prompt in Windows and writing dotnet and pressing Enter. If it displays usage and help as shown below then it means it is installed properly. for full article please visit:

ASP.NET Core Tutorial Video Series:

1) ASP.NET Core Introduction

2) ASP.NET Core Environment Setup

3) ASP.NET Core New Project Structure

4) ASP.NET Core New Project Structure Understanding

6) Learn Command Line Interface (CLI) for Build, Run and Publish in .NET Core

7) ASP.NET Core Dependency Injection & Configuration of Singleton, Scoped & Transient Service Lifetime

8) What is IoC Container in ASP.NET Core

9) What is Middleware in ASP.NET Core

10) How to create custom Middleware in ASP.NET Core Request Pipeline - Part 2

For more videos visit
------------------------------------------------------------------------

Follow us on social media
-------------------------------------------------------------------------.

Download Project from
--------------------------------------------------------------------------

Thanks
Infologs Team

[AbhilashYadavSanghsevak]

very nice articles very helpful thank you

[amankadakuntla]

When I run the command dotnet run and navigated to localhost:5000, it said " your connection is not private" and nothing came

[dattatreyakulkarni]

very nice video but i have one doubt while publishing .. you are publishing application or you are writing simply dotnet publish i did't get here