Browse by Tags

All Tags » FxCop (RSS)

Breaking changes to the String class

You may have already read Justin Van Patten's post about the upcoming breaking changes to the String class for .NET 4.0 . This change will affect the behavior of the String.StartsWith , String. EndsWith , String. IndexOf and String. LastIndexOf methods...
Posted by David Kean | 4 comment(s)
Filed under: , ,

New for Visual Studio 2008 SP1 and FxCop 1.36 – Multi-targeting rule

Back in October of last year, Krzysztof Cwalina talked about the multi-targeting changes in Visual Studio 2008 and .NET 3.5. He mentioned the limitations in its design that could cause an application that explicitly targets .NET Framework 2.0 and .NET...
Posted by David Kean | 21 comment(s)
Filed under:

New for FxCop 1.36 - Privates and internals are grayed out in the tree

One of the small, but rather useful changes we made in 1.36 was to gray out privates and internals in the Targets tree. This makes it quick and easy to see the public API for a particular assembly. This is similar to the feature already available in ...
Posted by David Kean | with no comments
Filed under:

FxCop 1.36 Released!

After what has to be the longest beta period for a product (after Gmail) - we've finally released the final version of FxCop 1.36 . I've talked in the past about some the improvements in this release, including: 200+ bug fixes that reduce noise...
Posted by David Kean | 9 comment(s)
Filed under: ,

FxCop has a cousin and its name is ‘StyleCop’

For the past couple of years, I spent considerable time saying the same statement over and over again in forums, emails and blog posts; ‘unfortunately, as FxCop runs over compiled binaries, it cannot analyze source-based constructs, such as whitespace...
Posted by David Kean | with no comments
Filed under: , ,

Reference resolutions changes in Code Analysis and FxCop – Part 2

Previously , I mentioned the reference resolution changes that were made in Code Analysis for 2008 and FxCop 1.36. Unfortunately, not long after we shipped Visual Studio 2008, we found an uncommon scenario in which the strong name matching prevented Code...
Posted by David Kean | with no comments
Filed under: ,

Reference resolution changes in Code Analysis and FxCop – Part 1

Another thing that we changed in Visual Studio 2008 Code Analysis and FxCop 1.36 , was the way we resolved and located references. These changes came down to two distinct behavior changes: Strong names of references must now match. Assemblies must now...
Posted by David Kean | 4 comment(s)
Filed under:

FxCop now ships with the spell checker libraries

One thing that we changed in FxCop 1.36 , is that it now ships with the spell checker libraries out-of-the-box. This means that you no longer need to install Office on your development and build machine boxes to get the spelling and compound word rules...
Posted by David Kean | 4 comment(s)
Filed under: