Recently, I converted a VB6 module that communicates with a hardware device through the serial port. Initially, I was accessing the comm module as a VB6 DLL, which was working all right. The VB.NET version of this module is working to some extent, but it is very unstable. I.e. a lot of the time (say 25% of the time) it is returning quite unexpected results. The rest of the time it is working fine.
The comm module uses the old Microsoft Comm Control 6.0 (MSComm32.ocx). Has anyone experienced similar problems with this control in VB.NET? Is there something I can do to make it stable?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The comm module is 100% stable now, but I am having the following problem when deploying and distributing the application: It won't run on client machines because of the following error: "Class not licensed for use" (MSComm32.ocx).
In an earlier version of the application I was using this control through a VB6 module, and so vb6cli.exe sorted out the licensing issue. Does an equivalent exist for VB.NET?
If anyone can help I will raise the points to 600.
Chrrris the MSComm32.ocx is unstable under the .NET framework. Follow this link http://msdn.microsoft.com/
Business Accounts
Answer for Membership
by: iboutchkinePosted on 2003-02-16 at 18:13:01ID: 7963100
Check this site. Here is the explanation how to deal with serial port in VB.NET
http://66.216.11.86/cc/VBN