A read-only field that represents a pointer or handle that has been initialized to zero.
Assembly: mscorlib (in mscorlib.dll)
The value of this field is not equivalent to nullptr. Use this field to efficiently determine whether an instance of IntPtr has been set to a value other than zero.
For example, assume the variable, ip, is an instance of IntPtr. You can determine if it has been set by comparing it to the value returned by a constructor, for example: " if ip != new IntPtr(0)... ". However, invoking a constructor to get an unintialized pointer is inefficient. It is better to code either " if ip != IntPtr.Zero... ", or " if !IntPtr.Zero.Equals(ip)... ".
When calling the Windows API from managed code, you can pass instead of null if an argument is expected to be either a pointer or a null. For example, the following call to the Windows CreateFile function supplies for the pSecurityAttributes and hTemplateFile argument values.
Although is equivalent to null for Windows API functions with parameters or return values that can be either pointers or null, is not equivalent to nullptr. Passing nullptr to the IntPtr.Zero.Equals method always returns false.
You can also test for a null return value from Windows API function calls that return either a pointer or a null by comparing the returned value with . For example, the call to the GetWindow function in the following example tries to retrieve the handle of a non-existent window. If it were called from unmanaged code, the function would return null, but when it is called from managed code, it returns .
Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.