Installation

Fetching packages from the NuGet feed

You may fetch the packaged .NET DeviceAPI from a NuGet feed by means of client tools.

To that end, please pick the feed address of the company you would like to be a customer at.

.NET-Framework projects

might require strongly-named assemblies.
In that case, also install the StrongNamer package.
This adds an open-source build tool that strongly-names assemblies that lack one
as part of the build process.

VisualStudio2019

has a package manager that can do this.

It needs to be told the feed address.

Feed sources can be edited under Tools->Options->NuGet Package Manager.

The same editor can also be reached from the gear wheel depicted next to the selected package source

inside the package manager tab shown here

Add the new feed source to the list of package sources and select it.

Then you can install and update the packages from our feed to your projects

in a similar fashion as demonstrated in the Quickstart: Install and use a package in Visual Studio.

.NET CLI

Assuming the StepOver feed, the statement

dotnet nuget add source https://stepoverinfo.net:44331/nuget --name StepOverFeed

adds the StepOverFeed to the list of package sources.

The resulting list of package sources could be printed as follows

dotnet nuget list source

Then, in a .NET project directory

dotnet add package SigDeviceAPI

adds a package reference to the .NET-DeviceAPI.

For example, the statements

mkdir TestProject
cd TestProject
dotnet new console
dotnet add package SigDeviceAPI

create a new .NET console application and add a package reference to the DeviceAPI.

Clearing the local http-cache of the NuGet client

There are situations in which the local caching prevents the NuGet client
from discovering new packages recently added to the feeds.

Using the .NET CLI, the statement

dotnet nuget locals http-cache --clear

clears the local http-cache.

Using nuget.exe, the statement

nuget locals http-cache -clear

has the same effect.