derek-will

> Can you elaborate on what your expectations were? My expectation was that the same address information that was passed into `bind` would be retrieved by a call to `getsockname`....

I will test within the next week to verify running conditions on Windows OS.

Update: I have a Windows PC partially set up. Will provide verification soon.

Yes, confirmed SocketCANSharp runs on Windows via WSL2. You will need to build and run your own custom kernel with CAN support enabled and then install dotnet in your WSL2...

Your observation is 100% correct. The reason why I provide so many overloads is to allow the .NET marshaller to do most of the heavy lifting for us. In most...

Interesting! Leveraging the base class `SafeHandle` of `SafeFileDescriptorHandle` everywhere possible. I like that this change, although large in scale, is essentially backwards compatible. I am considering the pros and cons.

> SafeHandle is designed to manage IntPtr more safely, and SafeFileDescriptorHandle basically just override a method and a property. So, It's actually quite safe to make this change. [`SafeFileDescriptorHandle`](https://github.com/derek-will/SocketCANSharp/blob/develop/src/SocketCANSharp/SafeFileDescriptorHandle.cs) is...

> Users can customize SafeHandle. Users should always be using the `SafeFileDescriptorHandle` returned from either `Socket()` or `EpollCreate()` functions in `LibcNativeMethods` class. I am unsure of what a customization use-case...

> More consistent with the design pattern. I've been considering this. [Parameter Design Guidelines](https://learn.microsoft.com/en-us/dotnet/standard/design-guidelines/parameter-design) on Microsoft's site state the following: > ✔️ DO use the least derived parameter type that...

> By the way, the repo have any discussions or discord? I have some new features want to discuss with you all. It has just been me working on this...