Re: Back to VB6 and .NET
- From: Tom Shelton <tom_shelton@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 06 Feb 2008 14:14:27 -0800
On 2008-02-06, Ken Halter <Ken_Halter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
"Cor Ligthert[MVP]" <notmyfirstname@xxxxxxxxx> wrote in message
news:C0B52161-16F0-42B8-80A6-C19C71D45DC8@xxxxxxxxxxxxxxxx
Can you tell me what was already in C# and not in VB for Net (beside the
dead horse unsafe code):
<g>... that "dead horse" is being shoved down our throats, in the form of
"the wonderful world of interop"
From version 2005 VB has Edit and continue ( a feature I don't like, it
cost me to much time)
Because it was an afterthought, hacked into place in a desparate attempt to
grab more VB Classic devs.
Try it in VB5/6. There is *no* noticable time delays between keystrokes.
It sucked in VB5/6 as well. It was feature that encouraged crappy
coding, IMHO. Didn't use it then, don;t use it now. By the way, the
couple of times I ahve tried it in .NET, I have never noticed any
keystroke lag?
Of course, you think of this as a language feature - since VB.CLASSIC
was so tied to the dev environment. This isn't true with VB.NET you can
code in notepad and use bat files to do your builds if you want.
VB for net has direct from version 2002 background compiling, a feature
that has never been in C# and therefore C# needs endless builds to correct
typing errors.
Which must be another "bolt on - after the fact" because VB Classic's had
that for years.
And? It's not a "bolt on" - the VB.NET IDE has always had it.
VB for net has direct from version 2002 a kind of auto editing, something
that has never been in C# (which is much improved in version 2008 by the
way)
Which must be another "bolt on - after the fact" because VB Classic's had
that for years.
LOL... Believe me the VB.NET version is MUCH better. All you get vrom
VB.CLASSIC is the annoying modal message box... In VB.NET it tells you
what's wrong, gives you a list of suggested fixes - and then let you
select one, which it will automatically implement for you.
VB has in version 2008 direct XML creation something that is not in C#.
Now there's one VB Classic doesn't have.... XML. The "kitchen sink" file
spec that was originally designed to be nothing more than a "treeview"
version of CSV files. If you check the contents of an XML file in notepad,
you'll see the same "bloatware" authors were involved in its creation.
I sense you really don't like XML... Which is fine, but for a lot of us,
XML is a reality we have to deal with - and so, I don't see the harm in
MS adding a feature that makes the our lives easier. That rant really
sounds more like sour grapes then anything rational. Really, if you
don't need the feature how is it hurting you if it's there?
--
Tom Shelton
.
- Follow-Ups:
- Re: Back to VB6 and .NET
- From: Ken Halter
- Re: Back to VB6 and .NET
- From: Ken Halter
- Re: Back to VB6 and .NET
- References:
- Re: Back to VB6 and .NET
- From: Bob Butler
- Re: Back to VB6 and .NET
- From: Robert Conley
- Re: Back to VB6 and .NET
- From: Tom Shelton
- Re: Back to VB6 and .NET
- From: Robert Conley
- Re: Back to VB6 and .NET
- From: Tom Shelton
- Re: Back to VB6 and .NET
- From: Robert Conley
- Re: Back to VB6 and .NET
- From: Tom Shelton
- Re: Back to VB6 and .NET
- From: Cor Ligthert[MVP]
- Re: Back to VB6 and .NET
- From: Ken Halter
- Re: Back to VB6 and .NET
- Prev by Date: Re: What Did I do?
- Next by Date: Re: newbie: how to avoid having return or space bar from activating bu
- Previous by thread: Re: Back to VB6 and .NET
- Next by thread: Re: Back to VB6 and .NET
- Index(es):
Relevant Pages
|