stylecop

I am trying to ensure my coding follows correct disposal of objects so I am enforcing these rules as errors. But I am having trouble with this section of code using System; using System.IO; using System.Runtime.Serialization; using System.Xml; class MyClass { public String ToXml() { var objSerializer = new DataContractSerializer(GetType()); var objStream = new MemoryStream(); StreamReader objReader; String strResult; try { // Serialize the object objSerializer.WriteObject(objStream, this); // Move to start of stream to read out contents objStream.Seek(0, SeekOrigin.Begin); objReader = new

Possible Duplicate: Should Usings be inside or outside the namespace sa1200 All using directives must be placed inside the namespace (StyleCop) Is this just for code readibility or is there any actual advantage to doing so? Does it help the GC somehow? It definitely won't help with GC. Here's the discussion about two styles: http://blogs.msdn.com/abhinaba/archive/2006/08/21/709051.aspx http://blogs.msdn.com/abhinaba/archive/2008/07/08/do-namespace-using-directives-affect-assembly-loading.aspx If you have multiple namespaces in your project, you can limit which namespaces are used by each one

SA1124 DoNotUseRegions suggest that region should not be used anywhere. Is it really reasonable? I think region is a way to group relative code together and make large class easy to read, for example, if you generate interface method for a class in vs2008 via context menu, a region will be automatically inserted. I would like to remove this rule while checking code style. May I know your opinions on this rule? This is going to be a personal preference thing. The only thing that matters here is what you and your team prefer . Forget what style cop says, you're the ones reading it, you're the

Not found it in StyleCop Help Manual, on SO and Google so here it is ;) During StyleCop use I have a warning: SA1121 - UseBuiltInTypeAlias - Readability Rules The code uses one of the basic C# types, but does not use the built-in alias for the type. Rather than using the type name or the fully-qualified type name, the built-in aliases for these types should always be used: bool, byte, char, decimal, double, short, int, long, object, sbyte, float, string, ushort, uint, ulong. so String.Empty is wrong (depend on above rules) and string.Empty is good. Why using built-in aliases is better? Can

Has Stylecop superseded FXcop? Which product should we be using with Visual Studio 2008? Stylecop is a style analysis tool that works at the source code level. It exists primarily to provide a single common style that managed projects can use to remain consistent within the larger world of managed software. It makes decisions regarding style primarily to avoid holy wars (after all, style is almost always an inherently subjective thing). I don't think I've ever met someone who liked all of StyleCop's rules, but that's ok . It means that StyleCop is a generally good compromise amongst the vast

I'm using StyleCop. But there a couple of rules I want to ignore, for instance using this. in front of class members. How do I turn off a StyleCop rule. I've looked but can't find how to do it. bdukes In your StyleCop install, there's a Settings.StyleCop file. You can edit this to turn off rules globally. Drag that file onto the Settings Editor executable in that file to edit it. You can also put copies of the settings file into your projects to override the global settings. If you're using Visual Studio integration and not just MSBuild integration, you should be able to get to the settings

I've been doing research on how to enable source analysis for the project I'm working on and plan to use StyleCop. The setup I have is a TFS Server for source control, using TFS Continuous Integration. I want to enable source analysis for CI builds and daily builds run on the build machine, and not only for those run on developers' machines. Here's an article from the documentation of StyleCop that I read on the subject: http://blog.newagesolution.net/2008/07/how-to-use-stylecop-and-msbuild-and.html . It basically modifies the csproj file for the purpose. I've also read other opinions about