Code Practices, Microsoft Reliability CA2000 Help...

Question

4.00/5 (1 vote)

See more:

I have the following piece of code, just for reference, and im facing the problem that upon running the code Analysis tool i get the error CA200

CA2000 : Microsoft.Reliability : In method , call System.IDisposable.Dispose on object 'newCol' before all references to it are out of scope.

VB

Dim newCol As New ColumnHeader
newCol.TextAlign = 'whatever value
newCol.Text = 'whatever value
newCol.Tag = 'whatever value
newCol.Width = 'whatever value

ListView1.Columns.Add(newCol)

And i was wondering to to deal with this, or similar situations, that i can not use newcol.Dispose() after adding it to the ListView, for obvious reasons, nor i can use the using statements.

What is the best code practice for this? what I'm missing?

Posted 10-May-11 12:13pm

creizlein

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Pete O'Hanlon · Accepted Answer · 2011-05-10T12:52:00

The important thing to understand is that these warnings are, just that, warnings. They don't cater for all cases, and can be too broad brush at times because they are looking in your code for the case to be handled, not something that may be 30 levels of indirection away. In this case, disposal of the listview should internally manage the disposal of all resources allocated by the listview framework.

If I were you, I'd probably suppress this message with the SuppressMessage attribute.