I for years I have used MSCOMM32.OCX to handle serial port comm in vb6. Is this the "proper" way to handle the serial port in .net or is there another better way?
thanks
kevin
Last edited by kebo; Jan 31st, 2005 at 11:35 AM.
Process control doesn't give you good quality, it gives you consistent quality.
Good quality comes from consistently doing the right things.
Vague general questions have vague general answers.
A $100 donation is required for me to help you if you PM me asking for help. Instructions for donating to one of our local charities will be provided.
______________________________
Last edited by kebo : Now. Reason: superfluous typo's
Hi
Each form as a thread responsible for updating your form GUI, using System.Threading.Thread.Sleep(200) will make that thread sleep for 200ms and you will notice that the GUI stops responding during that time.
Regards
Jorge
"The dark side clouds everything. Impossible to see the future is."
that takes care of one question, but I think the rest of them are irrelevant if the last can be answered with a no----Is it so bad using VB6 ocx's such as MSCOMM32.ocx in .net? What are the implications of using VB6 control in .net?
thanks
kevin
Process control doesn't give you good quality, it gives you consistent quality.
Good quality comes from consistently doing the right things.
Vague general questions have vague general answers.
A $100 donation is required for me to help you if you PM me asking for help. Instructions for donating to one of our local charities will be provided.
______________________________
Last edited by kebo : Now. Reason: superfluous typo's
Hi
When you add a vb6 control to your .net project it will create a wrapper dll starting with interop.yourcontrolname.dll on your \bin directory, so there disk space wasted and performance hit, Interop is very slow compared to .net .
Regards
Jorge
"The dark side clouds everything. Impossible to see the future is."
Ok that's much better . But I just want to add my 2cents . Using interop VB6 with .NET isn't like so bad but it's always not recommended .Simply because the overhead it causes , delay of execution , not 100% handled by the CLR environment and most of all , the data types are quite different .For example , Long in VB6 is Integer in .NET , Any or Variant is Object in .NET .
There was a thread I found that I think was started by Wossname about serial ports in .NET. A links were provided to at least three places that had free downloads of .NET serial port wrapper classes. I studied two of them, and ended up using one of them in my own project (with modifications)
Unfortunately, I haven't been able to find those links again. However, I do have the downloads lying around here somewhere if you'd like them.
There was a thread I found that I think was started by Wossname about serial ports in .NET. A links were provided to at least three places that had free downloads of .NET serial port wrapper classes. I studied two of them, and ended up using one of them in my own project (with modifications)
Unfortunately, I haven't been able to find those links again. However, I do have the downloads lying around here somewhere if you'd like them.
Yes please send them
thanks
kevin
Process control doesn't give you good quality, it gives you consistent quality.
Good quality comes from consistently doing the right things.
Vague general questions have vague general answers.
A $100 donation is required for me to help you if you PM me asking for help. Instructions for donating to one of our local charities will be provided.
______________________________
Last edited by kebo : Now. Reason: superfluous typo's
Here are 3 files (I hope, I've never actually attached a file to one of these posts before). The two zip files are the free downloads from places probably included in text files in the zips. They are small projects that test a core RS232 wrapper class (a different class in each project, not the same class).
I forget which one I included in the RS232.vb file, and I forget whether or not I made any modifications to the file, but the one I chose was simple to use, and could readily be plugged into my application.