Is your feature request related to a problem? Please describe.
I wanted to use the Proj file Solution to push the binaries. Sadly it is not recognizing a VbProj file.
The error I'm getting is "No csproj file was found"
Describe the solution you'd like
It should be searching for CsProj and VbProj files.

When I deploy a .net core self-contained project onto my Raspberry Pi,
I always have to chmod +x myProject && ./myProject on the Pi, as the executable is not marked as an executable file after the ssh copy of the project.

This is, however, only a minor inconvenience. That said, if it would be possible to add a chmod call to mark the executable as such without a lot of effort (i.e. the executable could be easily found from msbuild properties and the call could easily be added), that would be a nice improvement.

I have a project that cannot be deployed to the pi, when multiple target runtimes are available.

When I have only <RuntimeIdentifier>linux-arm</RuntimeIdentifier> set, and I do a dotnet publish command, it works.

However, when I have set <RuntimeIdentifiers>win-x64;linux-arm</RuntimeIdentifiers> and I do a dotnet publish -r linux-arm, ssh-deploy deploys the wrong files (the framework-dependent project .exe) and not the self-contained Linux version.

I also did not find a way to pass the directory to deploy (in my case D:\Dev\sg\bsc-ampel\bin\Debug\netcoreapp3.0\linux-arm\publish) to the tool. It always wants to deploy the wrong build.

I have to go back to only support one runtime, which makes local debugging extremely tedious.

Cannot deploy a ASP.NET Core project with Sdk "Microsoft.NET.Sdk.Web" with this tool.

The problem is in Swan and is tracked here: unosquare/swan#96

Describe the bug
I'm using the worker template from the dotnet cli (dotnet new worker) and I wanted to use sshdeploy with this project but the template has a SDK that is not supported (Microsoft.NET.Sdk.Worker). Would it be possible to add this SDK to the supported ones?

To Reproduce
Steps to reproduce the behavior:

1. Create a new worker project with the dotnet cli
2. Add sshdeploy
3. Push
4. See error

Expected behavior
The application is pushed.

Actual behavior

Unhandled exception. System.ArgumentException: Project file is not of the new .csproj type.
     at Unosquare.Labs.SshDeploy.Utils.CsProjFile`1..ctor(Stream stream, Boolean leaveOpen) in C:\Unosquare\sshdeploy\Unosquare.Labs.SshDeploy\Utils\CsProjFile.cs:line 54
     at Unosquare.Labs.SshDeploy.Utils.CsProjFile`1..ctor(String filename) in C:\Unosquare\sshdeploy\Unosquare.Labs.SshDeploy\Utils\CsProjFile.cs:line 32
     at Unosquare.Labs.SshDeploy.Program.Main(String[] args) in C:\Unosquare\sshdeploy\Unosquare.Labs.SshDeploy\Program.cs:line 46

Using Version 0.4.0.0.

When I run dotnet-sshdeploy push, the files are copied to my Pi device and it tells me that it finished the deployment (it did copy the files) but the tool is still running. It seems indefinitely stuck waiting for either some event to occur or the user to terminate the app with Ctrl+C, which is the only way I can seem to stop it. I'm assuming this is not expected behavior since I'm not running monitor. Ideas on potential cause and fix?

Project file has this:

  <PropertyGroup>
    <RuntimeIdentifiers>linux-arm</RuntimeIdentifiers>
    <SshDeployHost>192.168.4.87</SshDeployHost>
    <SshDeployTargetPath>/home/pi/myapp</SshDeployTargetPath>
    <SshDeployUsername>pi</SshDeployUsername>
  </PropertyGroup>

I'm running the tool with dotnet-sshdeploy push -w $PI_PWD -v. I've also tried it with the password directly in the project file, and with and without runtime identifiers.

Describe the bug
Projects that have .NET Standard 2.1 dependencies fail to deploy

To Reproduce
Steps to reproduce the behavior:

1. Create solution with a .NET 5.0 console application that has a project reference to a .NET Standard 2.1 class library
2. From the project directory of the console application, execute "dotnet-sshdeploy push -f net50"
3. Deployment fails with error:
   C:\Program Files\dotnet\sdk\5.0.102\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(241,5): error NETSDK1005: Assets file '<.NET Standard 2.1 project directory>\obj\project.assets.json' doesn't have a target for 'netstandard2.1'. Ensure that restore has run and that you have included 'netstandard2.1' in the TargetFrameworks for your project.
   [<.NET Standard 2.1 project .csproj file>]
   Invoking MSBuild target failed

Expected behavior
The application should successfully deploy.

Desktop (please complete the following information):

• OS: Windows 10

I try running
dotnet sshdeploy push
with a source path on
..\bin\Debug\net46
but the push command always creates the publish folder and sets the source path to ..\bin\Debug\net46\publish

This is just a suggestion.
Since the dotnet CLI can be extended, you could make it available on nuget to extend the dotnet CLI.
A possible usage would be:
dotnet sshdeploy ...

Going further, the sshdeploy could also trigger the SCD publishing (Self Contained Deployment) when you don't want to install the runtime or the sdk on the target linux machine.

Invoking the rsync command when available (on both source and destination), would make transfers 100x faster. Rsync copies only the portions of files that have changed and can be directed to delete all files not wanted on the destination.

Did you have a planning to make this library usable in .NET 5? Because i like this raspberryIO but that library seems dependable with ssh deploy library

Describe the bug
When I publish after a succesfull build my dotnet application does not execute anymore.

The following exception is thrown:

pi@pibot01:~/publish $ ./PiCore
PiCore: /root/coresetup/src/corehost/cli/fxr/fx_muxer.cpp:416: static pal::strin g_t fx_muxer_t::resolve_fx_dir(host_mode_t, const pal::string_t &, const runtime _config_t &, const pal::string_t &, const int &): Assertion `mode != host_mode_t ::standalone' failed.
Aborted

To Reproduce
My initial deploy was with Putty pscp.exe.
Later I implemented dotnet-sshdeploy which published the changes.

Expected behavior
I expect an update of my application.

Describe the bug
When you try to publish an app that uses async main, ssh deploy generates the next error:

error CS8107: Feature 'async main' is not available in C# 7.0.

Note: It seems like if you don't include the LangVersion tag then ssh deploy uses C# 7.0 by default for publishing the app.

Upgrade tool to .NET Core 2.1 and use the new global tool specification.

Is your feature request related to a problem? Please describe.
The current tool requires specifying a password to allow authentication.

Describe the solution you'd like
I would like to to have support for password-less authentication by using ssh private key and ssh-agent

Describe alternatives you've considered
Either try to get a public key for authenticating by default or if property was specified

I had the following error
CS7069 Reference to type 'SingletonBase<>' claims it is defined in 'Unosquare.Swan', but it could not be found

A Default ASP.NET Core 2.0 Projekt with following additional class

using System.Text;
using Unosquare.RaspberryIO;
using Unosquare.RaspberryIO.Gpio;

namespace WebApplication2.Controllers
{
    public class Class
    {
        public string Test()
        {
            StringBuilder str = new StringBuilder();

            GpioController gpio = Pi.Gpio;
            foreach (var pin in gpio)
            {
                str.AppendLine($"Pin: {pin.PinNumber} and BCM number: {pin.BcmPinNumber} has value: {pin.Read()}");
            }

            return str.ToString();
        }
    }
}

My csproj file after installing the Nuget looks like:

<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp2.0</TargetFramework>
  </PropertyGroup>
 
  <ItemGroup>
    <PackageReference Include="dotnet-sshdeploy" Version="0.2.1" />
    <PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.6" />
    <PackageReference Include="Unosquare.Raspberry.IO" Version="0.13.0" />
  </ItemGroup>
  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="2.0.3" />
  </ItemGroup>
</Project>

Describe the bug
Documentation is outdated

A default MVC app will push almost 400 files in "self-contained" mode. THis happens on every build and takes a minute every time. It would be great if there could be some file compare or datetime stamp logic to skip the 390 files that did not change.

Describe the bug
When the flag AppendTargetFrameworkToOutputPath is set to false in the csproj of the project the dotnet-sshdeploy throws a DirectoryNotFoundException

To Reproduce
Steps to reproduce the behavior:

1. In the csproj add <AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath>
2. Rebuild the solution
3. Execute dotnet-sshdeploy push
4. See error DirectoryNotFoundException

Expected behavior
It should push the files into the target

Additional context
Working with netcoreapp 2.1 versions and linux-arm runtime identifier