Slashdot Mirror


Coding Standards for C#?

infinite9 asks: "I've been given the task of writing the coding standards for my corporation. I've been in IT for 12 years, so many things are obvious. Recently though, my employer has standardized on C# and .NET, and since I'm new to the technology (isn't everyone?) I'm not sure what to include. I've included a paragraph about signing assemblies with a standard key pair as well as a few other odds and ends. Apart from the obvious statements that apply to any language like good comments, good variable names, and maintainable code, can anyone suggest other C#/.NET related things that I should include?"

1 of 82 comments (clear)

  1. A few perls of wisdom by Michael.Forman · · Score: 0, Offtopic

    Coding standards:
    • No & in function call unless necessary.

    • Split long lines using hard return; try to respect the 72th column margin (this is kind of a soft limit).

    • Scripts should use strict, and run -w. Documentation should come in .pod format, documentation about script internals should be in comments.

    • Refer to the Lire::Program manpage for more details.

    Another word of advice, "C#" is a bad name for your perl script. I hear there's already something named that.

    Michael.
    --
    Linux : Mac :: VW : Mercedes