-
-
Notifications
You must be signed in to change notification settings - Fork 122
PR#215 Breaking on .Net Framework 4.8 #222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@andyvorld do you think it could be solved with #ifs? |
I just tried with the following, Device.Net\Windows\ApiService.cs
Hid.Net\Windows\WindowsHidApiService.cs
That seems to have fixed my issue not having anything written, only when including the net45 build, while the netstandard2.0 builds still have the same issue. |
@andyvorld does the same issue occur if you target .net 5? |
@andyvorld you could submit a PR. I will probably do a new release fairly soon. |
Using the nuget packaged 4.2.1, it works fine.
EDIT2: Sorry I forgot to clean the build cache, so there were some conflicts between the binaries, rebuilt my test script in .Net5 with the changes and it works find with Ill make a pull request now with my edits. I am not sure if I am using the compiled dlls as expected, as for my .Net 5 test, using the binaries from the standard2.0 output of HID.Net fails at run time, while the net45 binaries works. Which after going through visual studio's debugger showed that the
|
Uh oh!
There was an error while loading. Please reload this page.
Describe the issue
#215 seems to be causing some issues with on .Net Framework 4.8.
WriteAsync
andWriteReadAsync
seems to fail silently, with nothing written to the HID device, probed with USBPcap/wireshark. Using HID.Net 4.2.1 on .Net 5 or downgrading to 4.0.0 seems to solve the issue.From what I can tell, this issue for .Net 4.8 occured at commit a45152e, using git bisect.
This maybe just be an issue with my specific HID device (Logitech G403).
Your Code
The following code is sending an invalid probe to a Logitech HID++ 2.0 device.
Info
The text was updated successfully, but these errors were encountered: