Question

There is not much easy-to-find information regarding custom code analysis rules for Visual Studio 2010. Although this is what I have found in regards to my question...

在上,关于《守则》的图书馆。这表明如何部署海关编码分析规则图书馆,该图书馆利用一套设施项目将图书馆的达格·哈马舍尔德图书馆移至。 Program files Folder ->Microsoftudio 10.0 -> Team Tool -> Static Analysis Tool -> FxCop -> Rules。

此外,http://blogs.msdn.com/b/codeanalysis/archive/03/26/how-to-write-custom-static-code-analysis-rules-and-integrate-them-into-technology-studio-2010.aspx”rel=“noreferer”/blog post by Du Kamstra <>a> 还建议将图书馆的剪辑拷贝复制到%Program 文档s%Microsoftosphere 10.0Team TechnologiesStatic Analysis ToolFxCop Rules。

我倾向于避免在这样一个全球地点坚持DLs。我想让DL与我的视觉演播室解决办法相对照,这样,当我更新DLL,加上一些习惯代码分析规则的改动,我无需采取额外步骤,使DLL的依赖性得到更新。

我的一个完美解决办法是,我的习惯*.ruleset<>/strong>档案了解通往DLL的相对途径,但我这样做是失败的。

Any suggestions?

Answer 1

In your .ruleset file, you should be able to add relative paths to the custom rule DLLs. e.g.:

<?xml version="1.0" encoding="utf-8"?>
<RuleSet Name="Sample" Description="Sample ruleset" ToolsVersion="10.0">
  <RuleHintPaths>
    <Path>..ToolsFxCopSomeRules.dll</Path>
    <Path>..ToolsFxCopSomeOtherRules.dll</Path>
  </RuleHintPaths>
  ...
</RuleSet>

Answer 2

I found even the correct project-relative relative path (provided as Nicole s answer) to my custom rules assembly did not cause my rules to appear in the ruleset editor, while an absolute path to the same assembly did make the rules show up. When I enabled the rules and then changed the path back to a relative path, the rules remain in the editor and are run during source analysis. If I uncheck the rules with a relative path specified, the rules disappear - this seems like a bug in the rules editor.

So, if your rules do not seem to appear when specifying a relative path, try using an absolute one, enabling the rules, and then switching back to a relative path (relative to the project location per @Raithlin).

Answer 3

这个问题似乎也影响到2013年《联邦调查》。我发现,人工进入相对规则组(和)。当我使用演播室规则设计师时,该大会的规则将产生这些规则。规则也将得到遵守。

So an operational CustomRules.ruleset could look like this, where SR1000 is a rule from SomeRules.dll and SOR1000 is from SomeOtherRules.dll. Note that the tools version is 12.0 for Visual Studio 2013.

<?xml version="1.0" encoding="utf-8"?>
<RuleSet Name="Sample" Description="Sample ruleset" ToolsVersion="12.0">
  <RuleHintPaths>
    <Path>..ToolsFxCopSomeRules.dll</Path>
    <Path>..ToolsFxCopSomeOtherRules.dll</Path>
  </RuleHintPaths>
  <Rules AnalyzerId="Microsoft.Analyzers.ManagedCodeAnalysis" RuleNamespace="Microsoft.Rules.Managed">
    <Rule Id="SR1000" Action="Error" />
    <Rule Id="SOR1000" Action="Warning" />
    <!-- etc. -->
  </Rules>
</RuleSet>

Note that you can easily include standard Microsoft rules by adding includes like this to RuleSet:

<Include Path="minimumrecommendedrules.ruleset" Action="Default" />

Answer 4

I am using Visual Studio C# 2015 with Update 2. My custom rules do not show up in the ruleset editor of Visual Studio 2015. However when i run the CodeAnalysis, violations appear if there are any. My RuleHintPath looks like this and is relative to the location of the ruleset file:

<RuleHintPaths>
  <Path>..Rules</Path>
</RuleHintPaths>

因此,由于发现了这些侵权行为,事实上,DLLs规则是按既定的相对路线确定的。为什么规则没有在规则编辑中显示,这是问题。因此,我假定编辑的 b。

友情链接