32feet.NET

Closed Issue: [Widcomm] Duplicate devices in DiscoverDevices, from Inquiry found and name callbacks

alanjmcf — Tue, 06 Jan 2009 12:29:51 GMT

The Widcomm device-discovery API can generate two events (callbacks) for the same device. This happens when the device was not previously known, and thus we get a callback when the device is discovered and a second event when the name of the device has been retrieved. We need to remove the first device instance to remove the duplication.

Source code checked in, #45548

alanjmcf — Tue, 06 Jan 2009 12:29:51 GMT

[widcomm] When Widcomm device Inquiry returns a device twice, replace the first rather than add a duplicate -- the second time occurs when its name is retrieved. Fixes #20462.

Created Issue: [Widcomm] Duplicate devices in DiscoverDevices, from Inquiry found and name callbacks

alanjmcf — Tue, 06 Jan 2009 11:29:12 GMT

Commented Issue: [Widcomm] BluetoothClient.Connected property should report state as of "the last Send or Receive operation"

alanjmcf — Tue, 06 Jan 2009 10:56:20 GMT

The current Connected property reports the current state of the connection to the device. According to MSDN:
"Gets a value that indicates whether a Socket is connected to a remote host as of the last Send or Receive operation. "
and similar on TcpClient, and
"The Connected property gets the connection state of the Client socket as of the last I/O operation. When it returns false, the Client socket was either never connected, or is no longer connected."

This was most noticeable on the current implementation in the preliminary WidcommBluetoothListener code, if the remote device, connected, sent data, and closed immediately, then the accept operation could fail because the stream was !Connected by that time.
This will also be visible in some scenarios from user code.
Comments:

Probably add a method in BtIf.cpp, "BtIf_HasRemoteDeviceInfoEx" which returns a bool and sets two static variables with the two function pointers (GetRemoteDeviceInfoEx and GetNextRemoteDeviceInfo). Uncomment the current native mapping methods and have both call that method first and return an error if it returns false, otherwise continue and do the Get/Next operations using the function pointers. In the managed code, call the 'HasRemoteDeviceInfoEx' method (once) and decide thus whether to call the Registry or API versions.

Win32 doesn't have the GetRemoteDeviceInfoEx so the Registry lookup will continue to be used. It does have "GetRemoteDeviceInfo" but there's apparently no way to get all devices, one has to supply a Class-of-device value for it to filter by -- unless 0 matches all. Anyway lets not worry about that for now until a user reports if the Registry lookup fails there too.

Created Issue: [Widcomm] BluetoothClient.Connected property should report state at "the last Send or Receive operation"

alanjmcf — Tue, 06 Jan 2009 10:46:40 GMT

Created Issue: [Widcomm] No "HKLM\Software\WIDCOMM\BTConfig\Devices\" on modern(?) Widcomm versions

alanjmcf — Tue, 06 Jan 2009 10:39:25 GMT

A tester with an WM device with Widcomm "1.8.5 Build 0300" reports that devices are not stored at the Registry location the current code uses. Thus the current code fails at InTheHand.Net.Bluetooth.Widcomm.WidcommBtInterface.ReadKnownDevicesFromRegistry() with:
if (rkDevices == null) // IOException is what GetValueKind throws.
throw new System.IO.IOException("Widcomm 'Devices' key not found in the Registry.");

We need to find some other way of finding the 'remembered' devices, either at another Registry location (unlikely?), or through using the WCE CBtIf::GetRemoteDeviceInfoEx() method. However it is not present on older devices (nor on Win32), so we will have to have the native code look that method up at runtime (GetProcAddress etc).

Source code checked in, #45496

alanjmcf — Sat, 03 Jan 2009 21:58:33 GMT

[widcomm] Move some test helper methods to a utility class.

Source code checked in, #45493

alanjmcf — Sat, 03 Jan 2009 15:38:31 GMT

[widcomm] Eeechhh! Fix the CF builds.

Source code checked in, #45492

alanjmcf — Sat, 03 Jan 2009 15:29:25 GMT

[widcomm] Suppress another two Asserts.

Source code checked in, #45491

alanjmcf — Sat, 03 Jan 2009 15:22:32 GMT

[widcomm] Have the code suppress the Debug.Asserts when running NUnit tests.

Source code checked in, #45490

alanjmcf — Sat, 03 Jan 2009 15:20:07 GMT

[widcomm] Add test Connect_PeerImmediatelyCloses. Added EventFirer classes.

Source code checked in, #45489

alanjmcf — Sat, 03 Jan 2009 13:52:02 GMT

[widcomm] Device-/ConsoleMenuTesting: have console.ReadLine take a prompt string, have DeviceMenuTesting use a MsgBox with Yes and No buttons rather than needing to type y or n.

Source code checked in, #45488

alanjmcf — Sat, 03 Jan 2009 13:41:00 GMT

[widcomm] Remove not-impl-ex failures in Lsnr tests.

Source code checked in, #45487

alanjmcf — Sat, 03 Jan 2009 13:39:30 GMT

[widcomm] Update widcomm doc, noting that Close currently just discards any pending data.

Source code checked in, #45486

alanjmcf — Sat, 03 Jan 2009 13:36:53 GMT

[widcomm] Update the build configuration for the new DeviceMenuTesting project.

Source code checked in, #45485

alanjmcf — Sat, 03 Jan 2009 13:36:15 GMT

[widcomm] WidcommRfcommStream: Move the clearing of the m_arConnect operation from EndXxxx to completion (HandlePortEvent), and store the completed event in another field, so we can argument check the AR passed into the EndXxxx methods. Doing the clear at completion because another event (e.g. CONNECT_ERR if the peer immediately closes) can come before EndXxxx has been called.

Source code checked in, #45467

alanjmcf — Fri, 02 Jan 2009 13:44:46 GMT

[widcomm] Update the Widcomm doc.

Source code checked in, #45466

alanjmcf — Fri, 02 Jan 2009 13:40:16 GMT

[widcomm] ConsoleMenuTesting/etc: use cli.RemoteEndPoint etc in ListenAndImmediatelySendAndClose_.

Source code checked in, #45465

alanjmcf — Fri, 02 Jan 2009 13:39:07 GMT

[widcomm] Have SdpBrowserDesktop device list use the Rssi property.

Source code checked in, #45464

alanjmcf — Fri, 02 Jan 2009 13:38:06 GMT

[widcomm] Flush some Dispose/Finalizer changes on WidcommBluetoothListener.