Re: Web enablement options (previously private)

["Adam Lang" <aalang@xxxxxxxxxxxxxxxxxxxx>]

The big thing that a lot of people have not noticed is that MS is going to
kill COM.  They are supporting it, but they are going to phase it out as
they force more .NET down developer throats.

And remember, they killed the variable data type.  Granted you shouldn't use
it anyway, but a lot of people did.

Also, default methods were gotten rid of.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Joe Pluta" <joepluta@PlutaBrothers.com>
To: <midrange-l@midrange.com>
Sent: Saturday, December 29, 2001 2:29 AM
Subject: RE: Web enablement options (previously private)


> > From: Brad Jensen
> >
> > Microsoft is discovering some of its own inertia. The three
> > million VB programmers are less than ecstatic about being shoved
> > into an 'upgrade'to VB.NET that is really a different, C-based
> > language, tons of stuff breaks.
>
> Wow.  I just looked at the VB.NET specs, and it really is fundamentally
> different from VB.  In fact, I suspect that most code written for VB will
> not work with VB.NET.  Just the fact that parentheses are now required for
> function calls is enough to cause that.  Changing the behavior of the
> assignment operator is also pretty huge.  Automatic conversion between
> string and numeric is gone.  Static functions are gone.  UDTs are gone.
> Man.
>
> I pity the folks who are forced to move, and given deadlines to do it.
>
> On the other hand, I think there's a heck of an opportunity for someone if
> they wanted to write a VB to VB.NET converter.
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>