Latest Articles: CodingStandards

Coding Standard: C#
Entry Date: Jun 2008	site: Tiobe	Rating:
keywords:Coding Standards;
Article Description: This coding standard for the C# language is mandatory for PMS. The objective of this coding standard is to have a positive effect on: Avoidance of errors/bugs, especially the hard-to-find ones. Maintainability, by promoting some proven design principles. Maintainability, by requiring or recommending a certain unity of style. Performance, by dissuading wasteful practices. Rules and recommendations are given that promote reliability and maintainability.
Comments: Very formal and elaborated document about C# coding standards. Good starting point to setup your coding standards in your company / IT Department.
Click Here To Navigate to the Article
.NET Programming Standards and Naming Conventions
Entry Date: Jun 2008	site: Irritated Vowel	Rating:
keywords:Coding Standards;
Article Description: These are the industry-accepted standard naming conventions for J#, C# and VB.NET programs. For additional information, please see the MSDN help documentation and FX Cop. While individual naming conventions at organizations may vary (Microsoft only suggests conventions for public and protected items), the list below is quickly becoming the de-facto standard in the industry. Please note the absence of Hungarian Notation except in visual controls. These naming standards should find their way into all of your .NET development, including ASP.NET Web applications and .NET Windows Forms applications.
Comments: Learn coding standards by example... It includes a good discussion that tells us why Hungarian notation has been deprecated.
Click Here To Navigate to the Article
Design Guidelines, Managed code and the .NET Framework
Entry Date: Jun 2008	site: Blogs MSDN	Rating:
keywords:Coding Standards;
Article Description: First, read the .NET Framework Design Guidelines. Almost all naming conventions, casing rules, etc., are spelled out in this document. Unlike the Design Guidelines document, you should treat this document as a set of suggested guidelines. These generally do not effect the customer view so they are not required.
Comments: Short and useful guide, good to setup some lite weight standard in your guerrilla development team. Better to use a short subset that having a heavy one that nobdy uses or understand
Click Here To Navigate to the Article
Naming Guidelines
Entry Date: Jun 2008	site: MSDN	Rating:
keywords:Coding Standards;
Article Description: A consistent naming pattern is one of the most important elements of predictability and discoverability in a managed class library. Widespread use and understanding of these naming guidelines should eliminate many of the most common user questions. This topic provides naming guidelines for the .NET Framework types. For each type, you should also take note of some general rules with respect to capitalization styles, case sensitivity and word choice.
Comments: Searching for a standard way of coding? Are you tired of having mixed code... hungarian notation, moder one... Here yoy will find some interesting rules and conventions.
Click Here To Navigate to the Article
Design Guidelines for Class Library Developers
Entry Date: Jun 2008	site: MSDN	Rating:
keywords:Coding Standards;
Article Description: The .NET Framework's managed environment allows developers to improve their programming model to support a wide range of functionality. The goal of the .NET Framework design guidelines is to encourage consistency and predictability in public APIs while enabling Web and cross-language integration. It is strongly recommended that you follow these design guidelines when developing classes and components that extend the .NET Framework. Inconsistent design adversely affects developer productivity. Development tools and add-ins can turn some of these guidelines into de facto prescriptive rules, and reduce the value of nonconforming components. Nonconforming components will function, but not to their full potential.
Comments: If you are looking for standards to make more uniform the code of your company / coders, this can be a good starting point. A good tip... be happy just with a subset of this rules, later on you can go and embrace more and more rules.
Click Here To Navigate to the Article

Page (1) Of 1