Ixxat.Vci4 4.1.6

There is a newer version of this package available.
See the version list below for details.
dotnet add package Ixxat.Vci4 --version 4.1.6                
NuGet\Install-Package Ixxat.Vci4 -Version 4.1.6                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Ixxat.Vci4" Version="4.1.6" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Ixxat.Vci4 --version 4.1.6                
#r "nuget: Ixxat.Vci4, 4.1.6"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Ixxat.Vci4 as a Cake Addin
#addin nuget:?package=Ixxat.Vci4&version=4.1.6

// Install Ixxat.Vci4 as a Cake Tool
#tool nuget:?package=Ixxat.Vci4&version=4.1.6                

VCI4 .NET Wrapper

Introduction

This project contains the source of the VCI4 .NET Wrapper (VCI4 = Virtual Communication Interface Version 4), a component that provides access to the VCI4 C++-API. VCI4 is a driver/application framework to access HMS CAN or LIN interfaces on the Windows OS, for details see https://www.ixxat.com/technical-support/support/windows-driver-software

This package is released as a binary package via NuGet for application developers, for details see https://www.nuget.org/packages/Ixxat.Vci4 There is also a strong named variant which is available from https://www.nuget.org/packages/Ixxat.Vci4.StrongName

Open source

The main purpose to release this component as open source is to give application developers a better insight into the internal workings of the component. As it is mostly a 1:1 wrapper to the underlying VCI4 C++-API there is little encoded functionality, nethertheless access to the source could help clarify unclear behaviour or help detect bugs.

Developers which need more control could alter the component or use it as a template to implement their own device access component on top of the VCI4 C++-API.

For users

See the user documentation in /doc/README.md

For developers

The component is split into three parts:

  • a contract assembly (interface declaration assembly)
  • a loader
  • a managed C++ implementation

The C++ part is compiled twice to x86 and x64 targets. A .NET application only references the loader and the contract assembly and could therefore be kept target agnostic (AnyCPU). The loader checks the platform and loads the corresponding target specific assembly.

To compile the component start a Powershell console and execute

PS> .\build.ps1 -Version=4.1.0

If you want to create a strong named version add the AssemblyKeyFile parameter

PS> .\build.ps1 -Version=4.1.0 -AssemblyKeyFile=mykeyfile.snk

For more information have a look at the build script .\build.ps1

Prerequisites

  • VisualStudio 2022
  • nuget.exe client version 6.3.0
  • Sandcastle Help File Builder version 2021.11.7.0

The VCI4 .NET wrapper sits on top of the VCI4 C++ API so you need the VCI4 driver setup installed.

Source tree overview

\doc           user documentation
\images        package icon
\nuget         files for nuget packaging (manifest files)
\src\contract  Contract assembly
\src\help      Help file builder project
\src\loader    Loader component (API entry point)
\src\impl      Component implementation (mixed assembly source)
\samples       minimal set of samples

Further documentation

See the folder /doc/manual for the user manuals which also gives a system overview.

Installing the VCI4 Setup provides additional manuals for the available VCI4 APIs.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net5.0-windows10.0 is compatible.  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.  net6.0-windows10.0 is compatible.  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. 
.NET Core netcoreapp3.1 is compatible. 
.NET Framework net40 is compatible.  net403 was computed.  net45 was computed.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
  • .NETCoreApp 3.1

    • No dependencies.
  • .NETFramework 4.0

    • No dependencies.
  • net5.0-windows10.0

    • No dependencies.
  • net6.0-windows10.0

    • No dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
4.1.7 338 5/17/2024
4.1.6 2,406 2/19/2024
4.1.5 145 2/9/2024
4.1.4 4,259 10/16/2023
4.1.3 405 10/5/2023
4.1.2 687 7/27/2023
4.1.1 4,901 1/25/2023
4.1.0 526 11/11/2022
4.0.436 17,622 12/14/2018
4.0.423 2,272 10/23/2018
4.0.355 2,749 2/9/2017
4.0.346 1,007 2/7/2017
4.0.340 952 2/2/2017
4.0.328 1,148 12/22/2016
4.0.324 974 12/16/2016
4.0.314 1,060 12/7/2016
4.0.308 978 12/6/2016
4.0.304 1,074 11/30/2016
4.0.291 1,004 11/24/2016
4.0.288 1,106 11/18/2016
4.0.255 1,039 8/30/2016

Resolved issues:
- fix CanCyclicTXMsg2::AutoIncrementIndex maximum check (CANFD data len, 0..63)
- update sample to set cyclicMsg.AutoIncrementMode
- fix internal dirty flag handling in cyclic message objects: setting the same AutoIncrementMode cleared the internal dirty flag and led to msg start to fail