I'm developing an application which connects to a custom hardware unit
via Bluetooth. I'm experiencing different behaviour in the phase of
connecting to the unit depending on which target device I'm selecting
in Visual Studio 2005.
I'm using a HTC P3600 (Bluetooth 2.0) with Windows Mobile 5.0 Pocket
PC. The custom unit is sampling data from a number of channels and
sending the data via Bluetooth (2.0) in a custom format. Coding in
Visual Studio Professional / C#.
An example scenario where the problem happens:
1. Add the unit to the list of devices in the Bluetooth control panel.
(enter pairing key, select serial port service)
2. Add an outgoing com port.
3. Activate a configure function which opens the com port and sends a
4. Activate a start function which sends a start message to the unit.
The unit now sends sampled data back to me.
If I have chosen 'Windows Mobile 5.0 Pocket PC Device' as target device
I get a pop up message at step 3 telling me that the unit is trying to
connect to me and asks if I want to add it to my list of devices. I
select 'yes' and I have to enter the paring key and select the serial
port service again. Now the outgoing com port is gone and as well the
unit in the list of devices. So I have to perform step 1 and 2 again.
If I say 'no' to adding the unit to my list of devices the unit and the
com port are left untouched and I can proceed to step 4 with the
configuration message in step 3 beeing recieved nicely by the unit.
If I have chosen 'Windows CE 5.0 Device' as target device I never get
the pop up and step 3 and 4 works like it should.
What's the difference in the two choices of target device that results
in this behaviour? Can I change some settings to avoid the behaviour
when selecting WM 5.0 PPC target device?
Since I'm using a Pocket PC device it seems like I shouldn't be
selecting CE. However, every thing works nice when using CE as target
device (what I can see so far). Am I just lucky that everything works
nicely on CE target device? Will I be unable to access some
functionality in the WM 5.0 sdk when using CE target device?
1. I'm posting in an appropriate group.
2. My swedish -> english works for you all out there.
3. I'm not asking something that has been answered several times
already (didn't really know what words to google on).
4. The raining here stops soon...