The related default StyleCop rules are:
using
statements inside namespace
.using
statements alphabetically.System
using
come first (still trying to figure out if that means just using System;
or using System[.*];
).So, my use case:
Debug.Assert(
and intellisense marks it in Red. I hover mouse over Debug
and between using System.Diagnostics;
and System.Diagnostics.Debug
I choose the former. This inserts using System.Diagnostics;
after all other using
statements. It would be nice if VS2010 did not assist me in writing code that won't build due to warnings as errors.How can I make VS2010 smarter? Is there some sort of setting, or does this require a full-fledged add-in of some sort?
With regards to your #1, you can edit the project template items by using the instructions here or here. I've done this for VS 2K8 to make StyleCop and FxCop happy by default, but I haven't gotten around to doing it for 2010 as I find the procedure a bit tedious and there's always a likelihood that a VS service pack could overwrite them.
For instance, I edited the program.cs in the ConsoleApplication template to look like this:
// <copyright file="Program.cs" company="$registeredorganization$">
// Copyright (c) $year$ All Rights Reserved
// </copyright>
// <author></author>
// <email></email>
// <date>$time$</date>
// <summary></summary>
namespace $safeprojectname$
{
using System;
using System.Collections.Generic;
$if$ ($targetframeworkversion$ == 3.5)using System.Linq;
$endif$using System.Text;
/// <summary>
/// Contains the program's entry point.
/// </summary>
internal static class Program
{
/// <summary>
/// The program's entry point.
/// </summary>
/// <param name="args">The command-line arguments.</param>
private static void Main(string[] args)
{
}
}
}
and the assemblyinfo.cs to look like this:
// <copyright file="AssemblyInfo.cs" company="$registeredorganization$">
// Copyright (c) $year$ All Rights Reserved
// </copyright>
// <author></author>
// <email></email>
// <date>$time$</date>
// <summary></summary>
using System;
using System.Reflection;
using System.Runtime.InteropServices;
// General Information about an assembly is controlled through the following
// set of attributes. Change these attribute values to modify the information
// associated with an assembly.
[assembly: AssemblyTitle("$projectname$")]
[assembly: AssemblyDescription("")]
[assembly: AssemblyConfiguration("")]
[assembly: AssemblyCompany("$registeredorganization$")]
[assembly: AssemblyProduct("$projectname$")]
[assembly: AssemblyCopyright("Copyright © $registeredorganization$ $year$")]
[assembly: AssemblyTrademark("")]
[assembly: AssemblyCulture("")]
// Setting ComVisible to false makes the types in this assembly not visible
// to COM components. If you need to access a type in this assembly from
// COM, set the ComVisible attribute to true on that type.
[assembly: ComVisible(false)]
[assembly: CLSCompliant(true)]
// The following GUID is for the ID of the typelib if this project is exposed to COM
[assembly: Guid("$guid1$")]
// Version information for an assembly consists of the following four values:
//
// Major Version
// Minor Version
// Build Number
// Revision
//
// You can specify all the values or you can default the Build and Revision Numbers
// by using the '*' as shown below:
// [assembly: AssemblyVersion("1.0.*")]
[assembly: AssemblyVersion("1.0.0.0")]
[assembly: AssemblyFileVersion("1.0.0.0")]
I've submitted an incident at Microsoft Connect to the effect that their tools' auto-generated code should satisfy StyleCop/FxCop and their coding guidelines documents.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With