Guidance on usage: .NET 6 Software Framework Server on Debian 11

Connecting to .NET 6 Software Framework Server on Debian 11

  1. For the connection to the server, you should know the IP address of the VM. You can find it in the personal account of Azure. Select the virtual machine from the list. By clicking the item “Overview”, your IP is displayed in the “Public IP Address” line.
  1. To manage with a Packer server, you should connect to a VM:
    1. With the PuTTY application 

To do this, you need the PuTTY application to connect via ssh. You can download it at the following link – Download

Run PuTTY, enter the VM address in the “Host” field (1), and click “Open” (2) to connect.

In the opened console, you will need to enter a username (1) and password (2) that were specified while the VM was being created (you’ll not see the password in the console while entering it). 

  1. With OpenSSH

In the Windows 10 operating system (starting with version 1809), an OpenSSH client is available, with which you can connect to Linux servers via SSH. If Windows 10 is suitable and the OpenSSH client is installed, you can start connecting via SSH. To do this, launch a standard Windows command prompt and enter the command “ssh user@*vm_ip*” (1), where “user” is the username that was specified while creating the virtual machine and “*vm_ip*” is the VM IP address.

Then type “Yes” (2) and enter a password (3) that was specified while creating the virtual machine.

  1. To view the version of the SDK package, enter the command:

> dotnet –list-sdks

  1. To view the runtime versions, enter the command:

> dotnet –list-runtimes

  1. You can view all information, including SDK versions and runtime versions, with the command:

> dotnet –info

  1. Now you can work with a completely clean .NET 6 Software Framework Server on Debian 11

For further interaction, please refer to the primary documentation:

 Install .NET on CentOS – .NET | Microsoft Docs

If you have any questions, welcome to our community:

 dotnet-ad-linux – Microsoft Q&A