Thanks, but first off, it is RS232 communication via serial port, so the system.net namespace is not a help. (MSComm could only be used for such for future refrence). Secondly, I am using a component that is used in software that is still sold by the company (I know it's not the best, but I just take the orders). Also, I am declaring it as a class, Using a Com component in design time creates a great many issues.
I am using the MSComm library due to the fact that the app is used to control materials testing machines, so speed is essential, which is why the IO.Ports namespace is aboslutly useless. It takes 1.5 seconds to send and recieve a replay from the machine due to the layers in .Net. due to this much data is lost. However, due to the demands of the customers, we have to use .net.
So, This error did not occur at design time, it occured at runtime on a diffrent machine than it was devloped on. I included the DLL that was copied to the apps directory so everything is refrenced properly. I Emphisis again that I cannot use the .Net component due to communication loss through framework lage time. Also, the serial port object appers to "Miss" Data, which can cause damage to the machine.
The application runs perfectly on the machine it was developed on, and not on the machine it needs to, even with the Library files for VB 6 installed.My question is this:
- Why does the error occur?
- How to fix it without the use of alternative librarys? (Unless operating at a Low-level)
- Really, What the heck is this error? I've used Com components before (Including MSComm and WinSock), and have never had this issue.
index > Windows Forms General > COM Component Error 80040112