.

NET Developers Need to Use Casing over Separators to Indicate Beginning of Each Word
The .NET framework on the basis of which .NET development is done is composed of classes, interfaces and value types. Using this framework, the development procedure turns into quicker along with ASP.NET developer can use system functionality. .NET framework types adhere to common language specification which can handle interoperability between languages. Due to this interoperability, .NET programmer is free select any sort of framework type from any programming language the compiler of which confirms to CLS. .NET framework types stand for base data types and exceptions, contain data structures, perform I/O, gain access to details regarding loaded types and call .NET framework security checks. The framework also provides data access, rich client-side GUI, plus server-controlled client-side GUI. Naming patterns can be used to club associated types into namespaces by .NET developers. This way they can develop and document class libraries. However, there's no effect of this naming scheme upon visibility, member access, inheritance, security or binding. There exists multiple assemblies over the framework that can contain a namespace whereas kinds of multiple namespaces can be covered within a single assembly. An assembly offers the formal structure for versioning, deployment, security, loading, and visibility inside common language runtime. There are specific guidelines available for .NET programmer to create class libraries. Among many guidelines, there is one rule for labeling which is comprised of several conventions. For instance, When an identifier includes numerous words, there shouldn't be any usage of separators such as underscores ("_") or hyphens ("-") in between words by C# .NET developers. In order to advise beginning of each new word, developers should make use of casing over these separators. Since brevity is favored over readability, C# developer ought to select simply readable identifier name which is always preferable to go for readability than brevity. A developer also needs to avoid Hungarian notation which is the practice of including prefix in identifiers to encode some metadata about the parameter, for example the data type of the identifier. C# programmers pick semantically appealing names than language-specific keywords. It is advisable to make use of general common language runtime in comparison to individual name. In order to group types into structure of related feature areas, .NET developers can make use of namespaces. It's advised not to use very deep namespace hierarchies because the user will have to backtrack them and browsing becomes difficult because of this kind of hierarchies. The developers also need to avoid use of numerous namespaces. The same namespaces should support the types of similar cases. As a way to produce common circumstances, it is not necessary to import many namespaces by the users. Based on the guidelines, inside the common namespace advance types in namespace should be inserted and also use Advanced as last identifier in the name. For example, the advanced kinds are in the System.Xml.Serialization.Advanced namespace and generally used types linked to XML serialization come in the System.Xml.Serialization namespace. Global namespace includes types that are not issued a namespace. These kinds are difficult to locate with the use of .NET development tools since they're not really in a feature-specific namespace. Additionally, it is not possible to deal with name crashes in the global namespace.

http://www.tatvasoft.com/