March 2019

  Command Line Commands for dotnet core
March 28   |   Net

Command Line Commands for dotnet core

 dotnet core


dotnet --version
dotnet new [template]

 Create a console app


dotnet new console

// dotnet restore implicit
dotnet build

// dotnet restore and build implicit
dotnet run

 Create a solution with tests and references


dotnet new [template]
dotnet new sln -n [name]

mkdir Library
cd Library
dotnet new classlib  
dotnet add package System.Threading.Task.Extensions
cd ..
dotnet sln add Library\Library.csproj

mkdir Test
cd Test
dotnet new xUnit
dotnet add reference ..\Library\Library.csproj
cd ..
dotnet sln add Test\Test.csproj
  ASP.NET attach your source code to published IIS website
March 21   |   Net

When working with ASP.NET and developing websites focused to micro-services is a common approach to use a remote published website to test our project and all the interactions between micro-services, so to debug this, follow the next steps:

It's a must that our source code match with the build of the published website to allow us debugging
  1. To debug, attach our visual studio using Ctrl + Alt + P

  2. In the window Attach to Process filter we can search by process name, for IIS is always w3wp.exe


✍️ Execute Visual Studio as administrator (right click over the visual studio shortcut to show this option)

✍️ Active checkbox [x] Show processes from all users

And now ... Which one is my website?

Most of the time you can identify your target website by its title name, but sometimes the title name won't show up (I'm not sure why, I guess is maybe a bug), but don't worry use the command appcmd inside directory cd %windir%\system32\inetsrv and add the parameter list wps, it will show up the identifier number that you can match with the one in the Attach to Process Window