MSCOMM32

[Michael]

I have seen a lot of messages over the last year or two about replacement of
the MSCOMM32.
The ones I have read all have different ideas.
Is there now a consensus, or not?

Thanks,
Michael

[thomas wenning]

HI Michael,

use the Resource Kit http://msdn.microsoft.com/vbasic/vbrkit/
inside is a control from Sax

a.. Sax Software Corp
Sax.net Communications makes it easy to add scalable serial communications
to all your .NET applications.

Regards

Thomas Wenning

"Michael" <IN******@aol.com> schrieb im Newsbeitrag
news:uW*******************@twister.tampabay.rr.com ...

I have seen a lot of messages over the last year or two about replacement of the MSCOMM32.
The ones I have read all have different ideas.
Is there now a consensus, or not?

Thanks,
Michael

[Herfried K. Wagner [MVP]]

* "thomas wenning" <th************@gmx.de> scripsit:

use the Resource Kit http://msdn.microsoft.com/vbasic/vbrkit/
inside is a control from Sax

a.. Sax Software Corp
Sax.net Communications makes it easy to add scalable serial communications
to all your .NET applications.

AFAIK this is a "Community Edition". Does it have any "limitations"?

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

[Herfried K. Wagner [MVP]]

* "Michael" <IN******@aol.com> scripsit:

I have seen a lot of messages over the last year or two about replacement of
the MSCOMM32.
The ones I have read all have different ideas.
Is there now a consensus, or not?

No.

;-)

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

[thomas wenning]

HI Herfried
Using Sax.net Communications Community Edition you can control both RS232
and RS485 serial ports, as long are connected to COM1 to COM8. To work with
an unlimited number of ports, you need Sax.net Communications Professional
Edition, which also supports multi-port cards such as Digiboards.

It is possible to develope Script-driven programs (make a connection,
perform a number of steps, and disconnect)
or Event-driven programs (the device wake you up when it has data to
process) with this control.

I use it without any problem.

Regards

Thomas

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> schrieb im Newsbeitrag
news:br*************@ID-208219.news.uni-berlin.de...

* "thomas wenning" <th************@gmx.de> scripsit:

use the Resource Kit http://msdn.microsoft.com/vbasic/vbrkit/
inside is a control from Sax

a.. Sax Software Corp
Sax.net Communications makes it easy to add scalable serial communications to all your .NET applications.

AFAIK this is a "Community Edition". Does it have any "limitations"?

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

[Herfried K. Wagner [MVP]]

* "thomas wenning" <th************@gmx.de> scripsit:

Using Sax.net Communications Community Edition you can control both RS232
and RS485 serial ports, as long are connected to COM1 to COM8. To work with
an unlimited number of ports, you need Sax.net Communications Professional
Edition, which also supports multi-port cards such as Digiboards.

OK, thanks. The control will fit the requirements of most people...

;-)

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

[Michael]

I am downloading it right now....
Thanks,
Michael

"thomas wenning" <th************@gmx.de> wrote in message
news:Oz**************@TK2MSFTNGP12.phx.gbl...

HI Michael,

use the Resource Kit http://msdn.microsoft.com/vbasic/vbrkit/
inside is a control from Sax

a.. Sax Software Corp
Sax.net Communications makes it easy to add scalable serial communications
to all your .NET applications.

Regards

Thomas Wenning

"Michael" <IN******@aol.com> schrieb im Newsbeitrag
news:uW*******************@twister.tampabay.rr.com ...

I have seen a lot of messages over the last year or two about

replacement of

the MSCOMM32.
The ones I have read all have different ideas.
Is there now a consensus, or not?

Thanks,
Michael

[Dick Grier]

Hi,

There is no consensus, I'm sure. You should use whatever makes your job
easiest and most productive. I use at least five different serial "tools"
for .NET, depending on what I'm doing (and, often, what are my client's
needs).

--
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.

[Michael]

I downloaded it to several of my machines.
What do I do next.
the e-link that it installs in Programs.... opens the .Net IDE to edit the
file.

Thanks,
Michael

(My goal is to have a .Net clue by 02/01/04)
"thomas wenning" <th************@gmx.de> wrote in message
news:Oz**************@TK2MSFTNGP12.phx.gbl...

HI Michael,

use the Resource Kit http://msdn.microsoft.com/vbasic/vbrkit/
inside is a control from Sax

a.. Sax Software Corp
Sax.net Communications makes it easy to add scalable serial communications
to all your .NET applications.

Regards

Thomas Wenning

"Michael" <IN******@aol.com> schrieb im Newsbeitrag
news:uW*******************@twister.tampabay.rr.com ...

I have seen a lot of messages over the last year or two about

replacement of

the MSCOMM32.
The ones I have read all have different ideas.
Is there now a consensus, or not?

Thanks,
Michael

[Michael]

Can you go into more detail?
All I do is 'talk' to devices. Simple stuff. Well, it was simple before
..Net.

Thanks,
Michael

"Dick Grier" <di**************@msn.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

Hi,

There is no consensus, I'm sure. You should use whatever makes your job
easiest and most productive. I use at least five different serial "tools"
for .NET, depending on what I'm doing (and, often, what are my client's
needs).

--
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.

[Dick Grier]

Hi,

If you want to use code almost identical to that used for MSComm, then I
suggest that you download NETComm.ocx from my homepage. It is free, and the
syntax is very close. It wraps all MSComm functions so that it may be used
in .NET apps with no licensing restrictions -- and is free.

There are several class modules available that use P/Invoke to call the
Windows communications API. I have one in my book (see below), and you can
download others
(http://msdn.microsoft.com/vbasic/dow...es/default.asp for
example).

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.