C# Coding Standards and Guidelines: Comments
1. All source code must include the following comments at the very top:
/********************************************************
*Author:
*Date:
*Description:
*Revision:
********************************************************/
2. All comments should be written in English(like in U.S. English).
3. Comments lines should begin with // indented at the same level as the code they are documenting.
4. Do not use /* … */ blocks for comments.
C# Coding Standards and Guidelines: Coding Practices
1. Use meaningful namespace such as the product name or the company name.
2. Avoid fully qualified type names. Use the using statement instead.
3. Avoid putting a using statement inside a namespace.
4. Group all framework namespaces together and put custom or third-party namespaces underneath.
C# Coding Standards and Guidelines: Naming Conversions and Style
1) Use Pascal casing for type and method and constants.
public class SomeClass
{
const int DefaultSize= 100;
public SomeMethod ()
{}
}
Types of Smart Clients Applications
Smart clients vary greatly in design and implementation, both in application requirements and in the number of scenarios and environments in which they can be used. Smart clients therefore can take many different forms and styles. These forms can be divided into three broad categories according to the platform that the smart client application is targeting:
Smart Client – figure out the design challenges and the solutions.
Smart clients are easily deployed and managed client applications that provide an adaptive, responsive and rich interactive experience by leveraging local resources and intelligently connecting to distributed data sources
To fully understand how smart clients combine the benefits of rich clients and thin clients, it is useful to examine the history and underlying principles behind the rich and thin client application models, and review some of the advantages and disadvantages associated with each.
