How are you building and packing about usb.events

[Jinjinov]

Thank you, I am glad you like it!

Yes, that is exactly what I am doing. I write the code in Windows and I share the solution folder with a Linux virtual machine, so that when I build in Linux, the built binary is already in the correct folder.

To see how the native C code is built with gcc, look at: https://github.com/Jinjinov/Usb.Events/blob/master/Usb.Events/Usb.Events.csproj#L40

[KZeronimo]

Awesome - thanks for the quick response - on the topic of building and artifacts have you considered using semver for the version number major.minor.patch - seems more canonical in the .NET shared lib world

[Jinjinov]

I have, in fact, considered it :)

I admit that according to https://semver.org/ my versioning violates one rule of the Backus–Naur Form Grammar for Valid SemVer Versions. That one rule is that the last separator should be a - or a + but not a dot.

On the other hand, in the Visual Studio IDE in the Package tab of the project Properties window, there are four text input boxes for the Assembly version. When you use them, VS writes the four values separated by dots, so in the end I decided to use that.

I agree that it is not canonical, but I find the binary version notation amusing :) My little joke in the otherwise depressing 2020.