Provide SDK version compatible with .NET Framework 4.5

[maztch]

After some experimenting, I found that when I add the nuget package (and not trying to compile the project myself), all works like a charm.
However, you have one dependency to a component that requires .NET 4.6. This prevents us from using the component from Windows PowerShell (as this component apparently uses .NET 4 or 4.5).
When I run the same code sample in the cross-platform PowerShell 7, it works perfectly well so I assume it must be related to the dependency (which returns the exception that “response” is NULL).
Being compatible with Windows PowerShell is somewhat important as this is the default scripting environment on Windows and widely used in the industry.

[OlegRa]

@maztch I'll check our dependencies list and write you back later about possible solutions for your issue. If it will be possible I add into our NuGet package support for targeting both 4.5 and 4.6+ frameworks.

[OlegRa]

@maztch I'll try to provide additional binaries compatible with .NET Framework 4.5 inside the existing NuGet package. The estimated time for the first alpha version availability is the end of this week.

[OlegRa]

@maztch Could you please try a new 1.3.0-alpha version of SDK and feel free to report any issues related to this release here.

[OlegRa]

@maztch Could you please confirm fact that the last 1.3.0-alpha version of the package solves your problem.

[maztch]

Working, txs