<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Custom Dictionary on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/custom-dictionary/</link><description>Recent content in Custom Dictionary on Marko Apfel</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 02 Jul 2010 11:27:00 +0200</lastBuildDate><atom:link href="http://blog.marko-apfel.de/tags/custom-dictionary/index.xml" rel="self" type="application/rss+xml"/><item><title>Specify a project-specific custom dictionary for FxCop build tasks and Visual Studio Team System static code analysis</title><link>http://blog.marko-apfel.de/posts/specify-a-project-specific-custom-dictionary-for-fxcop-build-tasks-and-visual-studio-team-system-static-code-analysis/</link><pubDate>Fri, 02 Jul 2010 11:27:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/specify-a-project-specific-custom-dictionary-for-fxcop-build-tasks-and-visual-studio-team-system-static-code-analysis/</guid><description>&lt;p&gt;Using a project-specific custom dictionary for &lt;em&gt;FxCop&lt;/em&gt; and &lt;em&gt;FxCop build tasks&lt;/em&gt; is very simple. The &lt;em&gt;FxCopCmd&lt;/em&gt; call in the &lt;em&gt;FxCop&lt;/em&gt;-target offers the parameter &lt;code&gt;/dictionary:&amp;lt;DictionaryName&amp;gt;&lt;/code&gt; for that.&lt;/p&gt;
&lt;p&gt;But for &lt;em&gt;Visual Studio&lt;/em&gt; a little bit more steps are needed. And these steps must me gone for all projects.&lt;/p&gt;</description></item><item><title>Specify a custom dictionary for FxCop and Visual Studio source analysis</title><link>http://blog.marko-apfel.de/posts/specify-a-custom-dictionary-for-fxcop-and-visual-studio-source-analysis/</link><pubDate>Tue, 11 May 2010 17:46:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/specify-a-custom-dictionary-for-fxcop-and-visual-studio-source-analysis/</guid><description>&lt;p&gt;Renaming the default custom dictionary from &lt;code&gt;CustomDictionary.xml&lt;/code&gt; to an other name – for instance &lt;code&gt;FxCop.CustomDictionary.xml&lt;/code&gt; needs some additional changes to work in involved applications.&lt;/p&gt;
&lt;h2 id="visual-studio-team-system-code-analysis"&gt;Visual Studio Team System code analysis&lt;/h2&gt;
&lt;p&gt;For Visual Studio Team System code analysis this file should be added as a link to all projects and set to be the Build Action CodeAnalysisDirectory.&lt;/p&gt;</description></item><item><title>Using a custom dictionary in code analysis</title><link>http://blog.marko-apfel.de/posts/using-a-custom-dictionary-in-code-analysis/</link><pubDate>Wed, 11 Nov 2009 09:22:00 +0100</pubDate><guid>http://blog.marko-apfel.de/posts/using-a-custom-dictionary-in-code-analysis/</guid><description>&lt;p&gt;see also &lt;a href="http://blog.marko-apfel.de/posts/working-with-microsoft-fxcop/"&gt;Working with Microsoft FxCop&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;As described in the previous post a custom dictionary could be referenced in a FxCop-call of a target by using the option:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-cmd" data-lang="cmd"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;/dictionary:&lt;span class="p"&gt;&amp;amp;&lt;/span&gt;quot;$(ProjectDir)..\FxCop.CustomDictionary.xml&lt;span class="p"&gt;&amp;amp;&lt;/span&gt;quot;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;But how is it possible to publish this custom dictionary for the Visual Studio integrated code analysis?&lt;/p&gt;</description></item></channel></rss>