VmbNET.linux-arm64
1.2.0
See the version list below for details.
dotnet add package VmbNET.linux-arm64 --version 1.2.0
NuGet\Install-Package VmbNET.linux-arm64 -Version 1.2.0
<PackageReference Include="VmbNET.linux-arm64" Version="1.2.0" />
<PackageVersion Include="VmbNET.linux-arm64" Version="1.2.0" />
<PackageReference Include="VmbNET.linux-arm64" />
paket add VmbNET.linux-arm64 --version 1.2.0
#r "nuget: VmbNET.linux-arm64, 1.2.0"
#:package VmbNET.linux-arm64@1.2.0
#addin nuget:?package=VmbNET.linux-arm64&version=1.2.0
#tool nuget:?package=VmbNET.linux-arm64&version=1.2.0
VmbNET
The .NET API of the Vimba X SDK.
Vimba X is a fully GenICam compliant SDK and the successor of Vimba. VmbNET is the .NET API that is provided by this SDK. It provides access to the full functionality of Vimba X from .NET applications.
VmbNET can be used on Windows64, Linux64 and Linux ARM.
Installation
To use VmbNET, a .NET runtime providing .NET Standard 2.0 is required.
These are .NET Framework 4.6.2 or above and .NET Core 2.0 or above.
A ready-to-install nuget package
for VmbNET (whose file name ends with .nupkg) that conforms to .NET Standard 2.0
can be found as part of the Vimba X installation.
This nuget package can be installed in an application in various ways.
1. Installation with Visual Studio 2019 (Windows64 only)
After opening your application's project file with Visual Studio 2019,
- Open the NuGet Package Manager for the project by right-clicking it in Solution Explorer
and selecting
Manage NuGet Packages.... - Click the cog wheel after
Package source:to open the package sources, and add the full path to the directory containing the.nupkgfile by clicking the+icon and entering this path into theSource:field. TheName:field can be whatever you like, but you will need it just now. Close this window to return to the NuGet Package Manager. - Open the drop-down menu after
Package source:and either selectAllor theName:field value you used when adding the package source for VmbNET. - Select the "Browse" tab and search for
VmbNET. Clik the VmbNET NuGet package that is displayed. - In the pane that appears, click
Installto install the version shown.
2. Installation from the command line
- Add the full path to the directory containing the
.nupkgfile by executing
dotnet nuget add source <path-to-directory-containing-VmbNET-NuGet-package> -n <user-chosen-name-for-this-package-source>
- Install VmbNET to your package by changing directory to the location of your project file and executing
dotnet add package VmbNET
- Then build your application by changing directory to the location of your project file and executing
dotnet build -c Release .
Usage
Below is a minimal example demonstrating how to acquire frames for 2 seconds from the stream of the first camera found by VmbNET. It
highlights the general usage of VmbNET. More complete code examples can be found in the Examples
directory.
using VmbNET;
class Program
{
static void Main()
{
using var vmb = IVmbSystem.Startup(); // API startup (loads transport layers)
var cam = vmb.GetCameras()[0]; // Get the first available camera
using var openCam = cam.Open(); // Open the camera
openCam.Features.ExposureTime = 5000.0; // Set the exposure time value
// Register an event handler for incoming frames
openCam.FrameReceived += (s,e) =>
{
using var frame = e.Frame;
Console.WriteLine($"Frame Received! ID={frame.Id}");
}; // IDisposable: Frame is automatically requeued
// Convenience function to start acquisition
using var acquisition = openCam.StartFrameAcquisition();
Thread.Sleep(2000);
} // IDisposable: Stops acquisition, closes camera, shuts down Vimba X
}
Versioning
To avoid manually looking after any versioning strings, the version of the NuGet package as well as the various assembly versions are created automatically during the build process from the last git tag, excluding the release candidate information. For example, if the git tag is "1.1.0_RC4", the version will be "1.1.0".
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
| .NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
| .NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
| .NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
| MonoAndroid | monoandroid was computed. |
| MonoMac | monomac was computed. |
| MonoTouch | monotouch was computed. |
| Tizen | tizen40 was computed. tizen60 was computed. |
| Xamarin.iOS | xamarinios was computed. |
| Xamarin.Mac | xamarinmac was computed. |
| Xamarin.TVOS | xamarintvos was computed. |
| Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- Microsoft.CSharp (>= 4.7.0)
- Microsoft.Extensions.Logging.Abstractions (>= 8.0.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.