VB .NET vs C#

[Eric Wise]

Does anyone work for companies that actually implement both VB and C#? I
know that you can do this in theory, I just find it hard to imagine that a
company would split its programming technologies like that.

Of course now with the CLR there doesn't seem to be any performance benefit
to using C# over VB, and VB I think is an "easier" language to pick up. I
actually wonder if the salaries between vb.net and c# will balance out a
little now since the language doesn't mean as much anymore.

I personally am a VB developer moved into asp .net / vb .net. I've been
considering going ahead and learning C# as well. I have only academic
experience with C++, but it is enough that I can read c# examples and
convert them to vb so I don't think this is a big deal for me to pick up the
new language. Just more wondering if I should even bother.

[Steve C. Orr, MCSD]

If you're on the job hunt, you'll increase your chances of landing a job by
being able to say that you know both languages instead of just one.
Then again there's something to be said for being a specialist. There is
only so much time to learn. You may not want to become a jack of all trades
but master of none.

--
I hope this helps,
Steve C. Orr, MCSD
[url]http://Steve.Orr.net[/url]


"Eric Wise" <NOewise@pica.army.milSPAM> wrote in message
news:exwW275VDHA.2252@TK2MSFTNGP10.phx.gbl...

> Does anyone work for companies that actually implement both VB and C#? I
> know that you can do this in theory, I just find it hard to imagine that a
> company would split its programming technologies like that.
>
> Of course now with the CLR there doesn't seem to be any performance

benefit

> to using C# over VB, and VB I think is an "easier" language to pick up. I
> actually wonder if the salaries between vb.net and c# will balance out a
> little now since the language doesn't mean as much anymore.
>
> I personally am a VB developer moved into asp .net / vb .net. I've been
> considering going ahead and learning C# as well. I have only academic
> experience with C++, but it is enough that I can read c# examples and
> convert them to vb so I don't think this is a big deal for me to pick up

the

> new language. Just more wondering if I should even bother.
>
>
>
>

[Bill Priess]

I worked recently at a company that dropped VB.NET in favor of C#. We
dropped VB.NET becuase of the amount of code that VB.NET required to do
some amazingly simple things (which, btw, is something that even MSFT has
acknowledged and on the roadmap, have said they will *fix*). Knowing both
has helped me, but given the choice, I would have never picked up VB at
all...

Just in general, I have found that C# is easier to follow and much more
logical and concise than VB is. Not to mention... XML Documnetation...
Plus, as many of us know... never rely on MSFT to actually stick to a
roadmap for anything. Just because one document says that this *feature*
will be in the next version, don't think that there won't be another one
that denies it. ;)

(Just think back to the release of WinME, you know, the revolutionary OS
that was supposed to be entirely 32-bit based and stable? ;) )

Bill P.

On Thu, 31 Jul 2003 16:05:24 -0400, Eric Wise <NOewise@pica.army.milSPAM>
wrote:

> Does anyone work for companies that actually implement both VB and C#? I
> know that you can do this in theory, I just find it hard to imagine that
> a
> company would split its programming technologies like that.
>
> Of course now with the CLR there doesn't seem to be any performance
> benefit
> to using C# over VB, and VB I think is an "easier" language to pick up.
> I
> actually wonder if the salaries between vb.net and c# will balance out a
> little now since the language doesn't mean as much anymore.
>
> I personally am a VB developer moved into asp .net / vb .net. I've been
> considering going ahead and learning C# as well. I have only academic
> experience with C++, but it is enough that I can read c# examples and
> convert them to vb so I don't think this is a big deal for me to pick up
> the
> new language. Just more wondering if I should even bother.
>
>
>
>
>

--
Using M2, Opera's revolutionary e-mail client: [url]http://www.opera.com/m2/[/url]

[Steve C. Orr, MCSD]

VB.NET is a little more verbose if that's what you mean. But that also
makes the code more readable and self documenting. (Although I'm still glad
VB.NET will be getting the XML documentation feature in the next version.)
Just because the code is a little more verbose doesn't necessarily mean you
have to do more typing. The VS.NET editor is more friendly with VB.NET than
C# and will write much of the code for you.

--
I hope this helps,
Steve C. Orr, MCSD
[url]http://Steve.Orr.net[/url]


"Bill Priess" <no.spam@nospam.com> wrote in message
news:oprs60xlkfcimqky@localhost...

> I worked recently at a company that dropped VB.NET in favor of C#. We
> dropped VB.NET becuase of the amount of code that VB.NET required to do
> some amazingly simple things (which, btw, is something that even MSFT has
> acknowledged and on the roadmap, have said they will *fix*). Knowing both
> has helped me, but given the choice, I would have never picked up VB at
> all...
>
> Just in general, I have found that C# is easier to follow and much more
> logical and concise than VB is. Not to mention... XML Documnetation...
> Plus, as many of us know... never rely on MSFT to actually stick to a
> roadmap for anything. Just because one document says that this *feature*
> will be in the next version, don't think that there won't be another one
> that denies it. ;)
>
> (Just think back to the release of WinME, you know, the revolutionary OS
> that was supposed to be entirely 32-bit based and stable? ;) )
>
> Bill P.
>
> On Thu, 31 Jul 2003 16:05:24 -0400, Eric Wise <NOewise@pica.army.milSPAM>
> wrote:
>

> > Does anyone work for companies that actually implement both VB and C#?

I

> > know that you can do this in theory, I just find it hard to imagine that
> > a
> > company would split its programming technologies like that.
> >
> > Of course now with the CLR there doesn't seem to be any performance
> > benefit
> > to using C# over VB, and VB I think is an "easier" language to pick up.
> > I
> > actually wonder if the salaries between vb.net and c# will balance out a
> > little now since the language doesn't mean as much anymore.
> >
> > I personally am a VB developer moved into asp .net / vb .net. I've been
> > considering going ahead and learning C# as well. I have only academic
> > experience with C++, but it is enough that I can read c# examples and
> > convert them to vb so I don't think this is a big deal for me to pick up
> > the
> > new language. Just more wondering if I should even bother.
> >
> >
> >
> >
> >

>
>
>
> --
> Using M2, Opera's revolutionary e-mail client: [url]http://www.opera.com/m2/[/url]

[Joao S Cardoso [MVP]]

>Now that's efficiency.

And in the end... that is what is important. :)
Efficiency and quality.

C# or VB.NET... I choose vb.net. Coding less and do the same thing? Why not?
:)

I'll have less OverTime on the end of the month :)

Joao Cardoso (MVP dotNET)
================================================== =====
[LusoCoders]- [url]http://groups.yahoo.com/group/lusocoders/[/url]
[PontoNetPT]- [url]http://www.programando.net/regras.aspx[/url]
[email]jjscc@acinet.pt.nosp[/email]am - [url]www.acinet.pt[/url]
================================================== =====

[John Sparrow]

"Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message news:<e5G1PP6VDHA.2316@TK2MSFTNGP09.phx.gbl>...

I'd be genuinely interested to see some examples of tasks that can be
performed more quickly in VB.

Thanks,

John

PS. Although, of course, it does save you all that time declaring your
variables.... (wry grin)

> With VB.NET you can develop web applications faster than you can with C#.
> Now that's efficiency.
>
> --
> I hope this helps,
> Steve C. Orr, MCSD
> [url]http://Steve.Orr.net[/url]
>
>
> "Mark Heimonen" <markh@adiaim.com> wrote in message
> news:eDcS7K6VDHA.2364@TK2MSFTNGP09.phx.gbl...

> > Our company has developed mostly in VB.NET, but our latest projects are
> > being written in C#. We have projects that are half VB/half C#.
> > Personally, I'm starting to use C# whenever I can. It just seems more
> > efficient to me.
> >
> > There's a new roadmap available:
> >
> > [url]http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx[/url]
> >
> > It seems like C# is becoming a more "Advanced" language, while vb.net is
> > being targetted towards non-coders. True, the capabilities of both
> > languages are very similar, but I would recommend making the switch if it

> is

> > at all possible.
> >
> > -Mark
> >
> >
> > "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message
> > news:ubHYuC6VDHA.2040@TK2MSFTNGP10.phx.gbl...

> > > If you're on the job hunt, you'll increase your chances of landing a job

> by

> > > being able to say that you know both languages instead of just one.
> > > Then again there's something to be said for being a specialist. There is
> > > only so much time to learn. You may not want to become a jack of all

> trades

> > > but master of none.
> > >
> > > --
> > > I hope this helps,
> > > Steve C. Orr, MCSD
> > > [url]http://Steve.Orr.net[/url]
> > >
> > >
> > > "Eric Wise" <NOewise@pica.army.milSPAM> wrote in message
> > > news:exwW275VDHA.2252@TK2MSFTNGP10.phx.gbl...
> > > > Does anyone work for companies that actually implement both VB and C#?

> I

> > > > know that you can do this in theory, I just find it hard to imagine

> that
> a

> > > > company would split its programming technologies like that.
> > > >
> > > > Of course now with the CLR there doesn't seem to be any performance

> benefit

> > > > to using C# over VB, and VB I think is an "easier" language to pick

> up.
> I

> > > > actually wonder if the salaries between vb.net and c# will balance out

> a

> > > > little now since the language doesn't mean as much anymore.
> > > >
> > > > I personally am a VB developer moved into asp .net / vb .net. I've

> been

> > > > considering going ahead and learning C# as well. I have only academic
> > > > experience with C++, but it is enough that I can read c# examples and
> > > > convert them to vb so I don't think this is a big deal for me to pick

> up
>
> the

> > > > new language. Just more wondering if I should even bother.
> > > >
> > > >
> > > >
> > > >
> > >
> > >

> >
> >

[Kevin Spencer]

I can mention 1 task in particular that can be performed much more quickly
in VB.Net: Typing code. Since you don't have to worry about case, you (at
least I) can type your code a heck of a lot faster.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
[url]http://www.takempis.com[/url]
Complex things are made up of
lots of simple things.

"John Sparrow" <jsparrow@ecclescollege.ac.uk> wrote in message
news:1357b958.0308011212.6eeeeb13@posting.google.c om...

> "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message

news:<e5G1PP6VDHA.2316@TK2MSFTNGP09.phx.gbl>...

>
> I'd be genuinely interested to see some examples of tasks that can be
> performed more quickly in VB.
>
> Thanks,
>
> John
>
> PS. Although, of course, it does save you all that time declaring your
> variables.... (wry grin)
>

> > With VB.NET you can develop web applications faster than you can with

C#.

> > Now that's efficiency.
> >
> > --
> > I hope this helps,
> > Steve C. Orr, MCSD
> > [url]http://Steve.Orr.net[/url]
> >
> >
> > "Mark Heimonen" <markh@adiaim.com> wrote in message
> > news:eDcS7K6VDHA.2364@TK2MSFTNGP09.phx.gbl...

> > > Our company has developed mostly in VB.NET, but our latest projects

are

> > > being written in C#. We have projects that are half VB/half C#.
> > > Personally, I'm starting to use C# whenever I can. It just seems more
> > > efficient to me.
> > >
> > > There's a new roadmap available:
> > >
> > > [url]http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx[/url]
> > >
> > > It seems like C# is becoming a more "Advanced" language, while vb.net

is

> > > being targetted towards non-coders. True, the capabilities of both
> > > languages are very similar, but I would recommend making the switch if

it

> > is

> > > at all possible.
> > >
> > > -Mark
> > >
> > >
> > > "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message
> > > news:ubHYuC6VDHA.2040@TK2MSFTNGP10.phx.gbl...
> > > > If you're on the job hunt, you'll increase your chances of landing a

job

> > by

> > > > being able to say that you know both languages instead of just one.
> > > > Then again there's something to be said for being a specialist.

There is

> > > > only so much time to learn. You may not want to become a jack of

all

> > trades

> > > > but master of none.
> > > >
> > > > --
> > > > I hope this helps,
> > > > Steve C. Orr, MCSD
> > > > [url]http://Steve.Orr.net[/url]
> > > >
> > > >
> > > > "Eric Wise" <NOewise@pica.army.milSPAM> wrote in message
> > > > news:exwW275VDHA.2252@TK2MSFTNGP10.phx.gbl...
> > > > > Does anyone work for companies that actually implement both VB and

C#?

> > I

> > > > > know that you can do this in theory, I just find it hard to

imagine

> > that
> > a

> > > > > company would split its programming technologies like that.
> > > > >
> > > > > Of course now with the CLR there doesn't seem to be any

performance

> > benefit

> > > > > to using C# over VB, and VB I think is an "easier" language to

pick

> > up.
> > I

> > > > > actually wonder if the salaries between vb.net and c# will balance

out

> > a

> > > > > little now since the language doesn't mean as much anymore.
> > > > >
> > > > > I personally am a VB developer moved into asp .net / vb .net.

I've

> > been

> > > > > considering going ahead and learning C# as well. I have only

academic

> > > > > experience with C++, but it is enough that I can read c# examples

and

> > > > > convert them to vb so I don't think this is a big deal for me to

pick

> > up
> >
> > the

> > > > > new language. Just more wondering if I should even bother.
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >

[Steve C. Orr, MCSD]

There are so many things that are easier and quicker to do in VB.NET

Here's one: Debugging.
The VS.NET designer catches most VB.NET syntax errors as I'm typing them,
where as you have to wait until compile time and then get them all thrown at
you at once. Then you have to retrace your steps and go back to fix them
all, which could have a domino effect and require you to go back and change
other related things too. What a waste of time!

--
I hope this helps,
Steve C. Orr, MCSD
[url]http://Steve.Orr.net[/url]



"John Sparrow" <jsparrow@ecclescollege.ac.uk> wrote in message
news:1357b958.0308011212.6eeeeb13@posting.google.c om...

> "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message

news:<e5G1PP6VDHA.2316@TK2MSFTNGP09.phx.gbl>...

>
> I'd be genuinely interested to see some examples of tasks that can be
> performed more quickly in VB.
>
> Thanks,
>
> John
>
> PS. Although, of course, it does save you all that time declaring your
> variables.... (wry grin)
>

> > With VB.NET you can develop web applications faster than you can with

C#.

> > Now that's efficiency.
> >
> > --
> > I hope this helps,
> > Steve C. Orr, MCSD
> > [url]http://Steve.Orr.net[/url]
> >
> >
> > "Mark Heimonen" <markh@adiaim.com> wrote in message
> > news:eDcS7K6VDHA.2364@TK2MSFTNGP09.phx.gbl...

> > > Our company has developed mostly in VB.NET, but our latest projects

are

> > > being written in C#. We have projects that are half VB/half C#.
> > > Personally, I'm starting to use C# whenever I can. It just seems more
> > > efficient to me.
> > >
> > > There's a new roadmap available:
> > >
> > > [url]http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx[/url]
> > >
> > > It seems like C# is becoming a more "Advanced" language, while vb.net

is

> > > being targetted towards non-coders. True, the capabilities of both
> > > languages are very similar, but I would recommend making the switch if

it

> > is

> > > at all possible.
> > >
> > > -Mark
> > >
> > >
> > > "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message
> > > news:ubHYuC6VDHA.2040@TK2MSFTNGP10.phx.gbl...
> > > > If you're on the job hunt, you'll increase your chances of landing a

job

> > by

> > > > being able to say that you know both languages instead of just one.
> > > > Then again there's something to be said for being a specialist.

There is

> > > > only so much time to learn. You may not want to become a jack of

all

> > trades

> > > > but master of none.
> > > >
> > > > --
> > > > I hope this helps,
> > > > Steve C. Orr, MCSD
> > > > [url]http://Steve.Orr.net[/url]
> > > >
> > > >
> > > > "Eric Wise" <NOewise@pica.army.milSPAM> wrote in message
> > > > news:exwW275VDHA.2252@TK2MSFTNGP10.phx.gbl...
> > > > > Does anyone work for companies that actually implement both VB and

C#?

> > I

> > > > > know that you can do this in theory, I just find it hard to

imagine

> > that
> > a

> > > > > company would split its programming technologies like that.
> > > > >
> > > > > Of course now with the CLR there doesn't seem to be any

performance

> > benefit

> > > > > to using C# over VB, and VB I think is an "easier" language to

pick

> > up.
> > I

> > > > > actually wonder if the salaries between vb.net and c# will balance

out

> > a

> > > > > little now since the language doesn't mean as much anymore.
> > > > >
> > > > > I personally am a VB developer moved into asp .net / vb .net.

I've

> > been

> > > > > considering going ahead and learning C# as well. I have only

academic

> > > > > experience with C++, but it is enough that I can read c# examples

and

> > > > > convert them to vb so I don't think this is a big deal for me to

pick

> > up
> >
> > the

> > > > > new language. Just more wondering if I should even bother.
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >

[John Sparrow]

Steve, have you actually opened up a C# project in VS and tried it??
It's got the same Intellisence features VB has!!

Yes, C# is case sensitive, but again that is all sorted by
intellisence. When you need to type
"LoadPageStateFromPersistenceMedium" just type "lo" (lower case) and
pick it from the list. Sorted.

I even opened up a VB project to see if there was something amazing I
was missing out on. The behaviour is identical!!

John

"Kevin Spencer" <kevin@takempis.com> wrote in message news:<uRsC1BHWDHA.1744@TK2MSFTNGP12.phx.gbl>...

> I can mention 1 task in particular that can be performed much more quickly
> in VB.Net: Typing code. Since you don't have to worry about case, you (at
> least I) can type your code a heck of a lot faster.
>
> --
> HTH,
>
> Kevin Spencer
> Microsoft MVP
> .Net Developer
> [url]http://www.takempis.com[/url]
> Complex things are made up of
> lots of simple things.
>
> "John Sparrow" <jsparrow@ecclescollege.ac.uk> wrote in message
> news:1357b958.0308011212.6eeeeb13@posting.google.c om...

> > "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message

> news:<e5G1PP6VDHA.2316@TK2MSFTNGP09.phx.gbl>...

> >
> > I'd be genuinely interested to see some examples of tasks that can be
> > performed more quickly in VB.
> >
> > Thanks,
> >
> > John
> >
> > PS. Although, of course, it does save you all that time declaring your
> > variables.... (wry grin)
> >

> > > With VB.NET you can develop web applications faster than you can with

> C#.

> > > Now that's efficiency.
> > >
> > > --
> > > I hope this helps,
> > > Steve C. Orr, MCSD
> > > [url]http://Steve.Orr.net[/url]
> > >
> > >
> > > "Mark Heimonen" <markh@adiaim.com> wrote in message
> > > news:eDcS7K6VDHA.2364@TK2MSFTNGP09.phx.gbl...
> > > > Our company has developed mostly in VB.NET, but our latest projects

> are

> > > > being written in C#. We have projects that are half VB/half C#.
> > > > Personally, I'm starting to use C# whenever I can. It just seems more
> > > > efficient to me.
> > > >
> > > > There's a new roadmap available:
> > > >
> > > > [url]http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx[/url]
> > > >
> > > > It seems like C# is becoming a more "Advanced" language, while vb.net

> is

> > > > being targetted towards non-coders. True, the capabilities of both
> > > > languages are very similar, but I would recommend making the switch if

> it
> is

> > > > at all possible.
> > > >
> > > > -Mark
> > > >
> > > >
> > > > "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message
> > > > news:ubHYuC6VDHA.2040@TK2MSFTNGP10.phx.gbl...
> > > > > If you're on the job hunt, you'll increase your chances of landing a

> job
> by

> > > > > being able to say that you know both languages instead of just one.
> > > > > Then again there's something to be said for being a specialist.

> There is

> > > > > only so much time to learn. You may not want to become a jack of

> all
> trades

> > > > > but master of none.
> > > > >
> > > > > --
> > > > > I hope this helps,
> > > > > Steve C. Orr, MCSD
> > > > > [url]http://Steve.Orr.net[/url]
> > > > >
> > > > >
> > > > > "Eric Wise" <NOewise@pica.army.milSPAM> wrote in message
> > > > > news:exwW275VDHA.2252@TK2MSFTNGP10.phx.gbl...
> > > > > > Does anyone work for companies that actually implement both VB and

> C#?
> I

> > > > > > know that you can do this in theory, I just find it hard to

> imagine

> > > that
> > > a
> > > > > > company would split its programming technologies like that.
> > > > > >
> > > > > > Of course now with the CLR there doesn't seem to be any

> performance
> benefit

> > > > > > to using C# over VB, and VB I think is an "easier" language to

> pick

> > > up.
> > > I
> > > > > > actually wonder if the salaries between vb.net and c# will balance

> out
> a

> > > > > > little now since the language doesn't mean as much anymore.
> > > > > >
> > > > > > I personally am a VB developer moved into asp .net / vb .net.

> I've
> been

> > > > > > considering going ahead and learning C# as well. I have only

> academic

> > > > > > experience with C++, but it is enough that I can read c# examples

> and

> > > > > > convert them to vb so I don't think this is a big deal for me to

> pick

> > > up
> > >
> > > the
> > > > > > new language. Just more wondering if I should even bother.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >

[Bill Priess]

Ahh, but there is one of the great things about C-based languages... case-
sensitivity allows for mixed case variables... _someVariable and
_SomeVariable are two distinct entities.

As for VB/Boolean/Intellisense... C'mon.. have we gotten so bad that we can
not type 4 or 5 characters? ;) (had to lighten this up...)


Bill P.



On Mon, 4 Aug 2003 08:41:13 -0400, msnews.microsoft.com
<cdglasser@hotmail.com> wrote:

> Actually, C#'s intellisense, in my experience, is not quite as good as
> VB's.
> Three examples come to mind:
>
> 1) In VB, if I define a boolean variable and later in the prcoedure go to
> assign a value to it, VB gives me a list of True or False after I type
> the
> assignment operator - C# doesn't do this.
>
> 2) If I define an Enum type and declare a variable of that type, when I
> go
> to assign a value to that variable in VB, I get a dropdown list of valid
> values for that type. I don't get this in C#.
>
> 3) And then there's the case-seinsitivity thing. In VB, I can declare a
> variable, say _someVariable, and later on I can just type the whole thing
> in
> lower case and VB knows what variable I mean and it will automatically
> correct the case to match the way I declared it and provide any
> applicable
> intellisense. In C#, if I don't type it the same way it was declared, I
> don't get any intellisense dropdown because C# considers it a different
> variable.
>
> Chris G.
>
> "John Sparrow" <jsparrow@ecclescollege.ac.uk> wrote in message
> news:1357b958.0308020245.103949ac@posting.google.c om...

>> Steve, have you actually opened up a C# project in VS and tried it??
>> It's got the same Intellisence features VB has!!
>>
>> Yes, C# is case sensitive, but again that is all sorted by
>> intellisence. When you need to type
>> "LoadPageStateFromPersistenceMedium" just type "lo" (lower case) and
>> pick it from the list. Sorted.
>>
>> I even opened up a VB project to see if there was something amazing I
>> was missing out on. The behaviour is identical!!
>>
>> John
>>
>> "Kevin Spencer" <kevin@takempis.com> wrote in message

> news:<uRsC1BHWDHA.1744@TK2MSFTNGP12.phx.gbl>...

>> > I can mention 1 task in particular that can be performed much more

> quickly

>> > in VB.Net: Typing code. Since you don't have to worry about case, you

> (at

>> > least I) can type your code a heck of a lot faster.
>> >
>> > -- > HTH,
>> >
>> > Kevin Spencer
>> > Microsoft MVP
>> > .Net Developer
>> > [url]http://www.takempis.com[/url]
>> > Complex things are made up of
>> > lots of simple things.
>> >
>> > "John Sparrow" <jsparrow@ecclescollege.ac.uk> wrote in message
>> > news:1357b958.0308011212.6eeeeb13@posting.google.c om...
>> > > "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message
>> > news:<e5G1PP6VDHA.2316@TK2MSFTNGP09.phx.gbl>...
>> > >
>> > > I'd be genuinely interested to see some examples of tasks that can

>> be

>> > > performed more quickly in VB.
>> > >
>> > > Thanks,
>> > >
>> > > John
>> > >
>> > > PS. Although, of course, it does save you all that time declaring

>> your

>> > > variables.... (wry grin)
>> > >
>> > > > With VB.NET you can develop web applications faster than you can

> with

>> > C#.
>> > > > Now that's efficiency.
>> > > >
>> > > > -- > > > I hope this helps,
>> > > > Steve C. Orr, MCSD
>> > > > [url]http://Steve.Orr.net[/url]
>> > > >
>> > > >
>> > > > "Mark Heimonen" <markh@adiaim.com> wrote in message
>> > > > news:eDcS7K6VDHA.2364@TK2MSFTNGP09.phx.gbl...
>> > > > > Our company has developed mostly in VB.NET, but our latest

> projects

>> > are
>> > > > > being written in C#. We have projects that are half VB/half C#.
>> > > > > Personally, I'm starting to use C# whenever I can. It just

>> seems

> more

>> > > > > efficient to me.
>> > > > >
>> > > > > There's a new roadmap available:
>> > > > >
>> > > > > [url]http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx[/url]
>> > > > >
>> > > > > It seems like C# is becoming a more "Advanced" language, while

> vb.net

>> > is
>> > > > > being targetted towards non-coders. True, the capabilities of

> both

>> > > > > languages are very similar, but I would recommend making the

> switch if

>> > it
>> > is
>> > > > > at all possible.
>> > > > >
>> > > > > -Mark
>> > > > >
>> > > > >
>> > > > > "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message
>> > > > > news:ubHYuC6VDHA.2040@TK2MSFTNGP10.phx.gbl...
>> > > > > > If you're on the job hunt, you'll increase your chances of

> landing a

>> > job
>> > by
>> > > > > > being able to say that you know both languages instead of just

> one.

>> > > > > > Then again there's something to be said for being a

>> specialist.

>> > There is
>> > > > > > only so much time to learn. You may not want to become a jack

> of

>> > all
>> > trades
>> > > > > > but master of none.
>> > > > > >
>> > > > > > -- > > > > > I hope this helps,
>> > > > > > Steve C. Orr, MCSD
>> > > > > > [url]http://Steve.Orr.net[/url]
>> > > > > >
>> > > > > >
>> > > > > > "Eric Wise" <NOewise@pica.army.milSPAM> wrote in message
>> > > > > > news:exwW275VDHA.2252@TK2MSFTNGP10.phx.gbl...
>> > > > > > > Does anyone work for companies that actually implement both

>> VB

> and

>> > C#?
>> > I
>> > > > > > > know that you can do this in theory, I just find it hard to
>> > imagine
>> > > > that
>> > > > a
>> > > > > > > company would split its programming technologies like that.
>> > > > > > >
>> > > > > > > Of course now with the CLR there doesn't seem to be any
>> > performance
>> > benefit
>> > > > > > > to using C# over VB, and VB I think is an "easier" language

>> to

>> > pick
>> > > > up.
>> > > > I
>> > > > > > > actually wonder if the salaries between vb.net and c# will

> balance

>> > out
>> > a
>> > > > > > > little now since the language doesn't mean as much anymore.
>> > > > > > >
>> > > > > > > I personally am a VB developer moved into asp .net / vb

>> .net.

>> > I've
>> > been
>> > > > > > > considering going ahead and learning C# as well. I have

>> only

>> > academic
>> > > > > > > experience with C++, but it is enough that I can read c#

> examples

>> > and
>> > > > > > > convert them to vb so I don't think this is a big deal for

>> me

> to

>> > pick
>> > > > up
>> > > >
>> > > > the
>> > > > > > > new language. Just more wondering if I should even bother.
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > >
>> > > > >

>
>
>

--
Using M2, Opera's revolutionary e-mail client: [url]http://www.opera.com/m2/[/url]

[Steve C. Orr, MCSD]

So you consider it to be a good thing that _someVariable and _SomeVariable
are two different variables? To me it sounds like a great way to introduce
bugs and typos. It's hard enough to remember the exact names of all the
variables in a large, complex app, but having to remember the case of every
letter in every variable is a bit more than I'd care to deal with. Instead
I'd like to spend my time and energy programming the logic of my
application.

The VB/Boolean/Intellisense thing he mentioned is just one of many such
examples. Multiply that by the number of times you'll run across stuff like
this during the development of a large, complex app and it turns into
something quite significant.

Perhaps your employer has so much money to spare that they don't mind paying
you to chase down issues like these all day long.
;)

--
I hope this helps,
Steve C. Orr, MCSD
[url]http://Steve.Orr.net[/url]


"Bill Priess" <no.spam@nospam.com> wrote in message
news:oprteja1ujcimqky@localhost...

> Ahh, but there is one of the great things about C-based languages... case-
> sensitivity allows for mixed case variables... _someVariable and
> _SomeVariable are two distinct entities.
>
> As for VB/Boolean/Intellisense... C'mon.. have we gotten so bad that we

can

> not type 4 or 5 characters? ;) (had to lighten this up...)
>
>
> Bill P.
>
>
>
> On Mon, 4 Aug 2003 08:41:13 -0400, msnews.microsoft.com
> <cdglasser@hotmail.com> wrote:
>

> > Actually, C#'s intellisense, in my experience, is not quite as good as
> > VB's.
> > Three examples come to mind:
> >
> > 1) In VB, if I define a boolean variable and later in the prcoedure go

to

> > assign a value to it, VB gives me a list of True or False after I type
> > the
> > assignment operator - C# doesn't do this.
> >
> > 2) If I define an Enum type and declare a variable of that type, when I
> > go
> > to assign a value to that variable in VB, I get a dropdown list of valid
> > values for that type. I don't get this in C#.
> >
> > 3) And then there's the case-seinsitivity thing. In VB, I can declare a
> > variable, say _someVariable, and later on I can just type the whole

thing

> > in
> > lower case and VB knows what variable I mean and it will automatically
> > correct the case to match the way I declared it and provide any
> > applicable
> > intellisense. In C#, if I don't type it the same way it was declared, I
> > don't get any intellisense dropdown because C# considers it a different
> > variable.
> >
> > Chris G.
> >
> > "John Sparrow" <jsparrow@ecclescollege.ac.uk> wrote in message
> > news:1357b958.0308020245.103949ac@posting.google.c om...

> >> Steve, have you actually opened up a C# project in VS and tried it??
> >> It's got the same Intellisence features VB has!!
> >>
> >> Yes, C# is case sensitive, but again that is all sorted by
> >> intellisence. When you need to type
> >> "LoadPageStateFromPersistenceMedium" just type "lo" (lower case) and
> >> pick it from the list. Sorted.
> >>
> >> I even opened up a VB project to see if there was something amazing I
> >> was missing out on. The behaviour is identical!!
> >>
> >> John
> >>
> >> "Kevin Spencer" <kevin@takempis.com> wrote in message

> > news:<uRsC1BHWDHA.1744@TK2MSFTNGP12.phx.gbl>...

> >> > I can mention 1 task in particular that can be performed much more

> > quickly

> >> > in VB.Net: Typing code. Since you don't have to worry about case, you

> > (at

> >> > least I) can type your code a heck of a lot faster.
> >> >
> >> > -- > HTH,
> >> >
> >> > Kevin Spencer
> >> > Microsoft MVP
> >> > .Net Developer
> >> > [url]http://www.takempis.com[/url]
> >> > Complex things are made up of
> >> > lots of simple things.
> >> >
> >> > "John Sparrow" <jsparrow@ecclescollege.ac.uk> wrote in message
> >> > news:1357b958.0308011212.6eeeeb13@posting.google.c om...
> >> > > "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message
> >> > news:<e5G1PP6VDHA.2316@TK2MSFTNGP09.phx.gbl>...
> >> > >
> >> > > I'd be genuinely interested to see some examples of tasks that can
> >> be
> >> > > performed more quickly in VB.
> >> > >
> >> > > Thanks,
> >> > >
> >> > > John
> >> > >
> >> > > PS. Although, of course, it does save you all that time declaring
> >> your
> >> > > variables.... (wry grin)
> >> > >
> >> > > > With VB.NET you can develop web applications faster than you can

> > with

> >> > C#.
> >> > > > Now that's efficiency.
> >> > > >
> >> > > > -- > > > I hope this helps,
> >> > > > Steve C. Orr, MCSD
> >> > > > [url]http://Steve.Orr.net[/url]
> >> > > >
> >> > > >
> >> > > > "Mark Heimonen" <markh@adiaim.com> wrote in message
> >> > > > news:eDcS7K6VDHA.2364@TK2MSFTNGP09.phx.gbl...
> >> > > > > Our company has developed mostly in VB.NET, but our latest

> > projects

> >> > are
> >> > > > > being written in C#. We have projects that are half VB/half

C#.

> >> > > > > Personally, I'm starting to use C# whenever I can. It just
> >> seems

> > more

> >> > > > > efficient to me.
> >> > > > >
> >> > > > > There's a new roadmap available:
> >> > > > >
> >> > > > > [url]http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx[/url]
> >> > > > >
> >> > > > > It seems like C# is becoming a more "Advanced" language, while

> > vb.net

> >> > is
> >> > > > > being targetted towards non-coders. True, the capabilities of

> > both

> >> > > > > languages are very similar, but I would recommend making the

> > switch if

> >> > it
> >> > is
> >> > > > > at all possible.
> >> > > > >
> >> > > > > -Mark
> >> > > > >
> >> > > > >
> >> > > > > "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message
> >> > > > > news:ubHYuC6VDHA.2040@TK2MSFTNGP10.phx.gbl...
> >> > > > > > If you're on the job hunt, you'll increase your chances of

> > landing a

> >> > job
> >> > by
> >> > > > > > being able to say that you know both languages instead of

just

> > one.

> >> > > > > > Then again there's something to be said for being a
> >> specialist.
> >> > There is
> >> > > > > > only so much time to learn. You may not want to become a

jack

> > of

> >> > all
> >> > trades
> >> > > > > > but master of none.
> >> > > > > >
> >> > > > > > -- > > > > > I hope this helps,
> >> > > > > > Steve C. Orr, MCSD
> >> > > > > > [url]http://Steve.Orr.net[/url]
> >> > > > > >
> >> > > > > >
> >> > > > > > "Eric Wise" <NOewise@pica.army.milSPAM> wrote in message
> >> > > > > > news:exwW275VDHA.2252@TK2MSFTNGP10.phx.gbl...
> >> > > > > > > Does anyone work for companies that actually implement both
> >> VB

> > and

> >> > C#?
> >> > I
> >> > > > > > > know that you can do this in theory, I just find it hard to
> >> > imagine
> >> > > > that
> >> > > > a
> >> > > > > > > company would split its programming technologies like that.
> >> > > > > > >
> >> > > > > > > Of course now with the CLR there doesn't seem to be any
> >> > performance
> >> > benefit
> >> > > > > > > to using C# over VB, and VB I think is an "easier" language
> >> to
> >> > pick
> >> > > > up.
> >> > > > I
> >> > > > > > > actually wonder if the salaries between vb.net and c# will

> > balance

> >> > out
> >> > a
> >> > > > > > > little now since the language doesn't mean as much anymore.
> >> > > > > > >
> >> > > > > > > I personally am a VB developer moved into asp .net / vb
> >> .net.
> >> > I've
> >> > been
> >> > > > > > > considering going ahead and learning C# as well. I have
> >> only
> >> > academic
> >> > > > > > > experience with C++, but it is enough that I can read c#

> > examples

> >> > and
> >> > > > > > > convert them to vb so I don't think this is a big deal for
> >> me

> > to

> >> > pick
> >> > > > up
> >> > > >
> >> > > > the
> >> > > > > > > new language. Just more wondering if I should even bother.
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >

> >
> >
> >

>
>
>
> --
> Using M2, Opera's revolutionary e-mail client: [url]http://www.opera.com/m2/[/url]

[Jerry III]

Actually allowing the programmer to use different casing for the same
variable intriduces bugs. If you mistype your variables in C# (or C/C++ for
that matter) your code will not compile. You have to use exactly the same
name all over your code, not like in VB where you can have four different
casings pointing to the same variable. C just requires more discipline.

Jerry

"Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message
news:eUsCWxtWDHA.608@TK2MSFTNGP12.phx.gbl...

> So you consider it to be a good thing that _someVariable and

_SomeVariable

> are two different variables? To me it sounds like a great way to

introduce

> bugs and typos. It's hard enough to remember the exact names of all the
> variables in a large, complex app, but having to remember the case of

every

> letter in every variable is a bit more than I'd care to deal with.

Instead

> I'd like to spend my time and energy programming the logic of my
> application.
>
> The VB/Boolean/Intellisense thing he mentioned is just one of many such
> examples. Multiply that by the number of times you'll run across stuff

like

> this during the development of a large, complex app and it turns into
> something quite significant.
>
> Perhaps your employer has so much money to spare that they don't mind

paying

> you to chase down issues like these all day long.
> ;)
>
> --
> I hope this helps,
> Steve C. Orr, MCSD
> [url]http://Steve.Orr.net[/url]
>
>
> "Bill Priess" <no.spam@nospam.com> wrote in message
> news:oprteja1ujcimqky@localhost...

> > Ahh, but there is one of the great things about C-based languages...

case-

> > sensitivity allows for mixed case variables... _someVariable and
> > _SomeVariable are two distinct entities.
> >
> > As for VB/Boolean/Intellisense... C'mon.. have we gotten so bad that we

> can

> > not type 4 or 5 characters? ;) (had to lighten this up...)
> >
> >
> > Bill P.
> >
> >
> >
> > On Mon, 4 Aug 2003 08:41:13 -0400, msnews.microsoft.com
> > <cdglasser@hotmail.com> wrote:
> >

> > > Actually, C#'s intellisense, in my experience, is not quite as good as
> > > VB's.
> > > Three examples come to mind:
> > >
> > > 1) In VB, if I define a boolean variable and later in the prcoedure go

> to

> > > assign a value to it, VB gives me a list of True or False after I type
> > > the
> > > assignment operator - C# doesn't do this.
> > >
> > > 2) If I define an Enum type and declare a variable of that type, when

I

> > > go
> > > to assign a value to that variable in VB, I get a dropdown list of

valid

> > > values for that type. I don't get this in C#.
> > >
> > > 3) And then there's the case-seinsitivity thing. In VB, I can declare

a

> > > variable, say _someVariable, and later on I can just type the whole

> thing

> > > in
> > > lower case and VB knows what variable I mean and it will automatically
> > > correct the case to match the way I declared it and provide any
> > > applicable
> > > intellisense. In C#, if I don't type it the same way it was declared,

I

> > > don't get any intellisense dropdown because C# considers it a

different

> > > variable.
> > >
> > > Chris G.
> > >
> > > "John Sparrow" <jsparrow@ecclescollege.ac.uk> wrote in message
> > > news:1357b958.0308020245.103949ac@posting.google.c om...
> > >> Steve, have you actually opened up a C# project in VS and tried it??
> > >> It's got the same Intellisence features VB has!!
> > >>
> > >> Yes, C# is case sensitive, but again that is all sorted by
> > >> intellisence. When you need to type
> > >> "LoadPageStateFromPersistenceMedium" just type "lo" (lower case) and
> > >> pick it from the list. Sorted.
> > >>
> > >> I even opened up a VB project to see if there was something amazing I
> > >> was missing out on. The behaviour is identical!!
> > >>
> > >> John
> > >>
> > >> "Kevin Spencer" <kevin@takempis.com> wrote in message
> > > news:<uRsC1BHWDHA.1744@TK2MSFTNGP12.phx.gbl>...
> > >> > I can mention 1 task in particular that can be performed much more
> > > quickly
> > >> > in VB.Net: Typing code. Since you don't have to worry about case,

you

> > > (at
> > >> > least I) can type your code a heck of a lot faster.
> > >> >
> > >> > -- > HTH,
> > >> >
> > >> > Kevin Spencer
> > >> > Microsoft MVP
> > >> > .Net Developer
> > >> > [url]http://www.takempis.com[/url]
> > >> > Complex things are made up of
> > >> > lots of simple things.
> > >> >
> > >> > "John Sparrow" <jsparrow@ecclescollege.ac.uk> wrote in message
> > >> > news:1357b958.0308011212.6eeeeb13@posting.google.c om...
> > >> > > "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message
> > >> > news:<e5G1PP6VDHA.2316@TK2MSFTNGP09.phx.gbl>...
> > >> > >
> > >> > > I'd be genuinely interested to see some examples of tasks that

can

> > >> be
> > >> > > performed more quickly in VB.
> > >> > >
> > >> > > Thanks,
> > >> > >
> > >> > > John
> > >> > >
> > >> > > PS. Although, of course, it does save you all that time declaring
> > >> your
> > >> > > variables.... (wry grin)
> > >> > >
> > >> > > > With VB.NET you can develop web applications faster than you

can

> > > with
> > >> > C#.
> > >> > > > Now that's efficiency.
> > >> > > >
> > >> > > > -- > > > I hope this helps,
> > >> > > > Steve C. Orr, MCSD
> > >> > > > [url]http://Steve.Orr.net[/url]
> > >> > > >
> > >> > > >
> > >> > > > "Mark Heimonen" <markh@adiaim.com> wrote in message
> > >> > > > news:eDcS7K6VDHA.2364@TK2MSFTNGP09.phx.gbl...
> > >> > > > > Our company has developed mostly in VB.NET, but our latest
> > > projects
> > >> > are
> > >> > > > > being written in C#. We have projects that are half VB/half

> C#.

> > >> > > > > Personally, I'm starting to use C# whenever I can. It just
> > >> seems
> > > more
> > >> > > > > efficient to me.
> > >> > > > >
> > >> > > > > There's a new roadmap available:
> > >> > > > >
> > >> > > > > [url]http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx[/url]
> > >> > > > >
> > >> > > > > It seems like C# is becoming a more "Advanced" language,

while

> > > vb.net
> > >> > is
> > >> > > > > being targetted towards non-coders. True, the capabilities

of

> > > both
> > >> > > > > languages are very similar, but I would recommend making the
> > > switch if
> > >> > it
> > >> > is
> > >> > > > > at all possible.
> > >> > > > >
> > >> > > > > -Mark
> > >> > > > >
> > >> > > > >
> > >> > > > > "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message
> > >> > > > > news:ubHYuC6VDHA.2040@TK2MSFTNGP10.phx.gbl...
> > >> > > > > > If you're on the job hunt, you'll increase your chances of
> > > landing a
> > >> > job
> > >> > by
> > >> > > > > > being able to say that you know both languages instead of

> just

> > > one.
> > >> > > > > > Then again there's something to be said for being a
> > >> specialist.
> > >> > There is
> > >> > > > > > only so much time to learn. You may not want to become a

> jack

> > > of
> > >> > all
> > >> > trades
> > >> > > > > > but master of none.
> > >> > > > > >
> > >> > > > > > -- > > > > > I hope this helps,
> > >> > > > > > Steve C. Orr, MCSD
> > >> > > > > > [url]http://Steve.Orr.net[/url]
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > "Eric Wise" <NOewise@pica.army.milSPAM> wrote in message
> > >> > > > > > news:exwW275VDHA.2252@TK2MSFTNGP10.phx.gbl...
> > >> > > > > > > Does anyone work for companies that actually implement

both

> > >> VB
> > > and
> > >> > C#?
> > >> > I
> > >> > > > > > > know that you can do this in theory, I just find it hard

to

> > >> > imagine
> > >> > > > that
> > >> > > > a
> > >> > > > > > > company would split its programming technologies like

that.

> > >> > > > > > >
> > >> > > > > > > Of course now with the CLR there doesn't seem to be any
> > >> > performance
> > >> > benefit
> > >> > > > > > > to using C# over VB, and VB I think is an "easier"

language

> > >> to
> > >> > pick
> > >> > > > up.
> > >> > > > I
> > >> > > > > > > actually wonder if the salaries between vb.net and c#

will

> > > balance
> > >> > out
> > >> > a
> > >> > > > > > > little now since the language doesn't mean as much

anymore.

> > >> > > > > > >
> > >> > > > > > > I personally am a VB developer moved into asp .net / vb
> > >> .net.
> > >> > I've
> > >> > been
> > >> > > > > > > considering going ahead and learning C# as well. I have
> > >> only
> > >> > academic
> > >> > > > > > > experience with C++, but it is enough that I can read c#
> > > examples
> > >> > and
> > >> > > > > > > convert them to vb so I don't think this is a big deal

for

> > >> me
> > > to
> > >> > pick
> > >> > > > up
> > >> > > >
> > >> > > > the
> > >> > > > > > > new language. Just more wondering if I should even

bother.

> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > > >
> > >
> > >
> > >

> >
> >
> >
> > --
> > Using M2, Opera's revolutionary e-mail client: [url]http://www.opera.com/m2/[/url]

>
>

[John Sparrow]

"Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message news:<eUsCWxtWDHA.608@TK2MSFTNGP12.phx.gbl>...

> So you consider it to be a good thing that _someVariable and _SomeVariable
> are two different variables? To me it sounds like a great way to introduce
> bugs and typos. It's hard enough to remember the exact names of all the

It's common practice in some environments to use all-lower-case for
fields, and capitalisation for Properties. A clear distinction I've
never had any problems with (ie 'color' is the field and 'Color' is
the property).

And all sorted by intellisense too.

> The VB/Boolean/Intellisense thing he mentioned is just one of many such
> examples. Multiply that by the number of times you'll run across stuff like
> this during the development of a large, complex app and it turns into
> something quite significant.

And the many other examples? like the debugging example - where VB
proved less effective at detecting type incompatibility? (see my
previous post)

I want to stress here once again that I'm not rubbishing VB - rather I
am defending C# against ill informed critisism - specifically of
offering lower productivity.

It can't be sunstantiated - and if necessary I'll do a keystroke
analysis of two identically functioning programs (VB v C#) to prove
it!

I'd be prepared to bet the C# version involved less typing, as well
(of course)as offering improved compile time type checking.

John

[John Kraft]

Jerry III wrote:

> Actually allowing the programmer to use different casing for the same
> variable intriduces bugs. If you mistype your variables in C# (or C/C++ for
> that matter) your code will not compile. You have to use exactly the same
> name all over your code, not like in VB where you can have four different
> casings pointing to the same variable. C just requires more discipline.

Perfect example of what's wrong with the world today. Let's not have
the discipline to do things correctly... lets just do whatever we feel
like and expect someone else will come along and clean it up for us.

John

[Steve C. Orr, MCSD]

It's not "incorrect" to mix case in VB.NET so your point is moot.
Furthermore, we're not expecting "somebody else" to clean up after us.
We're expecting the computer (VS.NET specifically) to assist us with minor
details that are unimportant to the logic of the program. Computers exist
to do things for us. If you don't like that then I don't see why you use
computers at all. All day long I write programs that do things for other
people. Microsoft programmers put a lot of effort into creating VS.NET so
it would do things like this for us and make our jobs easier. Are you
suggesting we throw away their efforts and do things manually? That seems
like a waste of time and money.

--
I hope this helps,
Steve C. Orr, MCSD
[url]http://Steve.Orr.net[/url]



"John Kraft" <jhkraft@ilstu.edu> wrote in message
news:bgrlo2$c7r$1@malachite.ilstu.edu...

> Jerry III wrote:
>

> > Actually allowing the programmer to use different casing for the same
> > variable intriduces bugs. If you mistype your variables in C# (or C/C++

for

> > that matter) your code will not compile. You have to use exactly the

same

> > name all over your code, not like in VB where you can have four

different

> > casings pointing to the same variable. C just requires more discipline.

>
> Perfect example of what's wrong with the world today. Let's not have
> the discipline to do things correctly... lets just do whatever we feel
> like and expect someone else will come along and clean it up for us.
>
> John
>

[Jerry III]

All I'm saying is that if you don't work completely alone you need to write
readable code. And using different capitalization for the same variable
really lowers the ability of somebody else than you to read and understand
the code. MaxIndex and MAXINDEX might be the same from the VB compiler point
of view but it's fairly difficult to get that for a human. If you think it's
not important for your code to be easy to understand - fine (if it was
difficult to write it should be difficult to read), but most of us work with
others and can't afford to waste time trying to match different identifiers
together. And it gets even worse with non-english languages (Java for
example allows for localized variable names, I'm not sure about VB). There's
a reason why vast majority of programming languages (and computer
technologies in general) do distinguish between different casings...

Jerry

"Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message
news:OtK7FFGXDHA.736@TK2MSFTNGP09.phx.gbl...

> It's not "incorrect" to mix case in VB.NET so your point is moot.
> Furthermore, we're not expecting "somebody else" to clean up after us.
> We're expecting the computer (VS.NET specifically) to assist us with minor
> details that are unimportant to the logic of the program. Computers exist
> to do things for us. If you don't like that then I don't see why you use
> computers at all. All day long I write programs that do things for other
> people. Microsoft programmers put a lot of effort into creating VS.NET so
> it would do things like this for us and make our jobs easier. Are you
> suggesting we throw away their efforts and do things manually? That seems
> like a waste of time and money.
>
> --
> I hope this helps,
> Steve C. Orr, MCSD
> [url]http://Steve.Orr.net[/url]

[John Sparrow]

This may be true to *you* as a VB programmer, but programmers familiar
with C# find the code easy to read.

In the same way, I find reading VB similar to wading through treacle.
But I'm sure it makes perfect sense to you.

The agument that "I can't read C#, therefore C# is difficult to read."
is like saying "I can't speak French, therefore French is difficult to
speak."

Subjectively true, objectively facile.

Still waiting to here about the productivity comparison. Should I do
the keystroke analysis??? grin.

John


"Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message news:<uZlO2vKXDHA.1640@TK2MSFTNGP10.phx.gbl>...

> As discussed already, VS.NET automatically adjusts the case of your VB.NET
> variables so that they all match. Therefore your point is again moot.
> Also, because VB.NET uses real words it is far more readable than C#. Even
> many C# programmers would likely agree with that. C#'s syntax strength is
> it's brevity, not readability.

[John Kraft]

Steve C. Orr, MCSD wrote:

> As discussed already, VS.NET automatically adjusts the case of your VB.NET
> variables so that they all match. Therefore your point is again moot.
> Also, because VB.NET uses real words it is far more readable than C#. Even
> many C# programmers would likely agree with that. C#'s syntax strength is
> it's brevity, not readability.
>

That's like saying that Spanish is more readable than Japanese. To
whom? I think a Japanese/Chinese person would disagree with you. That
is all a matter of perspective.

My first language I ever learned was C. Therefore, to me, C derived
languages are much easier to read. VB is easier to read for people who
are not programmers or who have only programmed in VB like languages.
Once again, we should base our comparison of the languages on the
languages themselves. After all, a language is nothing more than a
collection of symbol and a syntax to put those symbols together to
communicate something.

Additionally, "better" is a suggestive term. Maybe the discussion
should focus on which is "more powerful", "easier to learn", etc. I
personally tend to judge a language mostly on what a language can do,
with only a little bit given to ease of use. This is why I think C++ is
the best language ever made. But, that's a personal preference.

I personally prefer the c# language because I am more familier with the
syntax and there are, according to books I've read, some things you can
do in c# that cannot be done in VB. I am however forced to use VB in my
occupational position and have learned the syntax well enough that I am
mostly comfortable with it, even if I don't like it.

John

[Steve C. Orr, MCSD]

No, I'm saying that I can read the english language, therefore VB.NET is
easy to read.
VB.NET uses real words, that makes it READABLE.
Of course anyone can read C# with enough training, but it takes a good deal
more training because it has much less in common with the english language
which most of us already know to begin with.

--
I hope this helps,
Steve C. Orr, MCSD
[url]http://Steve.Orr.net[/url]


"John Sparrow" <jsparrow@ecclescollege.ac.uk> wrote in message
news:1357b958.0308070643.2f4488d4@posting.google.c om...

> This may be true to *you* as a VB programmer, but programmers familiar
> with C# find the code easy to read.
>
> In the same way, I find reading VB similar to wading through treacle.
> But I'm sure it makes perfect sense to you.
>
> The agument that "I can't read C#, therefore C# is difficult to read."
> is like saying "I can't speak French, therefore French is difficult to
> speak."
>
> Subjectively true, objectively facile.
>
> Still waiting to here about the productivity comparison. Should I do
> the keystroke analysis??? grin.
>
> John
>
>
> "Steve C. Orr, MCSD" <Steve@Orr.net> wrote in message

news:<uZlO2vKXDHA.1640@TK2MSFTNGP10.phx.gbl>...

> > As discussed already, VS.NET automatically adjusts the case of your

VB.NET

> > variables so that they all match. Therefore your point is again moot.
> > Also, because VB.NET uses real words it is far more readable than C#.

Even

> > many C# programmers would likely agree with that. C#'s syntax strength

is

> > it's brevity, not readability.

[Steve C. Orr, MCSD]

I suppose if you assume we're all using notepad then your argument holds
water.
But I'm a real programmer that uses real programming tools because that's
what makes sense.
That doesn't make me lazy, it makes me efficient.

--
I hope this helps,
Steve C. Orr, MCSD
[url]http://Steve.Orr.net[/url]



"John Kraft" <jhkraft@ilstu.edu> wrote in message
news:bgu3fb$je3$1@malachite.ilstu.edu...

> Steve C. Orr, MCSD wrote:

> > It's not "incorrect" to mix case in VB.NET so your point is moot.
> > Furthermore, we're not expecting "somebody else" to clean up after us.

>
> Actually you are. You are expecting the environment to clean up after
> you.
>
> I don't think that having the environment do things for you is a bad
> thing. If it helps you to write code more quickly, I think that is a
> good thing.
>
> Complaining that C derived languages are bad, or worse than VB, because
> the environment will not do things for you is simply laziness. Those
> people using the excuse that the environment won't do things for them as
> an excuse to criticize the language are only lying to themselves.
>

> > We're expecting the computer (VS.NET specifically) to assist us with

minor

> > details that are unimportant to the logic of the program. Computers

exist

> > to do things for us. If you don't like that then I don't see why you

use

> > computers at all. All day long I write programs that do things for

other

> > people. Microsoft programmers put a lot of effort into creating VS.NET

so

> > it would do things like this for us and make our jobs easier. Are you
> > suggesting we throw away their efforts and do things manually? That

seems

> > like a waste of time and money.
> >

> Definately not. I happen to love VS... for the most part. But writing
> code in VB.NET has definately made me become a lazier programmer.
>
> I think if you want to compare languages, you shoud compare them on the
> languages themselves... not the environment.
>
> John
>