D
David Hearn
I have an CF application which is based on logic which has been tried
and tested on the full .NET Framework. Most of the logic is the same,
with the only significant difference being some hardware which sends and
receives some data - however most of this code has been used
successfully before with this device.
Consequently there's very little code which is actually new. However,
I'm seeing some very strange results.
When I run the application it keeps hitting unusual conditions within my
code - specifically, things like being unable to find certain data
within the response (which never happened ever on the desktop version) -
not not the same thing each time - completely different errors each time
through. When I try it a 2nd time (to examine the response to check why
it failed before, the response is fine and the check works fine, but it
falls over earlier or later in the code.
The issue is that the responses should be constant, so it appears that
there's something very odd happening.
I'm going to hard code the input and responses so that the device can be
excluded, and possibly also then run it in the emulator. This would
then help me work out where the issue is.
Any suggestions though what sort of thing might cause these random,
non-predictable problems?
Thanks
David
and tested on the full .NET Framework. Most of the logic is the same,
with the only significant difference being some hardware which sends and
receives some data - however most of this code has been used
successfully before with this device.
Consequently there's very little code which is actually new. However,
I'm seeing some very strange results.
When I run the application it keeps hitting unusual conditions within my
code - specifically, things like being unable to find certain data
within the response (which never happened ever on the desktop version) -
not not the same thing each time - completely different errors each time
through. When I try it a 2nd time (to examine the response to check why
it failed before, the response is fine and the check works fine, but it
falls over earlier or later in the code.
The issue is that the responses should be constant, so it appears that
there's something very odd happening.
I'm going to hard code the input and responses so that the device can be
excluded, and possibly also then run it in the emulator. This would
then help me work out where the issue is.
Any suggestions though what sort of thing might cause these random,
non-predictable problems?
Thanks
David