Sign in
|
Join
|
Help
|
Search
.NET Components for Mobility
Home
Products
Services
Blogs
Forums
Library
Downloads
About
This Blog
Home
Syndication
RSS
Atom
Comments RSS
Recent Posts
Closed Issue: An exception in HandleDiscoveryComplete causes Connect to hang
Created Issue: An exception in HandleDiscoveryComplete causes Connect to hang
Closed Issue: [widcomm] NETCF BtCli.Connect hangs due to broken out-of-date DLL detection in WidcommBtIf.ReadDiscoveryRecords
Created Issue: [widcomm] NETCF BtCli.Connect hangs due to broken out-of-date DLL detection in WidcommBtIf.ReadDiscoveryRecords
Created Issue: [widcomm] Current SocketExceptions include the base message which is just confusing!
Archives
February 2008
(10)
January 2008
(5)
December 2007
(7)
November 2007
(3)
September 2007
(5)
August 2007
(6)
July 2007
(2)
32feet.NET
Closed Issue: An exception in HandleDiscoveryComplete causes Connect to hang
As seen in bug #23313. Comments: Resolved with changeset 55741. Read More...
Posted
Jun 30 2009, 08:20 AM
by
32feet.NET
Created Issue: An exception in HandleDiscoveryComplete causes Connect to hang
As seen in bug #23313. Read More...
Posted
Jun 30 2009, 08:19 AM
by
32feet.NET
Closed Issue: [widcomm] NETCF BtCli.Connect hangs due to broken out-of-date DLL detection in WidcommBtIf.ReadDiscoveryRecords
A new version of native function BtIf_ReadDiscoveryRecords was required (bug #22999), and was added as BtIf_ReadDiscoveryRecordsServiceClassOnly. WidcommBtIf.ReadDiscoveryRecords detect if the old DLL is being used and falls-back...
Posted
Jun 30 2009, 08:17 AM
by
32feet.NET
Created Issue: [widcomm] NETCF BtCli.Connect hangs due to broken out-of-date DLL detection in WidcommBtIf.ReadDiscoveryRecords
A new version of native function BtIf_ReadDiscoveryRecords was required (bug #22999), and was added as BtIf_ReadDiscoveryRecordsServiceClassOnly. WidcommBtIf.ReadDiscoveryRecords detect if the old DLL is being used and falls-back...
Posted
Jun 30 2009, 08:17 AM
by
32feet.NET
Created Issue: [widcomm] Current SocketExceptions include the base message which is just confusing!
e.g. "InTheHand.Net.Bluetooth.Widcomm.NoResultCodeWidcommSocketException: WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable; ; StartInquiry" As we know...
Posted
Jun 24 2009, 07:19 AM
by
32feet.NET
Created Issue: [widcomm] On XP at least, a (empty) radio instance is returned when no dongle is present
With Widcomm stack installed and functional, but with no dongle plugged in WidcommBluetoothRadio..ctor still returns a new instance. All the natoive methods fails so we could know that there's no radio present. The problem here is that my iPAQ often...
Posted
Jun 24 2009, 07:16 AM
by
32feet.NET
Commented Issue: [widcomm] Diagnosis of failure to load Widcomm support is very difficult
In the release version we don't display any Assert dialogs reporting why each stack failed to initialise. If we did then end users would always see one dialog, i.e. if they have MSFT stack they'd see the Widcomm failed report, and if they...
Posted
Jun 24 2009, 05:06 AM
by
32feet.NET
Created Issue: Diagnosis of failing Widcomm support is very difficult
In the release version we don't display any Assert dialogs reporting why each stack failed to initialise. If we did then end users would always see one dialog, i.e. if they have MSFT stack they'd see the Widcomm failed report, and if they...
Posted
Jun 24 2009, 04:52 AM
by
32feet.NET
Closed Issue: [widcomm] Reports "May only be one instance of WidcommBtIf." on initialisation after failure
If Bluetooth initialisation fails to load any stack, then the second time we try to intialise will fail with InvalidOperationException("May only be one instance of WidcommBtIf.") instead of the actual error[1]. We need to...
Posted
Jun 24 2009, 04:23 AM
by
32feet.NET
Created Issue: [widcomm] Reports "May only be one instance of WidcommBtIf." on latter attempts
If Bluetooth initialisation fails to load any stack, then the second time attempting to intialise will fail with InvalidOperationException("May only be one instance of WidcommBtIf.") instead of the actual error[1]. We need to reset...
Posted
Jun 24 2009, 04:19 AM
by
32feet.NET
Created Feature: SetBluetoothPin on ObexWebRequest
For use When the server (might) need bonding. Can just call through to BluetoothClient.SetPin... Read More...
Posted
Jun 22 2009, 08:20 AM
by
32feet.NET
Created Issue: [widcomm] BluetoothListener doesn't listen without call to Begin-/Accept
Read More...
Posted
Jun 18 2009, 03:08 PM
by
32feet.NET
Created Issue: ObexWebRequest doesn't include ConnectionID, affects FTP connections
Read More...
Posted
Jun 17 2009, 08:54 AM
by
32feet.NET
Created Issue: ObexWebRequest mis-parses FTP packets and affects packet size
Read More...
Posted
Jun 17 2009, 08:54 AM
by
32feet.NET
Created Issue: More ObexWebRequest use of Stream.Read is not correct, it doesn't check the buffer has the correct number of bytes
Read More...
Posted
Jun 17 2009, 08:53 AM
by
32feet.NET
More Posts
Next page »
Copyright © 2001-2009
In The Hand Ltd
. All rights reserved.
Terms of Use
and
Privacy Policy
.