I wrote an application in eVB that beamed Tasks between PPC 2000 devices and
used the POOM store to interact with the Tasks list. Worked quite well - I
am now trying to migrate this to .Net CF and trying to resolve some problems
encountered when using this program on PPC2002 devices.
These newer devices use the Palm compliant IrOBEX methodology and I will
want to use that eventually. However, in the meantime, I find that when I
use the same methods that I used in eVB, on the newer PPC2002 devices, the
Task is beamed twice - once using the older legacy IR method, and once with
the newer automatic-reception of the beamed Task.
Since the older IR beaming method works better for now with my code for the
POOM store, I would like to be able to temporarily disable Beam reception on
the device so that it does not also grab the Task using the newer transfer
method.
In looking through the .Net documentation, I had thought that I should be
able to do this with the following code:
'Add a Reference to System.Net.IrDA
Dim ird As New System.Net.Sockets.IrDAListener("x")
ird.Stop()
The string "x" was chosen at random - I grabbed this idea from the AgentBeam
example on GotDotNet. I don't know if the string matters or not.
I assigned this ird.Stop() method to a button on a test Form in VB.Net -
while it compiles and runs without complaint, the Stop() method does not
appear to stop the IrDA listener from listening.
So what am I missing? Does the string parameter matter? How do I access the
main default IrDAListener?
dt
|
Similar Threads
