More Information: https://flevy.com/browse/business-document/microsoft-net-code-guidelines-5049 Enterprise architecture is the process by which organizations standardize and organize IT infrastructure to align with business goals. Enterprise architecture (EA) is the practice of analysing, designing, planning and implementing enterprise analysis to successfully execute on business strategies. EA helps businesses structure IT projects and policies to achieve desired business results and to stay on top of industry trends and disruptions using architecture principles and practices, a process also known as enterprise architectural planning (EAP). EA is guided by the organization's business requirements -- it helps lay out how information, business and technology flow together. This has become a priority for businesses that are trying to keep up with new technologies such as the cloud, IoT, machine learning and other emerging trends that will prompt digital transformation. The process is driven by a "comprehensive picture of an entire enterprise from the perspectives of owner, designer and builder." Unlike other frameworks, it doesn't include a formal documentation structure; instead, it's intended to offer a more holistic view of the enterprise. This document is the work of Adaptive US Inc. It is the World's most innovative business analysis solutions organization which has successfully conducted 300+ BA workshops and has served 200+ top-notch clients including Wells-Fargo Bank, Credit Suisse, HP, CGI, AXA, AkzoNobel, Ness, Unisys, etc. We are proud to have a 100% key client retention rate. Got a question about this presentation? Email us at support@flevy.com.

1. Microsoft.net Coding Guidelines

2. Microsoft.net Coding Guidelines
Page 4 of 9
public class Foo
{
int bar;
public int Bar
{
get { return bar; }
set { bar = value; }
}
}
It is suggested that all control structures (if, while, for, etc.) use braces, but it is not required.
2.4 Commenting
Comments should be used to describe intention, algorithmic overview, and/or logical flow. It would be ideal, if
from reading the comments alone, someone other than the author could understand a function’s intended behavior
and general operation. While there are no minimum comment requirements and certainly some very small routines
need no commenting at all, it is hoped that most routines will have comments reflecting the programmer’s intent and
approach.
2.4.1 Copyright notice
Each file should start with a copyright notice. To avoid errors in doc comment builds, you don’t want to use triple-
slash doc comments, but using XML makes the comments easy to replace in the future. Final text will vary by
product (you should contact legal for the exact text), but should be similar to:
//-----------------------------------------------------------------------
// <copyright file="ContainerControl.cs" company="Microsoft">
// Copyright (c) Microsoft Corporation. All rights reserved.
// </copyright>
//-----------------------------------------------------------------------
1.1.1 2.4.2 Documentation Comments
All methods should use XML doc comments. For internal dev comments, the <devdoc> tag should be used.
public class Foo
{
/// <summary>Public stuff about the method</summary>
/// <param name=”bar”>What a neat parameter!</param>
/// <devdoc>Cool internal stuff!</devdoc>
///
public void MyMethod(int bar) { … }
}
However, it is common that you would want to move the XML documentation to an external file – for that, use the
<include> tag.
This document is a partial preview. Full document download can be found on Flevy:
https://flevy.com/browse/document/microsoft-net-code-guidelines-5049

3. Microsoft.net Coding Guidelines
Page 7 of 9
[SuppressUnmanagedCode]
class SafeNativeMethods
{
private SafeNativeMethods() {}
[DllImport(“user32”)]
internal static extern void MessageBox(string text);
}
All interop classes must be private, and all methods must be internal. In addition a private constructor should be
provided to prevent instantiation.
2.8 File Organization
• Source files should contain only one public type, although multiple internal classes are allowed
• Source files should be given the name of the public class in the file
• Directory names should follow the namespace for the class
For example, I would expect to find the public class “System.Windows.Forms.Control” in
“SystemWindowsFormsControl.cs”…
• Classes member should be alphabetized, and grouped into sections (Fields, Constructors, Properties,
Events, Methods, Private interface implementations, Nested types)
• Using statements should be inside the namespace declaration.
namespace MyNamespace
{
using System;
public class MyClass : IFoo
{
// fields
int foo;
// constructors
public MyClass() { … }
// properties
public int Foo { get { … } set { … } }
// events
public event EventHandler FooChanged { add { … } remove { … } }
// methods
void DoSomething() { … }
void FindSomethind() { … }
//private interface implementations
void IFoo.DoSomething() { DoSomething(); }
This document is a partial preview. Full document download can be found on Flevy:
https://flevy.com/browse/document/microsoft-net-code-guidelines-5049

4. 1
Flevy (www.flevy.com) is the marketplace
for premium documents. These
documents can range from Business
Frameworks to Financial Models to
PowerPoint Templates.
Flevy was founded under the principle that
companies waste a lot of time and money
recreating the same foundational business
documents. Our vision is for Flevy to
become a comprehensive knowledge base
of business documents. All organizations,
from startups to large enterprises, can use
Flevy— whether it's to jumpstart projects, to
find reference or comparison materials, or
just to learn.
Contact Us
Please contact us with any questions you may have
about our company.
• General Inquiries
support@flevy.com
• Media/PR
press@flevy.com
• Billing
billing@flevy.com