developed by pombeirp
column indicates how many devices have been reported as compatible. Conversely the 
column indicates how many devices have been reported as incompatible. 
Sat, 17 May 2008 00:28:41
Bluetooth ActiveSync Toggle Utility
After looking around on the internet for some kind of utility that allowed me to quickly establish a Bluetooth ActiveSync connection to my laptop, I've decided to take the plunge and write my first Windows Mobile utility. Basically, this utility does the following:
First run: Enables Bluetooth, if not already enabled. Instructs ActiveSync to connect to a device (specified in the PartnerId.cfg file);
Second run: Disables Bluetooth, thereby ending ActiveSync connection. If ActiveSync is synchronizing, the utility will wait until ActiveSync is done.
This allows me to quickly setup and tear down a sync session, without having to stare at the screen waiting for ActiveSync to be done until I can take Bluetooth down! In my case, I've assigned the utility to a physical device key that now serves as a sync toggle.
This tool was tested on a WM6 emulator and a WM6 HTC Touch Dual, although there is no reason it wouldn't run on a WM5 device. It requires .NET CF 2. In order for the utility to know which machine to try to connect to, you need to edit the PartnerId.cfg file located in the install folder.
Enjoy!
First run: Enables Bluetooth, if not already enabled. Instructs ActiveSync to connect to a device (specified in the PartnerId.cfg file);
Second run: Disables Bluetooth, thereby ending ActiveSync connection. If ActiveSync is synchronizing, the utility will wait until ActiveSync is done.
This allows me to quickly setup and tear down a sync session, without having to stare at the screen waiting for ActiveSync to be done until I can take Bluetooth down! In my case, I've assigned the utility to a physical device key that now serves as a sync toggle.
This tool was tested on a WM6 emulator and a WM6 HTC Touch Dual, although there is no reason it wouldn't run on a WM5 device. It requires .NET CF 2. In order for the utility to know which machine to try to connect to, you need to edit the PartnerId.cfg file located in the install folder.
Enjoy!
