What resolutions or warnings need to provide more information?

VSTS Links - 02/07/2007

Team System News — Wed, 07 Feb 2007 17:28:38 GMT

Rob Caron on Visual Studio and Daylight Saving Time Change. Willy-Peter Schaub on What "main" features...

re: What resolutions or warnings need to provide more information?

David M. Kean — Mon, 05 Feb 2007 22:25:14 GMT

Byrant: Thanks for the feedback. We're are definately improving the docs to include better examples and explanations, I'll make sure to put DoNotNestGenericTypesInMemberSignatures on the radar.

re: What resolutions or warnings need to provide more information?

Bryant — Mon, 05 Feb 2007 21:57:52 GMT

The CA1006:DoNotNestGenericTypesInMemberSignatures rule in Microsoft.Design definitely needs help! There isn't even an example of how to fix the problem in the documentation! You might consider checking your current set of rules to make sure that all the violations have appropriate solutions.

Thanks!

Bryant

re: What resolutions or warnings need to provide more information?

Steve Dunn — Mon, 05 Feb 2007 11:33:34 GMT

In Orcase, will analysis be built into the IDE? (I remember someone saying this quite some time ago). If so, it'd be great if the warning/error was 'squiggled' at the appropriate point in the code. The user could then click and have the IDE do the changes!

Cheers,

Steve.

re: What resolutions or warnings need to provide more information?

David M. Kean — Sun, 04 Feb 2007 00:40:00 GMT

Harry: The right-click, disable rule is something that we wanted to do for Orcas, unfortunately, we did not have enough time. Look out for it in future versions.

Bob, Brant: I personally would prefer naming and casing issues to be raised before you build. Imagine raising these issues as you type (you could also see us hooking onto the refactoring tools to help making sure that any consumers get updated with the new name), sort of like the Office spell checker.

re: What resolutions or warnings need to provide more information?

Brant Gurganus — Sat, 03 Feb 2007 22:06:13 GMT

I agree with Bob D. Especially for the usually trivial, repetitive fixes, the ability to automatically fix would be great. Eclipse can automatically fix several things like missing imports and such, and I don't see Visual Studio do this kinds of usually trivial repetitive fixes.

re: What resolutions or warnings need to provide more information?

Bob D — Sat, 03 Feb 2007 20:59:32 GMT

Our team has a large set of .net project and we didn't start using FxCop from the beginning.

Have you ever thought of adding the funtionality to auto-fix these types of errors? Although some errors I wouldn't want FxCop to try to fix, casing errors seem like the type of repetative monotonous task that could benefit from automation. Even if was something like "find/replace" without a "replace all" button so that someone had to verify before it made the fix.

re: What resolutions or warnings need to provide more information?

Bob D — Sat, 03 Feb 2007 20:58:57 GMT

Our team has a large set of .net project and we didn't start using FxCop from the beginning.

re: What resolutions or warnings need to provide more information?

Harry[at]Ardimedia.Com — Sat, 03 Feb 2007 20:21:52 GMT

Great work! I like this kind of fixing things up...

My opinion is that the more information the better. So to give us the hint, why it should be IO, would help.

What also would help, that with a click of a mouse button, I could "disable" certain rules. At the moment I have to search for them...

Keep going ;-) Cheers Harry