Port to .NETCore/.NETStandard ? about scrypt

[viniciuschiele]

I believe it shouldn't be that hard to port it.
I will dig into it this week and I will let you know and feel free to contribute if you wish.

Cheers

[prajaybasu]

If this helps : https://github.com/dotnet/corefx/issues/9442

[prajaybasu]

Ah yes, took about 2 lines to port (most of the commits are to fix my own mistakes) , however travis deployment would require scripts for .NET Core so I am not submitting a pull request.

[viniciuschiele]

Thanks for that @prajaybasu

I have to keep compatibility with .NET 2.0, I will check how to keep it working with .NET 2.0 and .NET Core 1.0 and then I will release a new version on NuGet.

[prajaybasu]

The docs are here.
However, netcore uses project.json for resolving dependencies. I suggest we keep .NET 2.0 and .NETCore version both, since they are not compatible (but the latter works on mono+xamarin+uwp+netcore+net461) and using preprocessor directives is not ideal.
(And I hope to use the default rfc2898derivebytes function with sha256 once they release a new package for System.Security.Cryptography).

[viniciuschiele]

Just to let you know, I've released a new version on NuGet, this version contains a DLL for .NET 2.0 and another for .NET Core (netstandard 1.3).
I also added your references in the AUTHORS file.
Thanks again.