When using compilers for languages like C#, VB.NET or F#, you can determine the assemblies that need to be installed with your application simply by building your project, and then taking the files from compiler's output directory (e.g. bin/Release).
Alternatively, you can simply deploy all .DLL files from Assemblies\net47 subdirectory (in the installation directory of the product). Files from the Assemblies\net47\Design subdirectory need not and should not be deployed.
You may omit from the installation
Please refer to “Product Parts” chapter for description of purpose of individual assemblies. You will find them under the Assemblies\net47 subdirectory (in the installation directory of the product).
The assemblies need to be placed so that the referencing software (your application) can find them, according to standard Microsoft .NET loader (Fusion) rules. The easiest is to simply place the assembly files alongside (in the same directory as) your application file.
There are other methods of how assemblies can be located, including their installation to GAC (Global Assembly Cache). Which method you use depends on the needs of your application. Unless you have a compelling need, however, we do not recommended installing the assemblies into the GAC.
Remember that in .NET Standard, the deployment will contain not only the files of your application and QuickOPC files, but also the files from NuGet packages that QuickOPC depends on, and that you have to comply with their licensing requirements as well.
In .NET Core, the assemblies that become the part of the deployment are determined and included automatically by the tools that build the deployment. For more information, see Microsoft's article .NET Core application deployment.
If your application needs to use OPC UA PubSub Ethernet mapping, or it needs to work with Wireshark capture files, you also need to install:
In addition, you need to comply with LGPL requirements of PacketDotNet and SharpPcap.