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

Also, the next version of VB.Net is supposed to have the XML documentation
process built in. Why MS did not allow the tool to work in VB is beyond me.
But, I use XML comments in my VB.Net and extract them with code from source
forge or some where like that. I actually, went and created my own extractor
anyway. I am looking forward to seeing what is built in to the new version.
It would be nice to use the same standard.
 
For the last 20 years I have worked on projects that have had "Auto"
documenting features built into the code. Not XML, but each company had its
own standard. Never much a of a problem in extracting the comments with
support info from any of them.  I'm not sure why XML documentation is the
major point for changing languages. Other than the two of you know C#, are
there programmatic why you want C# instead of VB.Net? 
 
My opinion has been stated here before, and I don't mean to start a flame
war. But, my main problem with C is the Case sensitivity. I never
understood, why after we got rid of paper tape programming that we need to
manually correct case when the computer can do it for us. The only
"advantage" is the use of the same letters with different case for different
variables. Which every C book I have read says not to do that. But, that is
my opinion. When I write code I like to put the declarations in the case
required, then use lower case for all the actually code. That way when the
code capitalizes itself, I know I have the correct spelling (typing was
never a strong point :) ).  I like the idea of using words instead of curly
braces for blocks of code. 
 
You might find after using VB.Net that it is not as bad as most people make
it out to be. I have converted C programmers into Ada programmers in the
past, once the learned that something's are just easier to develop.  They
were dead set against using Ada at the time. After the first project, they
volunteered for the next Ada project.  
 
Oh well, I said to much again. Sorry if I offend anyone. I just don't see a
problem with VB.net.
 
Ken Pinard
 

   _____  

From: Aaron B. Hockley [mailto:ahockley@xxxxxxxxx] 
Sent: Thursday, January 20, 2005 8:51 AM
To: padnug@xxxxxxxxxxxxxxx
Subject: Re: [padnug] VB vs C# is there a auto documenting feature in C#


You might be referencing the XML comments which are supported
out-of-the-box in C# but not VB.  That said, the developer community
has built several tools for VB.NET which add this support, so it's
really a non-issue and shouldn't be the factor that determines which
language you write.

Aaron
-- 
HYPERLINK "http://www.hockley.org"http://www.hockley.org - me, photography,
and such
HYPERLINK "http://www.dogcaught.com/dpack"http://www.dogcaught.com/dpack -
my blog

On Thu, 20 Jan 2005 08:16:20 -0800 (PST), Liz Gee <lizgeee@xxxxxxxxx> 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?


   _____  

Yahoo! Groups Links


*       To visit your group on the web, go to:
HYPERLINK
"http://groups.yahoo.com/group/padnug/"http://groups.yahoo.com/group/padnug/
  

*       To unsubscribe from this group, send an email to:
HYPERLINK
"mailto:padnug-unsubscribe@xxxxxxxxxxxxxxx?subject=Unsubscribe"padnug-unsubs
cribe@xxxxxxxxxxxxxxx
  

*       Your use of Yahoo! Groups is subject to the HYPERLINK
"http://docs.yahoo.com/info/terms/"Yahoo! Terms of Service. 



--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 1/17/05



-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 1/17/05
 


[Non-text portions of this message have been removed]