NuGet.org packages
Rebex components are available from the NuGet.org package feed, available and configured by default in both legacy .NET Framework and current .NET. Use standard methods to install them, for example:
- In .NET CLI:
dotnet add package Rebex.Sftp - In VS Package Manager Console:
Install-Package Rebex.Sftp
Specifying license keys
When referencing standard NuGet packages, you have to set license key before using the components:
Rebex.Licensing.Key = "==somekey==";
Trial keys
You can get trial key valid for 30 days at https://www.rebex.net/support/trial/. Obtaining trial keys does not require any kind of registration or login.
Production keys
After login, you can find your production key at https://www.rebex.net/account/nuget/.
This key is valid forever, for builds relesed before your support contract ends. After your support ends, you would still be able to use versions released while you had it, but not newer ones. After extending your support contract you'll have to generate a new nuget key.
Storing license keys
The best way to store your license keys is to hardcode them into your code. Which is kind of counterintuitive, because usually we want to keep secrets out of the source code and repository, but in this case it makes sense.
Do not store license keys in configuration, .NET user secrets or in similar places. They are not and should not be made user configurable or user accessible.
If you cannot abide to this policy, you have to use local packages or assemblies, which do not require keys to be specified, but then you need to build your own infrastructure to made them available during build and is your responsibility to keep them updated.