U
Urs Vogel
Hi
For supporting the serial port for remote data collection on manufacturing
devices, I added the mscomm32.ocx Active-X component to my .Net 1.1
application, which works fine on my machine (I have VS 2003 FW 1.1 and VS
6.0 installed). When creating the setup, it nicely includes the mscomm32.ocx
and the interop module in the setup project. When installing it on a client
machine, everything appears to be ok, and even talking to the mscomm32.ocx
does not throw any exceptions. The problem is that this component does not
talk to the serial port ... so it's pretty useless.
I suppose there's something missing, any hints of what that could be, or how
I could track it down and solve this?
Thanks, Urs.
For supporting the serial port for remote data collection on manufacturing
devices, I added the mscomm32.ocx Active-X component to my .Net 1.1
application, which works fine on my machine (I have VS 2003 FW 1.1 and VS
6.0 installed). When creating the setup, it nicely includes the mscomm32.ocx
and the interop module in the setup project. When installing it on a client
machine, everything appears to be ok, and even talking to the mscomm32.ocx
does not throw any exceptions. The problem is that this component does not
talk to the serial port ... so it's pretty useless.
I suppose there's something missing, any hints of what that could be, or how
I could track it down and solve this?
Thanks, Urs.