>Does anyone know if there are serious issues regarding using
>C# .NET System.IO.Ports.SerialPort object?

If it is used correctly, the .NET SerialPort class works fine. One thing wh=
ich=20
is importatn to understand is that events raised by the serial port object =
is=20
not running in the GUI thread. This means that objects used by the GUI thre=
ad=20
may not be touched from the SerialPort event code without using some kind o=
f=20
synchronization method. These kind of object includes GUI controls so if yo=
u=20
need to update any visible control (or invisible, for that matter) as a res=
ult=20
from events rised by the serial port you need to do that in the GUI thread =
by=20
using Invoke() or BeginInvoke() for example.

Most of the time you get away with updating GUI objects from the SerialPort=
=20
threads which is why it can be hard to debug faults caused by this.

/Ruben


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Ruben J=F6nsson
AB Liros Electronic
Box 9124, 200 39 Malm=F6, Sweden
TEL INT +46 40142078
FAX INT +46 40947388
ruben@pp.sbbs.se
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.