Re: VB vs C# is there a auto documenting feature in C#

Not sure if you realized the religous war this would start ;)

The languages in .NET generate pretty much the same code and both can
be used to build just about anything, so as far as the output, there
is no reason for one over another.

There are a few features on both side of the fence that might draw a
person one way or another, but I think the true choice of which to use
comes down to productivity and who will be own/maintain the code.

You are a temp and this if work done for hire where others will be
responsible to maintain or update the code and they happen to be more
comfortable with VB.NET, then there is not a lot you can do.  Such as
you mention your manager knows some VB but not C#, then it matters who
will be spending time with the code. 

If it happens that you and the other developer who desires this in C#
will be the ones mostly working with the code, now and in the future
and you are more comfortable with C# than VB.NET, you can push the
idea that you will have greater productivity with C# than you would
with VB.NET (this only due to what skills one happens to have the most
experience with).  I know that if I would have to do a VB.NET
application, you can about double or triple the time to develop the
applciation since I come from an almost 20 year background of
C/C++/C#, and to me VB is a pain to read and debug, while all those
curly braces and semicolons I have loved for years are much more
readible TO ME.

So, in short, with .NET it does not matter.  With VS.NET 2005 you will
be able to combine C#/VB.NET all in the same assembly so a program
does not really have to be one way or another.  From a code point of
view, I do not feel there really is any reason to choose one over
another, it is all a matter of taste and productivity.

You can also look into C#->VB converters and build your inital code in
C# and then translate for the end project.

Rocky Moore
www.RockyMoore.com


--- In padnug@xxxxxxxxxxxxxxx, Liz Gee <lizgeee@xxxx> wrote:
> All the same pCode, but is there any reason for selecting VB or C#
when starting a new project?
> I thought there was some auto documenting feature in C# that is not
in VB.
> 
> Started this new job in Sept.  Manager wants it in VB.Net.  Tried to
tell him reasons for going
> C#, but didn't push it.  Now the other developer of 4 yrs here wants
to push C#, and we are
> supposed to come up with a justification.
> 
> SCENARIO
> Manager knows a bit of VB.  Manager + third guy are old COBOL
programmers.
> Mike and I are to write the bulk of the code, and all the code for
the first year.
> 
> Any ideas for justifying going C# or VB.Net?
> 
> Thanks in Advance,
> 
> =====
> Elizabeth Gee
> Information Architect
> http://www.nwtd.com