I apologize for posting in 'EE', but I'm only doing it since I *think* more
people will see this here (and hopefully be helped) as opposed to posted it
in OT. I'll try to be brief and keep this message small.

For those that may not know of it, I just tried out the *FREE* Sax.net
Communications Community Edition serial port ActiveX control. I was getting
a little frustrated (see postscipt below) migrating a VB6 project using the
MSCOMM control to Microsoft Visual Basic .NET 2003.

So until Microsoft Visual Studio .NET 2005 arrives with its *intrinsic*
SerialPort class (System.IO.Ports.SerialPort), you have the option of using
the Sax.net Communications Community Edition ActiveX control for controlling
serial ports. It is free and therefore it is not as feature-rich as Sax's
ActiveX serial port communication controls they are charging real money for,
but hey, it's a lot of fun to use this one. You can get up and running
rather quickly with it. In some respects, it might be easier for people to
use the Community Edition serial port communication control than the MSCOMM
control which Sax wrote for Microsoft many years ago.

You can get the free Sax Community Edition serial port communications
ActiveX control with the Visual Basic .NET Resource Kit:

http://msdn.microsoft.com/vbasic/vbrkit/default.aspx

Hope this helps anyone trying to get your serial port projects working under
Microsoft Visual Studio .NET. I think a lot of PICListers picked up a free
version of VB.NET for watching those Microsoft movies, so give it a try if
you have not already. My hopes is that the control will work with that free
version of VB.NET too.

Best regards, good luck, and have fun,

Ken Pergola


P.S. This is the line of code from VB6 that I just can't seem to coerce into
VB.NET thus far:

bytUART_Byte = Asc((StrConv(MSComm1.Input, vbUnicode)))

The 'vbUnicode' is not accepted.



_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist