VB.NET and FxCop 1.21

I played around with FxCop for the first time today -- very cool app! One thing that is very annoying for VB.NET developers: If you turn on automatic "code reformatting" in VS.NET, the "Set" clause of a Property statement is generated as:

Set(Value As <type>)
End Set

See the problem? The "Value" parameter should be camelCased to conform to Microsoft's .NET Design guidelines. Argh -- I'm notifying Microsoft. Maybe this can be fixed (or configurable) in some future version of VS.NET.

And yes, I know I can exclude the rule, but it's a pre-incident setting. I have to exlude every property set clause in every file in every assembly. I'd prefer Microsoft fix VS.NET to adhere to their own guidelines! :)