System.PlatformNotSupportedException: System.IO.Ports is currently only supported on Windows. on Archlinux

[Foxlider]

Description

When using IO Ports on ArchLinux System and dotnet 7.0 or 6.0 I get an exception System.PlatformNotSupportedException: System.IO.Ports is currently only supported on Windows.

SerialPort.GetPortNames() works but not SerialPort()

Reproduction Steps

1. Make new console application on dotnet 6 or 7
2. Add the code snippet below
3. Run on different Linux systems

Expected behavior

Access to UART Serial ports

Actual behavior

Exception thrown

Regression?

No response

Known Workarounds

None so far

Configuration

Dotnet Version

╰─ dotnet --list-sdks    
6.0.111 [/usr/share/dotnet/sdk]
7.0.100 [/usr/share/dotnet/sdk]

╰─ dotnet --list-runtimes 
Microsoft.AspNetCore.App 6.0.11 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 7.0.0 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.11 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.0 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

OS Version, kernel

╰─ lsb_release -a
LSB Version:    n/a
Distributor ID: EndeavourOS
Description:    EndeavourOS Linux
Release:        rolling
Codename:       rolling


╰─ uname -a
Linux keelah-dellG15 6.0.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 16 Nov 2022 17:01:17 +0000 x86_64 GNU/Linux

CPU Architecture :

╰─ uname -m
x86_64

From what I've seen on the forums, it works on certain linux distros but not on others such as Manjaro and EndeavourOS (both running archlinux) and might be the same on other more obscure linux distros

Other information

A few lines of code I used on my console program :

//DEFAULT port sur /dev/ttyUSB0
string SERIALPORT = "/dev/ttyUSB0";

//Line below works
List<string> ports = SerialPort.GetPortNames().ToList();
SERIALPORT = ports.Last();

//Crash on line below
SerialPort _serialPort = new SerialPort(SERIALPORT, BAUDRATE, Parity.None, 8, StopBits.One);

_serialPort.ReadTimeout = -1;       // |Pas de timeout
_serialPort.WriteTimeout = -1;      // |
_serialPort.Handshake = Handshake.None;
_serialPort.DataReceived += _serialPort_DataReceived;

[Foxlider]

I had TargetFramework on <TargetFramework>net6.0</TargetFramework> and tried net7.0 too.
Also had <PackageReference Include="System.IO.Ports" Version="7.0.0" />

I'll check your code on my Arch..

[krwq]

What RID does your dotnet --info show (second section of the output under Runtime Environment)?

[Foxlider]

RID is arch-x64

Still have the same error on the GetPortsName though

[krwq]

@Foxlider if you have some time to experiment...
I'm curious if you published for linux-x64 (dotnet publish -r linux-x64 and then run binary produced under bin/.../publish) - there is a chance it will just work. Or alternatively you could copy & paste System.IO.Ports binaries from linux-x64 (there should be .dll and .so file) to your other build (replace existing ones)

We seem to not produce bits for arch-64 currently but I'm curious if we could just make arch use linux bits.

[Foxlider]

So it seems publishing with linux-x64 works and so is dotnet run -r linux-x64
I am not sure why arch-x64 is considered as a different system as linux since it still uses the linux kernel as any other linux system. Or if there is a difference, I am unsure what it is

[krwq]

@Foxlider I'm guessing some of the native components in different areas need some arch specific binaries. Having said that I think arch should extend linux RID and IMO we should be picking up linux-x64 package if arch-x64 is not present. I'll see if I can find someone who knows what needs to be changed to fix this.

[krwq]

cc: @ViktorHofer

[ViktorHofer]

I followed @am11 sample from above and didn't get a PlatformNotSupportedException when performing a dotnet run but the intended output: "Done" on my Arch distro.

@Foxlider can you please share a minimal but complete repro?

[Foxlider]

Let me know if you need anything.

I tried a minimal code with a dotnet new console and simply adding the SerialPort.GetPortNames() and still had the issue