Re: Why not serial port component in .NET?
- From: "Lorenz Buchberger" <l_buchberger@xxxxxxxxxxx>
- Date: Mon, 13 Jun 2005 11:55:19 +0200
Hi,
A serial communication component will be included in VS 2005.
Regards,
Lorenz
"Lau Lei Cheong" <leu_lc@xxxxxxxxxxxx> schrieb im Newsbeitrag
news:uIclNl$bFHA.3696@xxxxxxxxxxxxxxxxxxxxxxx
> Hello,
>
> Just a bit curious why CLR team decided not to include serial
> communication compatibilities in the .NET Framework. Although we can use
> CreateFile() API to access the COM ports to read/write synchronously, it's
> not easy(for beginners) to write something that can listen the COM ports
> and response to events. I know MSCOMM32.OCX is avaliable but 1) it's not a
> .NET thing 2) it's not easy to program it in a machine that didn't have
> VS6 installed.
>
> It should be more handy to have something like
> System.Net.Sockets.TcpClient as a simple wrapper that allow us to do
> simple tasks. And enable us to have more consistant coding so it'll be
> easier for us to port the code to use TCP/UDP later. How do you think?
>
> And anyone know will that be anything of the sort in .NET v2.0?
>
> All responses are welcomed.
>
> Regards,
> Lau Lei Cheong
>
>
.
- Follow-Ups:
- Re: Why not serial port component in .NET?
- From: Lau Lei Cheong
- Re: Why not serial port component in .NET?
- References:
- Why not serial port component in .NET?
- From: Lau Lei Cheong
- Why not serial port component in .NET?
- Prev by Date: Re: writing a .BAT to use xcopy
- Next by Date: RE: A complete response was not received from the remote server
- Previous by thread: Why not serial port component in .NET?
- Next by thread: Re: Why not serial port component in .NET?
- Index(es):
Relevant Pages
|