Regarding converting the following from VB6 to VB.NET:

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


James Caska wrote:

> The question is.. Is this the only problem you are experiencing
> with MSComm?



Hi James,

To answer your question, so far, yes. But that does not mean that I won't
run into other problems with porting MSCOMM porting to VB.NET. I actually am
looking forward to Visual Studio .NET 2005 because of the built-in
SerialPort class. I don't know too much about the details at this point, but
I'm hoping it will work fine.

If I'm not mistaken, using the MSCOMM control in VB.NET violates the
philosophy of .NET "managed code". It also appears to create a potential
distribution problem since you should have a legal license for it. For me, I
have a legal version of VB6. But the managed/unmanaged code issue is more
important to me. I'm not sure if using the Sax control qualifies as
unmanaged code too? I could be totally wrong about these two points, so
hopefully someone who is well-versed with the .NET framework can shed some
more light on the situation.


James also asked:

> and how do your recommended package resolve the problem because
> as far as I can see the problem is actually with the StrConv routine being
> incompatible with vbUnicode Strings not the MSComm1.Input.


Well, I just don't know enough about the VB.NET and the .NET framework to
solve this problem at this point. I let VB.NET "upgrade" the VB6 application
with the conversion wizard. I've spent hours reading on-line documentation
and fiddling with things by trial and error to try to get things to work. I
just decided to switch gears and try out that free Sax serial communications
control because it came free with the VB.NET resource kit.

That Sax serial communications control is pretty slick for what I've used it
for so far. This is what prompted me to post the quick results I had with
that Sax serial communications control. I simply got it working in VB.NET,
and was up and running rather quickly . I can't say that with the MSCOMM
control, but I would imagine others have used the MSCOMM control in VB.NET.
I'm sure it's pilot error on my part: miles of .NET before I sleep, and
miles of .NET before I sleep. I have a long journey with .NET, but I'm
looking forward to it.

Best regards,

Ken Pergola






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