Installation and release compatibility
This section details the release compatibility and installation for P4API.NET.
Installation
The simplest way to install P4API.NET is using the NuGet package manager. Alternatively libraries can be added manually from the archive.
https://www.nuget.org/packages/p4api.net
Alternative manual install from archive
Alternatively, libraries can be added manually from the archive:
- Following assemblies must be in the build output directory:
For Windows:
p4api.net.dll and p4bridge.dll
For Linux:
p4api.net.dll and libp4bridge.so
For macOS:
p4api.net.dll and libp4bridge.dylib
- On creation of a new console application, the Debug output location would be:
For Microsoft .NET framework:
...\SolutionDir\ProjectDir\bin\Debug\.
For Microsoft .NET Core:
...\SolutionDir\ProjectDir\bin\Debug\net6.0\
- Add the p4api.net.dll as a project reference by clicking Add Reference... on the References node of the project in the solution explorer in Visual Studio and browsing to the location of the newly added p4api.net.dll.
Download P4API.NET from one of the following locations:
Release compatibility
P4API.NET is subject to change from release to release, and is not guaranteed to be source-code compatible from one release to the next. However, clients that you create using P4API.NET can run against previous releases of the Helix Core Server and will probably run against later releases of the Helix Server.
Support for specific features depends on the version of Helix Server and P4API.NET that you use.