Focus on Microsoft Technologies - Tutorials, Articles, Code Samples.

Monday, September 11, 2006

.NET Class members and suggested Order

.NET Class members and suggested Order

The most common definition states that a class is a template for an object. Suppose that someone builds a paper pattern for a shirt. All the shirts done with the same paper pattern will be identical (same design, size, etc.). In this sample, the paper pattern is the class and the shirt is the object. To build the same exact shirt over and over, you need the paper pattern as a template. Another great example are house plans and blueprints. The plans and blueprints define the number of rooms, the size of the kitchen, the number of floors, and more. In this real world sample, the house plans and blueprints are the class and the house is the object. In OOP you program a class as a template for a specific object or groups ob objects that will always have the same features.

Class members

A class has different members, and developers in Microsoft suggest to program them in the following order:

  • Namespace: The namespace is a keyword that defines a distinctive name or last name for the class. A namespace categorizes and organizes the library (assembly) where the class belongs and avoids collisions with classes that share the same name.

  • Class declaration: Line of code where the class name and type are defined.

  • Fields: Set of variables declared in a class block.

  • Constants: Set of constants declared in a class block.

  • Constructors: A method or group of methods that contains code to initialize the class.

  • Properties: The set of descriptive data of an object.

  • Events: Program responses that get fired after a user or application action.

  • Methods: Set of functions of the class.

  • Destructor: A method that is called when the class is destroyed. In managed code, the Garbage Collector is in charge of destroying objects; however, in some cases developers need to take extra actions when objects are being released, such as freeing handles or deallocating unmanaged objects. In .NET, there is no concept of deterministic destructors. The Garbage Collector will call the Finalize() method at a non-deterministic time while reclaiming memory for the application.

Post a Comment