Powershell Script started with SshCommand keeps running even after connectivity loss

I wanted to start a specific .ps1 file with SSH, so I tried running the script with both SSH.NET and SSH on the Terminal. After testing a little bit I noticed, that after a connectivity loss the Script started with the Terminal drops itself regardless of the progress, on the other Hand with SSH.NET the .ps1 file keeps running even if the connection is dropped.

for SSH.NET I used this Code to start the .ps1-File:

sshc.Connect();
using (var cmd = sshc.CreateCommand("powershell.exe -command C:\\Test.ps1\""))
{
    cmd.Execute();   
}
sshc.Disconnect();

So I want to know why does SSH.NET keeps the script alive and is this a wanted feature

Inizia con il flusso SSH.NET mostrato usando Connect(), CreateCommand(), Execute() e Disconnect(), quindi riproduci il comportamento interrompendo la connettività durante C:\Test.ps1. Confrontalo con il comportamento del terminale e determina se l’esecuzione del comando deve continuare dopo la perdita della connessione SSH; documenta o testa il comportamento risultante.