Microsoft and Widcomm have completely different SDKs. If you are creating
a simple enough application you might be able to get away with just using
virtual COM ports (Serial Port Profile). Virtual COM ports use standard
Windows CE APIs which wrap Microsoft and Widcomm BT stacks.
I hope this helps.
Greg Scott
Software Design Engineer, Windows CE
Microsoft Corporation
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________________________________
--------------------
Thread-Topic: MS / widcomm bluetooth programming
thread-index: AcVFtm3PpBU9KVMQTGOvX2dvIU97pg==
X-WBNR-Posting-Host: 217.15.96.17
From: "=?Utf-8?B?S2V2aW4gQnVzdXR0aWw=?="
< XXXX@XXXXX.COM >
Subject: MS / widcomm bluetooth programming
Date: Wed, 20 Apr 2005 07:37:07 -0700
Lines: 9
Message-ID: < XXXX@XXXXX.COM >
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.pocketpc.developer.networking
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.pocketpc.developer.networking:4224
X-Tomcat-NG: microsoft.public.pocketpc.developer.networking
Hi I'm rather new to Bluetooth programming.
Is there a way to make one program using VC++ CE 4.2 that works both with
Widcomm and Microsoft Bluetooth stack? Does programming with OBEX or Serial
Connectivity works?
I couldn't find a simple up-to-date answer of this issue on the internet.
Please help
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Microsoft and Widcomm have completely different SDKs. If you are creating a simple enough application you might be able to get away with just using virtual COM ports (Serial Port Profile). Virtual COM ports use standard Windows CE APIs which wrap Microsoft and Widcomm BT stacks.
\par
\par I hope this helps.
\par
\par Greg Scott
\par Software Design Engineer, Windows CE
\par Microsoft Corporation
\par _____________________________________________________________
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par _____________________________________________________________
\par
\par \pard\li720 --------------------
\par Thread-Topic: MS / widcomm bluetooth programming
\par thread-index: AcVFtm3PpBU9KVMQTGOvX2dvIU97pg==
\par X-WBNR-Posting-Host: 217.15.96.17
\par From: "=?Utf-8?B?S2V2aW4gQnVzdXR0aWw=?=" < XXXX@XXXXX.COM >
\par Subject: MS / widcomm bluetooth programming
\par Date: Wed, 20 Apr 2005 07:37:07 -0700
\par Lines: 9
\par Message-ID: < XXXX@XXXXX.COM >
\par MIME-Version: 1.0
\par Content-Type: text/plain;
\par \tab charset="Utf-8"
\par Content-Transfer-Encoding: 7bit
\par X-Newsreader: Microsoft CDO for Windows 2000
\par Content-Class: urn:content-classes:message
\par Importance: normal
\par Priority: normal
\par X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
\par Newsgroups: microsoft.public.pocketpc.developer.networking
\par NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
\