Typed DataSets

CA1034 - NestedTypesShouldNotBeVisible error on a Typed DataSet
CA2237 - MarkISerializableTypesWithSerializable on a Typed DataSet
Should I not use FxCop on Typed DataSets as they are generated code?

[209 byte] By [Schenz74] at [2007-12-17]

«« VBA source code
»» MSF certification

# 1

Hi Schenz,

What version of FxCop are you using? We have done a lot of work in the last half year to reduce noise on generated code like typed datasets. So if you see any violations like these with recent versions of FxCop, I'd like to know how you generated these typed datasets so we can improve this in the future.

Regards,
Jeffrey

JeffreyvanGogh_MS at 2007-9-9 >

top of Msdn Tech,Visual Studio Team System,Visual Studio Code Analysis and Code Metrics...

# 2

I am using 1.32, and because my database is mySQL I had to build the DataSet Schema manually myself.
I would be happy to provide any code or files you my need to track this down.

Schenz74 at 2007-9-9 >

# 3

I also believe I am getting a CA1823 - AvoidUnusedPrivateFields Message in error.

Schenz74 at 2007-9-9 >

# 4

CA1822 - MarkMethodsAsStatic reported on a Crystal Report.

Schenz74 at 2007-9-9 >

# 5

Hi Schenz,

I just looked at our code, and the noise reduction I was talking about, is in the bits of FxCop that will ship with Visual Studio 2005, but are not in FxCop 1.32. These fixes should eliminate all noise against datasets. They'll be part of our next release on gotdotnet.

Regards,
Jeffrey

JeffreyvanGogh at 2007-9-9 >

# 6

So, roughly, the next release will coincide with Whidbey?

Schenz74 at 2007-9-9 >

# 7

Roughly, yes. I'll post an exact date on the forum here within a week.

MichaelFanning-MS at 2007-9-9 >

Visual Studio Team System

Visual Studio Code Analysis and Code Metrics