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

I think it's important to note that this auto documenting feature is not
really very automatic.

You still have to type every word of the documentation, it just gets
extracted into a document automatically.  And I think this is only useful
for a certain kind of documentation, where you are documenting the methods
and interfaces of your code.  Not for end user documentation.


----- Original Message ----- 
From: "Liz Gee" <lizgeee@xxxxxxxxx>
To: <padnug@xxxxxxxxxxxxxxx>
Sent: Friday, January 21, 2005 4:01 PM
Subject: RE: [padnug] VB vs C# is there a auto documenting feature in C#


> Nick,
>
> Mike and I reviewed all of your responses thusfar, and many thanks!
> We tried to look at it from the Manager's perspective, since he gets the
final vote.
>
> Like I said, he told me when I started in Sept. that VB.Net was a
pre-exisitng condition.  Now that the subject has come up again, (not by my
newbie on the block position)
> This is what we whittled it down to:
>
> Manager will like the XML auto-documenting feature of C# and the Natural
Language readability of VB.Net, show he choose to help (or get stuck with)
debugging the code.
>
> The Curly brace If end if discussion will be helpful.
> The auto CamelCasing and case sensitive issues are a high point.
> Continuity with JavaScript on ASP.Net
>
> Most of these have to do with code mainentance and debugging by a
non-author of the code.
>
> Thanks,
> Liz
>
> Nick Hebb <nick_hebb@xxxxxxxxx> wrote:
> Liz,
>
> Back to your original question - the differences
> between C# and VB.Net.  MS released a white paper on
> this last summer, which can be downloaded from:
>
> http://support.microsoft.com/?kbid=308470
>
> It's not that helpful for your cause, however, unless
> you really need to write unmanaged code or do bit
> fiddling. So, I don't think that you'll be able to
> convince your manager from a technical perspective.
>
> Looking at the problem from your manager's
> perspective:
> 1. Manager knows some VB so is going to feel more
> comfortable with VB.Net.
> 2. Manager doesn't know C#, so managing a project
> written in it may make him/her feel less knowledgable
> about (or in control of) the project.
> 3. A project written in 2 languages is likely to be
> seen as a higher maintenance risk by the manager.
>
> Allaying your manager's concerns on these issues will
> likely get you farther than debating the technical
> merits.
>
> As a last resort, you could take my old college
> buddy's advice on persuasion: "When in doubt, lie.  If
> that doesn't work, lie harder."  Needless to say, he
> works in sales now. ;-)
>
> -Nick
>
>
>
> __________________________________
> Do you Yahoo!?
> Take Yahoo! Mail with you! Get it on your mobile phone.
> http://mobile.yahoo.com/maildemo
>
>
> ---------------------------------
> Yahoo! Groups Links
>
>    To visit your group on the web, go to:
> http://groups.yahoo.com/group/padnug/
>
>    To unsubscribe from this group, send an email to:
> padnug-unsubscribe@xxxxxxxxxxxxxxx
>
>    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>
>
>
> [Non-text portions of this message have been removed]
>
>
>       Yahoo! Groups Sponsor
>             ADVERTISEMENT
>
>
>
>
>
> --------------------------------------------------------------------------
------
> Yahoo! Groups Links
>
>   a.. To visit your group on the web, go to:
>   http://groups.yahoo.com/group/padnug/
>
>   b.. To unsubscribe from this group, send an email to:
>   padnug-unsubscribe@xxxxxxxxxxxxxxx
>
>   c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>
>