fxcop

I followed the steps here to create a new custom rule and add it to the ruleset in VSStudio 2013: http://blog.tatham.oddie.com.au/2010/01/06/custom-code-analysis-rules-in-vs2010-and-how-to-make-them-run-in-fxcop-and-vs2008-too/ However, despite all my efforts, the custom rule does not show up in the ruleset file. If I add the rule in the FXCop Editor, it shows up and analyzes the target project correctly. This is the Rule File, which is an embedded resource in the project: <?xml version="1.0" encoding="utf-8" ?> <Rules FriendlyName="PSI Custom FxCop Rules"> <Rule TypeName=

I'm going to analysis two different versions of the same dll with fxcop. I would like to display only the differences between these two reports. Does anyone know if this is possible ? Thanks for your time. Yes, it's possible, but there are no built-in tools available for this. One fairly simple approach would be to use a diff tool to compare the two reports. If the result is too noisy for you, another approach would be to roll your own tool to compare the XML of the two reports. Are you using UI or the command line? With the command line tool, you have a number of options. One of them is to

I want to create an FxRule that applies a method, only if the method gets called from a specific class. NOTE: I don't want to just apply a rule to a method of a particular class, i want to be able to handle methods calling other methods calling other methods which do the boxing. I'd like to get FxCop to report problems associated with the method that does the boxing. Below is the code i have so far: using System; using System.Linq; using Microsoft.FxCop.Sdk; using System.Collections.Generic; class CheckUpdatableComponents : BaseIntrospectionRule { private string[] MethodsToCheck = new string[]

I want to be able to specify the Code AnalysisRules in commandline MSBuild (for Code Analysis / FXCOP). The project file would have something like this in it: <CodeAnalysisRules>-Microsoft.Globalization#CA1301;-Microsoft.Globalization#CA1302</CodeAnalysisRules> So I would assume that I use something like this: MSBuild.exe /property:RunCodeAnalysis=true /property:CodeAnalysisRules=-Microsoft.Globalization#CA1301 Which works fine, but when I want to add another rule, it does not like the semi colon: MSBuild.exe /property:RunCodeAnalysis=true /property:CodeAnalysisRules=-Microsoft.Globalization

I have the following code in my application: [DllImport("user32.dll")] private static extern int GetWindowLong(IntPtr hwnd, int index); [DllImport("user32.dll")] private static extern int SetWindowLong(IntPtr hwnd, int index, int newStyle); [DllImport("user32.dll")] private static extern bool SetWindowPos(IntPtr hwnd, IntPtr hwndInsertAfter, int x, int y, int width, int height, uint flags); [DllImport("user32.dll")] private static extern IntPtr SendMessage(IntPtr hwnd, uint msg, IntPtr wParam, IntPtr lParam); I am getting the following warning from Code Analysis (FxCop): CA1060 : Microsoft

I have a piece of code which deals with customers stored in database. There is an object Customer , and it has, among other, two properties of type byte[] : one property for password salt, the second one for password hash. Checking the code with FxCop, I see that it complains ( CA1819 , Performance Rules ) that: "Properties that return arrays are prone to code inefficiencies. Consider using a collection or making this a method. See the design guidelines for more information." and suggests: "Change 'Customer.PasswordHash' to return a collection or make it a method." I don't really understand,

public class MultiSomething { } //CA1704:IdentifiersShouldBeSpelledCorrectly When I run Code Analysis, I get an error because the Microsoft does not recognize the word 'Multi' (go figure they use it in IMultiValueConverter ). So, what I did to correct this was to add a CodeAnalysisDictionary.xml file and followed the steps supplied here . However, it doesn't seem to solve the situation, I still get a Code Analysis warning message. To ensure that this isn't a bug with the recognized words section, I added another class and another exception. public class MultiSomething { } //CA1704

I have been reading this question and a few other answers and whilst I get the difference between changing the reference and changing the state of the current instance I'm not certain why this means that I shouldn't mark it readonly. Is this because marking something as readonly tells the compiler something special about the instance and so it is able to then treat it as thread safe when it actually might not be? Presumably there are situations where I don't want the instance to be able to be changed, but don't mind if the state of the instance is changed (singleton maybe. /me prepares for