nefarius/Nefarius.Peripherals.SerialPort
1
0
Fork 0
Code Issues Pull Requests Activity
49 Commits 1 Branch 5 Tags 296 KiB
C# 100%
c8b8859dbe
Go to file
Benjamin Höglinger-Stelzer c8b8859dbe Updated README
2022-09-26 23:53:14 +02:00
assets Added logo 2022-09-26 20:54:12 +02:00
Nefarius.Peripherals.SerialPort Clean-up 2022-09-26 23:51:23 +02:00
PInvokeSerialPort.Sample Renamed solution and project file 2022-09-26 20:52:14 +02:00
PInvokeSerialPort.Test Disabled building tests for now 2022-09-26 21:49:14 +02:00
.gitignore Converted class library into SDK format 2018-11-25 13:54:47 +01:00
appveyor.yml Updated to VS 2022 2022-09-26 21:50:41 +02:00
LICENSE Corrected copyright notice 2019-12-29 16:49:00 +01:00
Nefarius.Peripherals.SerialPort.sln Disabled building tests for now 2022-09-26 21:49:14 +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 Updated README 2022-09-26 23:53:14 +02:00

README.md

Nefarius.Peripherals.SerialPort

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)

Motivation behind this fork

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

Download

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