Hi Everyone,
Is it proper to use the previous MSComm Control in VB.net application.

Thanking you,

Nommy

Hi Nommy

I recommend a look at the control at http://www.codeworks.it/net/index.htm.

HTH

Charles


"Nommy" <(E-Mail Removed)> wrote in message
news:A43EC400-3DEB-4733-A952-(E-Mail Removed)...
>
> Hi Everyone,
> Is it proper to use the previous MSComm Control in VB.net application.
>
> Thanking you,
>
> Nommy

* "=?Utf-8?B?Tm9tbXk=?=" <(E-Mail Removed)> scripsit:
> Is it proper to use the previous MSComm Control in VB.net application.

I don't know...

Thomas Scheidegger's Serial Port FAQ (in German)
<http://groups.google.com/groups?selm=O2UyhTLvDHA.1680%40TK2MSFTNGP12.phx.gbl>

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

Hi,

Yes, you may use it. However, technically, it is licensed only for use if
you also have Visual Studio 6.0 installed. To avoid the license issue, you
can download NETComm.ocx from my homepage, which wraps MSComm32.ocx, and is
free, with no license restrictions. You also can refer to the other posts
for alternate solutions.

BTW, I have native .NET code examples (using P/Invoke) in my book, along
with solutions that use add-ons that range from MSComm32 to NETComm and
XMCommCRC to commercial communications add ons. See below. These examples
and text may help you with other questions that come up. Feel free to ask
here, too.

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 3rd
Edition ISBN 1-890422-27-4 (391 pages) published February 2002.