VS2003 Application stops in debugger in same place!

  • Thread starter Thread starter Andy
  • Start date Start date
A

Andy

Hi

I am developing using VS2003, PPC2003 SE (in an i-mate PDA2K) using
VB.net. I also use the SerialNet from Franson, this feeds into TTNCF
for driving GPS data to TomTom Navigator. The data arrives via
Bluetooth.

The problem I have is that everything runs OK for a short random
amount of time and then stops. I have a clean install on my laptop of
VS2003 and this stops as well in exactly the same place in the
debugger. If I remove the TTNCF refs and DLL it still stops, but in a
different place.

Sometimes when VS is loading the PDA under debug it has an error when
launching the application, this means that you have to reset the PDA
as if you try to load it again you get an exception as the application
is running in a mysterious way which cannot be seen.

Does anybody have any ideas about this, as I am tearing what is left
of my hair out!

Thanks

Andy.
 
Still having problems!

At :-
Try
TextBox3.Text = "PingOn"
Catch ex As Exception
If DebugMe = True Then
MessageBox.Show(ex.Message & "
TmrSerial_Tick")
End If
End Try

The program freezes execution at the TextBox3.Text = "PingOn" line and
I have no idea of why.

It seems that the more times I write to a text box, the sooner
everything locks up.

If I set the Program to Release and deploy it the same thing happens,
probably at the same place.

Andy.
 
I don't have any seperate threads running, I only have the running
form going and am setting/clearing forma items from it.

Andy.
 
So what you are saying is that if I want to update some UI, then I
have to put it into seperate subroutines and call them?

Like :-

Me.Invoke(New EventHandler(AddressOf HandleSerial)) calls

Sub HandleSerial(ByVal o As Object, ByVal e As EventArgs)
If objPort.Enabled = True Then
TextBox4.Text = "Conn"
Else
TextBox4.Text = "NotConn"
End If
end sub

And that will solve all my problems?

Andy.
 
No. Event handlers are in the thread context of the caller. The TomTom
library likely has a worker thread listening to the port, so in the handler
you must use Control.Invoke to affect the UI.

-Chris
 
Back
Top