Re: COMM Control

From: Wpayten (Wpayten_at_discussions.microsoft.com)
Date: 01/10/05 

Date: Mon, 10 Jan 2005 13:37:01 -0800

Hi

On further investigation the comm control does work, when the port is open
it put a character in the receive port, (doesnt happen in 2000-2002). Thus
as i read this byte my data stream is completely out of step. Clearing the
port works. However I think i will stay with the marshallsoft dll as it
exposes many more functions then the comm control that i find very useful.

As I am logged in, getting on my soap box, I am not happy that evb will
not load under the next version of PPC when it comes out. I am okay for MS
to stop support, but there most be an awful lot of legacy code out there. MS
is actively forcing one to recode in the compact framework. I better policy
would have been to stop support but allow legacy code to be used at least
through the next couple of versions. This would give code developers
particularly myself where the code is quite large more time to learn the new
framework and vb.net syntax or change to C++ which we are also doing and then
go through the recoding process. As mentioned in my last message we have
started this process but it will take time. As the software is used on Snow
slopes to predicted slope stabilty I have to be very sure that each version
of the software is behaving.

Warwick

"*** Grier" wrote:

> Hi,
>
> I haven't used it under Windows Mobile 2003, because eVB isn't supported on
> that platform, though there are ways to get it to work. Porting to the
> Compact Framework seems to me to be the "way to go." Certainly, performance
> is LOTS better.
>
> ***
>
> --
> Richard Grier (Microsoft Visual Basic MVP)
>
> See www.hardandsoftware.net for contact information.
>
> Author of Visual Basic Programmer's Guide to Serial Communications, 4th
> Edition ISBN 1-890422-28-2 (391 pages) published July 2004. See
> www.mabry.com/vbpgser4 to order.
>
>
>

Quantcast