Extensible XML documentation?

[Phill. W]

Whilst hammering away cutting VB.Net code, I'm hearing (mostly
from my C#-cutting colleagues) about XML documentation that
can be produced from our .Net projects. Now, I've only scratched
the surface about this (and already worked out that I need an add-in
to do this from VB.Net) I'd like to ask:

Is it possible to extend the output produced?

[In the absence of Java's "Checked Exceptions"] I'd like, if possible,
to add into these documents information about what Exceptions can
be thrown by my code. That way, at least other Developers will have
half an idea of what my code might do to them.

TIA,
Phill W.

Exceptions

 

[CJ Taylor]

I just asked this same questoin yesterday. check out gotdotnet for the VB
Commenter. I started using it this morning, seems pretty decent so far, but
not quite as good as the C# commenter. Which I like more. =)

 

[Tom Spink]

Just you wait for Whidbey ;-)

--
Happy to help,
-- Tom Spink
([email protected])

"Go down with your server"

http://dotnetx.betasafe.com >> On The Mend

Please respond to the newsgroup,
so all can benefit

I just asked this same questoin yesterday. check out gotdotnet for the VB
Commenter. I started using it this morning, seems pretty decent so far, but
not quite as good as the C# commenter. Which I like more. =)

Whilst hammering away cutting VB.Net code, I'm hearing (mostly
from my C#-cutting colleagues) about XML documentation that
can be produced from our .Net projects. Now, I've only scratched
the surface about this (and already worked out that I need an add-in
to do this from VB.Net) I'd like to ask:

Is it possible to extend the output produced?

[In the absence of Java's "Checked Exceptions"] I'd like, if possible,
to add into these documents information about what Exceptions can
be thrown by my code. That way, at least other Developers will have
half an idea of what my code might do to them.

TIA,
Phill W.

Exceptions

 

[CJ Taylor]

See Tom... you can't just throw out a teaser like that and not tell me what
it is. =)

So... what is it?

And whats so special?

-CJ

Just you wait for Whidbey ;-)

--
Happy to help,
-- Tom Spink
([email protected])

"Go down with your server"

http://dotnetx.betasafe.com >> On The Mend

Please respond to the newsgroup,
so all can benefit

I just asked this same questoin yesterday. check out gotdotnet for the VB
Commenter. I started using it this morning, seems pretty decent so far, but
not quite as good as the C# commenter. Which I like more. =)

Whilst hammering away cutting VB.Net code, I'm hearing (mostly
from my C#-cutting colleagues) about XML documentation that
can be produced from our .Net projects. Now, I've only scratched
the surface about this (and already worked out that I need an add-in
to do this from VB.Net) I'd like to ask:

Is it possible to extend the output produced?

[In the absence of Java's "Checked Exceptions"] I'd like, if possible,
to add into these documents information about what Exceptions can
be thrown by my code. That way, at least other Developers will have
half an idea of what my code might do to them.

TIA,
Phill W.

Exceptions

 

[Tom Spink]

Whidbey? The next VS.NET, language enhancements for VB.NET include, Operator
Overloading (yey!) and XML Documentation.

I can't remember where I read this though.

--
Happy to help,
-- Tom Spink
([email protected])

"Go down with your server"

http://dotnetx.betasafe.com >> On The Mend

Please respond to the newsgroup,
so all can benefit

See Tom... you can't just throw out a teaser like that and not tell me what
it is. =)

So... what is it?

And whats so special?

-CJ

Just you wait for Whidbey ;-)

--
Happy to help,
-- Tom Spink
([email protected])

"Go down with your server"

http://dotnetx.betasafe.com >> On The Mend

Please respond to the newsgroup,
so all can benefit

the

VB

Commenter. I started using it this morning, seems pretty decent so

far,
but

not quite as good as the C# commenter. Which I like more. =)


Whilst hammering away cutting VB.Net code, I'm hearing (mostly
from my C#-cutting colleagues) about XML documentation that
can be produced from our .Net projects. Now, I've only scratched
the surface about this (and already worked out that I need an add-in
to do this from VB.Net) I'd like to ask:

Is it possible to extend the output produced?

[In the absence of Java's "Checked Exceptions"] I'd like, if possible,
to add into these documents information about what Exceptions can
be thrown by my code. That way, at least other Developers will have
half an idea of what my code might do to them.

TIA,
Phill W.

Exceptions

 

[Jeremy Cowles]

Whidbey? The next VS.NET, language enhancements for VB.NET include,
Operator

Overloading (yey!) and XML Documentation.

Tom, stop telling lies to the locals; you forgot to take your pills again
didn't you?



~
Jeremy

 

[Herfried K. Wagner [MVP]]

Hello,

See Tom... you can't just throw out a teaser like that and not tell me what
it is. =)

So... what is it?

And whats so special?

http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx

HTH,
Herfried K. Wagner

 

[Herfried K. Wagner [MVP]]

Hello,

Whidbey? The next VS.NET, language enhancements for VB.NET
include, Operator Overloading (yey!) and XML Documentation.

Edit & Continue for VB .NET, generics, ...

;-)))

I can't remember where I read this though.

http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx

HTH,
Herfried K. Wagner

 

[Jeremy Cowles]

Hello,



Edit & Continue for VB .NET, generics, ...

Generics?! Dare I say... <Templates>? In VB? Are you MAD?!



I will seriously explode with happyness if they add Templates(or something
like it) to VB...

~
Jeremy

 

[Herfried K. Wagner [MVP]]

Hello,

Generics?! Dare I say... <Templates>? In VB? Are you MAD?!

Yes. Generics ("templates" in C++ terminology). You can read that in the
article (I posted the link before).

I will seriously explode with happyness if they add Templates
(or something like it) to VB...

I am very happy about that too...

))

Regards,
Herfried K. Wagner

 

[Jay B. Harlow [MVP - Outlook]]

Jeremy,

I will seriously explode with happyness if they add Templates(or something
like it) to VB...

I'm sure Armin & Herfried would join me in wanting to see the video of you
"exploding with happiness". ) (in a good way of course)

Yes: Generics are to .NET as Templates are to C++.

And according to the above mentioned documents we VB.NET gets them!

For details of how they will work see:
http://msdn.microsoft.com/msdnmag/issues/03/09/net/default.aspx

and:
http://msdn.microsoft.com/library/d...l/vbconCProgrammingLanguageFutureFeatures.asp

One of the articles I read I got the impression VB.NET will be both a
producer & consumer of generics...

Hope this helps
Jay

 

[Jay B. Harlow [MVP - Outlook]]

Jerermy
Umm...

it just that when you copy the code base for your
collections 100 times, and then you find a bug in one of them,

Using inheritance you should not be copying base code.

Using CollectionBase or DictionaryBase there should be little code each
specific class needs.

Also there are generators out there that will generate the boiler plate code
that is unique to each collection. Its also not that hard to write your own
generator.

I hope I am taking you too literally!

Jay

 

[Jeremy Cowles]

it just that when you copy the code base for your

Using inheritance you should not be copying base code.

You can't inherit the Item property, or the Add sub, you see because they
require a specific type.

Using CollectionBase or DictionaryBase there should be little code each
specific class needs.

I inherit from CollectionBase, but still, you must rewrite for the specific
types every time.

Also there are generators out there that will generate the boiler plate code
that is unique to each collection. Its also not that hard to write your own
generator.

I have actually created macros for almost everything (notation, classes,
methods, properties, TSQL, stored procs, data conversion, you name it - I
love the macros! It's just like when i used to smoke PCP and code all
night!), and that does ease the pain, but it's the principle of the matter
that eerks me, you know? Maybe I am just a whiner.



~
Jeremy