Code Analysis on Marko Apfel

Simian counts errors in Jenkins dashboard but shows in details “No violation found”

Thu, 08 Dec 2011 16:46:00 +0100

Problem

Jenkins dashboard shows following simian analysis:

But after clicking one item I get:

Toolset agnostic build server and Silverlight projects

Thu, 10 Nov 2011 22:42:00 +0100

Problem

Normally I try to have my continuous integration as most a possible toolset free to ensure that no local stuff could have an impact to my build.

My Silverlight app references a special compile target in a folder outside my developer tree:

MSB4067: The element beneath element is unrecognized.

Tue, 08 Nov 2011 11:32:00 +0100

Problem

Our global Jenkins continuous integration server throws this error during compile step. My local TeamCity continuous integration server runs fine. What is the difference.

Background

I integrate some static code analysis steps via MSBuild-targets in the csproj files.

Running StyleCop without an installation to empower continuous integration

Mon, 07 Nov 2011 22:32:00 +0100

Problem

A continuous integration server should only have a minimal toolset installed. This ensures that no unwanted libraries could affect the build and other steps.

Clearly that with this slogan also StyleCop should not be installed to the CI server. But we wanna have this analysis as an part of the whole build.

Code Contracts: For unit test a manual rebuild is needed for toggeling “runtime checking”

Sat, 04 Jun 2011 01:19:00 +0200

Toggeling the checkbox “Perform Runtime Contract Checking” lets run the next application start with the new set option. But for unit test an explicit new build will apply the option for the next run.

Installation experiences with NDepend under Win7/64 with restricted user permissions

Mon, 27 Dec 2010 19:10:00 +0100

Today Patrick gives me a new license for his static code analysis tool NDepend for my fresh machine with Win7/64. This platform is new for me, so some things are different to Win XP. Maybe that till yet some of these things are not well enough understandanded from me. So i stepped in some traps.

Searching the new FxCop-Release (10.0)

Mon, 05 Jul 2010 14:45:00 +0200

Today my FxCop-GUI stated, that a new release is available – but the link to this release is broken.

After googling a little bit i realized, that the new release of FxCop ist actually only included in “Windows SDK for Windows 7.1”.

My own set of SuppressMessage-lines

Mon, 05 Jul 2010 10:35:00 +0200

StyleCop issues

inheritedoc-comment

Using <inheritdoc />-comment is not recognized by StyleCop. So this needs a suppression:

// <inheritdoc /> [SuppressMessage( “Microsoft.StyleCop.CSharp.DocumentationRules”, “SA1604:ElementDocumentationMustHaveSummary”, Justification = “InheritDoc”)]

FxCop issues

Too few namespaces

[module: SuppressMessage( “Microsoft.Design”, “CA1020:AvoidNamespacesWithFewTypes”, Scope = “namespace”, Target = “EsriDE.Core.Service.Logging”, Justification = “We want to have this namespace, but do not have enough classes to go in it right now to satisfy the rule.”)]

Specify a project-specific custom dictionary for FxCop build tasks and Visual Studio Team System static code analysis

Fri, 02 Jul 2010 11:27:00 +0200

Using a project-specific custom disctionary for FxCop and FxCop build tasks is very simple. The FxCopCmd call in the FxCop-target offers the parameter /dictionary:<DictionaryName> for that.

But for Visual Studio a little bit more steps are needed. And these steps musst me gone for all projects.

Specify a custom dictionary for FxCop and Visual Studio source analysis

Tue, 11 May 2010 17:46:00 +0200

Renaming the default custom dictionary from CustomDictionary.xml to an other name – for instance FxCop.CustomDictionary.xml needs some additional changes to work in involved applications.

Visual Studio Team System code analysis

For Visual Studio Team System code analysis this file should be added as a link to all projects and setted to be the Build Action CodeAnalysisDirectory.

Visual Studio 2005/2008 Code Analysis Error

Thu, 26 Nov 2009 12:52:00 +0100

After installing VS2005 TE on my machine (which previously runs Visual Studio 2008 TE) all mixed projects (VS2005/VS2008 compatibility with TargetFramework=2.0 and ToolsVersion=2.0 options) thrown an error during compilation:

C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\CodeAnalysis\Microsoft.CodeAnalysis.targets(46,4):
error : In order to perform Code Analysis on managed binaries, MSBuild needs to launch FxCop.
MSBuild is unable to locate the FxCop binaries.
Make sure Visual Studio Team Edition for Software Developers or Visual Studio Team Suite is installed
and run MSBuild from within the "Visual Studio Command Prompt"
or specify the path to FxCop by setting the FXCOPDIR environment variable.

Specifying the FXCOPDIR-variable brings up the next obscure errors.

StyleCop throws documentation warning SA1600 for private elements

Thu, 12 Nov 2009 06:24:00 +0100

if you see the following warnings in your code:

You have two choices:

deactivate the rule but this disables this rule for all documentations – also the wanted
tune the detail settings In the settings editor you see additional options if you select the “Documentation Rules” root node

Installing StyleCop for ReSharper

Thu, 12 Nov 2009 05:58:00 +0100

Installing StyleCop for ReSharper under an administrative account does not activate this ReSharper plugin under my developer account.

A system analysis show, that this plugin is installed under

%userprofile%\Local Settings\Application Data\JetBrains\ReSharper\v4.5\vs9.0\Plugins\Microsoft StyleCop for ReSharper

AgentSmith: suppressing spell checking warnings

Thu, 12 Nov 2009 03:42:00 +0100

If AgentSmith throws a warning that some term is not spelled correctly for this term the spell checking could be suppressed with:

//agentsmith spellcheck disable

...

//agentsmith spellcheck enable

Using a custom dictionary in code analysis

Wed, 11 Nov 2009 09:22:00 +0100

Working with Microsoft FxCop

Wed, 11 Nov 2009 09:06:00 +0100

Run FxCop as a post build event

Since FxCop 1.36 it is possible to include FxCop in a post-build event.

So FxCop runs after compiling in Visual Studio and allows you directly jumping to the warned line.

ReSharper is not available

Mon, 09 Nov 2009 07:23:00 +0100

Today a colleague ask me to help.

On his system all ReSharper menus are grayed out. Also the Visual Studio Add-In Manager does not show this add-in.

He tried:

a new installation: without success,
running with administrative privilegeg: without success,
looking in event- and application-logs: no entries.

After searching a little bit with old buddy google we found this message: Wild World of Visual Studio – Mysterious Component

Visual Studio lists Error: “CA0503 : Additional code analysis warnings or errors cannot be displayed”

Thu, 29 Oct 2009 05:54:00 +0100

This error during compilation annoys me in a legacy project.

Apparently because of performance issues the Visual Studio development team decided to limit the warnings of code analysis to 200 items.

This behaviour could be parameterized under: