Closed VPeruS closed 5 years ago
Thank you for the report. Even if the underlying device driver is removed, the object still needs to be closed to free up resources - the library doesn't do this automatically (that would lead to memory errors). Have you tested the MS implementation? If this differs to MS, then I'll certainly consider a change to improve compatibility
Yes, it different from MS's, their IsOpen starts to returns false after device removed.
Thankyou. I'll consider this a bug.
Please note, that the IsOpen now returns false when the device is physically removed, but the SerialPortStream still needs to be closed. Resources are still being held.
After device manual disconnection IsOpen property of SerialPortStream continue to return true. We using USB to COM converted, host system Windows 7.
Code that was used for testing
After disconnect s.WriteByte will continuously throw exception