CollectionBase BUG???

[SharpCoderMP]

hi,

does anyone know something about this:
..net documentation says that CollectionBase.RemoveAt(int index) is
virtual method, but when i try to override it i get compiler error:
cannot override inherited member
'System.Collections.CollectionBase.RemoveAt(int)' because it is not
marked virtual, abstract, or override

is this some kind of bug or what?
if this method is not really virtual so what's the point of this class
being abstract? i can override Remove method but cant RemoveAt.

 

[Nicholas Paldino [.NET/C# MVP]]

SharpCoderMP,

The documentation could be wrong. What you should be overriding is the
OnRemove or the OnRemoveComplete method to provide custom actions to perform
on removal.

Hope this helps.

 

[Willy Denoyette [MVP]]

In my experience, product feedback doesn't care about v1.x issues, on the
other hand all issues with documentation I reported through the feedback
link on the page where corrected within a few weeks, it's easy to do you
don't have to type that much you don't have to refer to some ugly url, the
reference to their internal document system is automatically inserted in the
mail subject (ex. - Documentation Feedback (v1.1):
systemcollectionscollectionbase_2.rtf, RemoveAt Method), more you get a
personal reply when it's done, I suggest you try it before you suggest we
shouldn't bother with this.

Willy.

SharpCoderMP,

Don't bother with that. Use the MSDN Product Feedback Center:

http://lab.msdn.microsoft.com/productfeedback/default.aspx

This is input directly into the bug database at MS, so you can be
assured that it will be documented somewhere (whether or not they fix it,
who knows).


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Agreed, it's frustrating that such errors still exists 4 years after
.NET was released, guess we are just to lazy to click the "Send comments
on this topic" at the bottom of the offending page when we encounter
such mistakes.

ahem... you know... through that last 2,5 years of coding in c# i never
looked down at the footer in documentation ;] despite lunching sdk
documentation every day... i think i'll just click "Send comments on this
topic." and write a few lines
boy - i didn't knew it even existed ;p

 

[SharpCoderMP]

don't worry. i didn't felt insulted. i was just laughing on myself
when i realised that tere is that feedback link in documentation
after all i was looking at it for over two years.

Agreed, it's frustrating that such errors still exists 4 years after .NET
was released, guess we are just to lazy to click the "Send comments on
this topic" at the bottom of the offending page when we encounter such
mistakes.

ahem... you know... through that last 2,5 years of coding in c# i never
looked down at the footer in documentation ;] despite lunching sdk
documentation every day... i think i'll just click "Send comments on this
topic." and write a few lines
boy - i didn't knew it even existed ;p

Hmmm, I said "we are just too lazy" I didn't mean to say YOU are, sorry if
you feel insulted it was by no means my intention.
Note I did clicked the link several times, you'll get a reply from MS when
they correct the MSDN library, so please consult the online msdn docs. when
in doubt.

Willy.