Go to file

Benjamin Höglinger-Stelzer 7509e6db71 Update README.md		2024-07-13 15:37:19 +02:00
assets	Added logo	2022-09-26 20:54:12 +02:00
Nefarius.Peripherals.SerialPort	Migrated all legacy PInvoke	2024-07-13 15:28:19 +02:00
PInvokeSerialPort.Sample	Works with test hardware	2022-10-03 17:25:19 +02:00
PInvokeSerialPort.Test	Works with test hardware	2022-10-03 17:25:19 +02:00
.editorconfig	Updated to latest packages	2024-07-13 14:48:28 +02:00
.gitignore	More fixes	2024-07-13 14:15:41 +02:00
appveyor.yml	Updated to VS 2022	2022-10-03 17:30:39 +02:00
LICENSE	Corrected copyright notice	2019-12-29 16:49:00 +01:00
Nefarius.Peripherals.SerialPort.sln	Works with test hardware	2022-10-03 17:25:19 +02:00
Nefarius.Peripherals.SerialPort.sln.DotSettings	Attempting fixes	2022-10-03 02:27:27 +02:00
nuget.config	Updated to latest packages	2024-07-13 14:48:28 +02:00
Package.nuspec	v1.0.1	2017-03-03 18:56:45 +03:30
PInvokeSerialPort.vsmdi	Initial commit	2012-03-03 13:20:54 +03:30
ProjectIcon.png	+ Icon	2012-03-03 21:17:06 +03:30
README.md	Update README.md	2024-07-13 15:37:19 +02:00

Nefarius.Peripherals.SerialPort

Like System.IO.Ports.SerialPort but actually works 😏

About

Originally copied from John Hind - "Use P/Invoke to Develop a .NET Base Class Library for Serial Device Communications" that I guess licensed under Ms-PL so this project is also under Ms-PL. (Update: well, after the years now I think this was not a true claim, but well I don't think MS will sue anyone because a sample intended for public use)

It is useful in the cases System.IO.Ports.SerialPort is not working well (for connecting to \\.\... devices)

System.IO.Ports.SerialPort is terrible and this is exactly what I've experienced in a project so this library came to the rescue.

Consume the NuGet via Install-Package Nefarius.Peripherals.SerialPort