By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,446 Members | 3,120 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,446 IT Pros & Developers. It's quick & easy.

Deployment of my .Net app with MSCOMM32.oxc Active-X component fails

P: n/a
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.
Nov 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
I've used the RS232.vb module from this article in my VB .net applications
and have been able to use the COM ports without using the OCX.

http://www.microsoft.com/downloads/d...DisplayLang=en
"Urs Vogel" <uv****@msn.com> wrote in message
news:un*************@TK2MSFTNGP11.phx.gbl...
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.

Nov 21 '05 #2

P: n/a
That's cool, just changed it and got rid of the ocx. Thanks.

Urs
"Terry Olsen" <to******@hotmail.com> schrieb im Newsbeitrag
news:%2***************@TK2MSFTNGP12.phx.gbl...
I've used the RS232.vb module from this article in my VB .net applications
and have been able to use the COM ports without using the OCX.

http://www.microsoft.com/downloads/d...DisplayLang=en
"Urs Vogel" <uv****@msn.com> wrote in message
news:un*************@TK2MSFTNGP11.phx.gbl...
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.


Nov 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.