24 out of 38 rated this helpful - Rate this topic

Object Class

Supports all classes in the .NET Framework class hierarchy and provides low-level services to derived classes. This is the ultimate base class of all classes in the .NET Framework; it is the root of the type hierarchy.

System.Object
  All classes, structures, enumerations, and delegates.

Namespace:  System
Assembly:  mscorlib (in mscorlib.dll)
[SerializableAttribute]
[ClassInterfaceAttribute(ClassInterfaceType.AutoDual)]
[ComVisibleAttribute(true)]
public class Object

The Object type exposes the following members.

  Name Description
Public method Supported by the XNA Framework Supported by Portable Class Library Object Initializes a new instance of the Object class.
Top
  Name Description
Public method Supported by the XNA Framework Supported by Portable Class Library Equals(Object) Determines whether the specified Object is equal to the current Object.
Public method Static member Supported by the XNA Framework Supported by Portable Class Library Equals(Object, Object) Determines whether the specified object instances are considered equal.
Protected method Supported by the XNA Framework Supported by Portable Class Library Finalize Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.
Public method Supported by the XNA Framework Supported by Portable Class Library GetHashCode Serves as a hash function for a particular type.
Public method Supported by the XNA Framework Supported by Portable Class Library GetType Gets the Type of the current instance.
Protected method Supported by the XNA Framework Supported by Portable Class Library MemberwiseClone Creates a shallow copy of the current Object.
Public method Static member Supported by the XNA Framework Supported by Portable Class Library ReferenceEquals Determines whether the specified Object instances are the same instance.
Public method Supported by the XNA Framework Supported by Portable Class Library ToString Returns a string that represents the current object.
Top

Languages typically do not require a class to declare inheritance from Object because the inheritance is implicit.

Because all classes in the .NET Framework are derived from Object, every method defined in the Object class is available in all objects in the system. Derived classes can and do override some of these methods, including:

  • Equals - Supports comparisons between objects.

  • Finalize - Performs cleanup operations before an object is automatically reclaimed.

  • GetHashCode - Generates a number corresponding to the value of the object to support the use of a hash table.

  • ToString - Manufactures a human-readable text string that describes an instance of the class.

Performance Considerations

If you are designing a class, such as a collection, that must handle any type of object, you can create class members that accept instances of the Object class. However, the process of boxing and unboxing a type carries a performance cost. If you know your new class will frequently handle certain value types you can use one of two tactics to minimize the cost of boxing.

  • One tactic is to create a general method that accepts an Object type, and a set of type-specific method overloads that accept each value type you expect your class to frequently handle. If a type-specific method exists that accepts the calling parameter type, no boxing occurs and the type-specific method is invoked. If there is no method argument that matches the calling parameter type, the parameter is boxed and the general method is invoked.

  • The other tactic is to design your class and its methods to use generics. The common language runtime creates a closed generic type when you create an instance of your class and specify a generic type argument. The generic method is type-specific and can be invoked without boxing the calling parameter.

Although it is sometimes necessary to develop general purpose classes that accept and return Object types, you can improve performance by also providing a type-specific class to handle a frequently used type. For example, providing a class that is specific to setting and getting Boolean values eliminates the cost of boxing and unboxing Boolean values.

The following example defines a Point type derived from the Object class and overrides many of the virtual methods of the Object class. In addition, the example shows how to call many of the static and instance methods of the Object class.


using System;

// The Point class is derived from System.Object.
class Point 
{
    public int x, y;

    public Point(int x, int y) 
    {
        this.x = x;
        this.y = y;
    }

    public override bool Equals(object obj) 
    {
        // If this and obj do not refer to the same type, then they are not equal.
        if (obj.GetType() != this.GetType()) return false;

        // Return true if  x and y fields match.
        Point other = (Point) obj;
        return (this.x == other.x) && (this.y == other.y);
    }

    // Return the XOR of the x and y fields.
    public override int GetHashCode() 
    {
        return x ^ y;
    }

    // Return the point's value as a string.
    public override String ToString() 
    {
        return String.Format("({0}, {1})", x, y);
    }

    // Return a copy of this point object by making a simple field copy.
    public Point Copy() 
    {
        return (Point) this.MemberwiseClone();
    }
}

public sealed class App {
    static void Main() 
    {
        // Construct a Point object.
        Point p1 = new Point(1,2);

        // Make another Point object that is a copy of the first.
        Point p2 = p1.Copy();

        // Make another variable that references the first Point object.
        Point p3 = p1;

        // The line below displays false because p1 and p2 refer to two different objects.
        Console.WriteLine(Object.ReferenceEquals(p1, p2));

        // The line below displays true because p1 and p2 refer to two different objects that have the same value.
        Console.WriteLine(Object.Equals(p1, p2));

        // The line below displays true because p1 and p3 refer to one object.
        Console.WriteLine(Object.ReferenceEquals(p1, p3));

        // The line below displays: p1's value is: (1, 2)
        Console.WriteLine("p1's value is: {0}", p1.ToString());
    }
}

// This code example produces the following output:
//
// False
// True
// True
// p1's value is: (1, 2)
//


.NET Framework

Supported in: 4, 3.5, 3.0, 2.0, 1.1, 1.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Portable Class Library

Supported in: Portable Class Library

Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows XP SP2 x64 Edition, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Public static (Shared in Visual Basic) members of this type are thread safe. Instance members are not guaranteed to be thread-safe.

Did you find this helpful?
(1500 characters remaining)
Community Content Add
Annotations FAQ
A potentially useful addition: MemberwiseEquals
It would be nice to have a function called MemberwiseEquals that works similar to the existing MemberwiseClone, but does a shallow equality comparison instead. Many classes that override the Equals function only need to compare their type and the values of all fields. A built-in MemberwiseEquals would simplify the code for the Point example like this:

    public override bool Equals(object obj)
    {
        return this.MemberwiseEquals(obj);
    }

Of course, MemberwiseEquals would return false if the type of 'obj' is not the same as the type of 'this'. And it would use the Equals method from each field to compare it with the corresponding field of the other instance.
Test for equality of Objects rintu_i
$0$0 $0$0 $0 $0 $0$0 I wish to express my opinion about equality of Objects.$0 $0 $01. Objects created using Shallow copy or Deep Copy are not equal to the original Object because the hash codes are different. $0 $0When the Hash codes are different only value equality may exist.$0 $0In the example shown above,$0 $0$0 $0 $0Dim p2 As point = p1.Copy( )................ produces a shallow copy with a different hash code. Therefore p2 is not equal to p1$0 $0Dim p3 As point = p1 ............ produces a pointer to the p1 object. Therefore it has the same hash value. Both reference and value equality exist.$0 $0$0 $0 $0Kindly comment about these views.$0 $0$0 $0 $0Rohan Thalagala ---janneny$0
您好,我在努力恢复,8月15日我的电脑全部被摧毁,硬盘坏掉,好不容易建立好的系统又付之东流,我换了所有硬盘.那可是我日夜工作的成果.我在努力恢复.