[ This article is for Windows Phone 8 developers. If you’re developing for Windows 10, see the latest documentation. ]
Creates a new object or a new instance of a value type, pushing an object reference (type O) onto the evaluation stack.
Assembly: mscorlib (in mscorlib.dll)
The following table lists the instruction's hexadecimal and Microsoft intermediate language (MSIL) assembly format, along with a brief reference summary:
73 < T >
Allocates an uninitialized object or value type and calls the constructor method ctor.
The stack transitional behavior, in sequential order, is:
Arguments arg1 through argn are pushed on the stack in sequence.
Arguments argn through arg1 are popped from the stack and passed to ctor for object creation.
A reference to the new object is pushed onto the stack.
The newobj instruction creates a new object or a new instance of a value type. Ctor is a metadata token (a methodref or methoddef that must be marked as a constructor) that indicates the name, class and signature of the constructor to call.
The newobj instruction allocates a new instance of the class associated with ctor and initializes all the fields in the new instance to 0 (of the proper type) or null references as appropriate. It then calls the constructor ctor with the given arguments along with the newly created instance. After the constructor has been called, the now initialized object reference (type O) is pushed on the stack.
From the constructor's point of view, the uninitialized object is argument 0 and the other arguments passed to newobj follow in order.
All zero-based, one-dimensional arrays are created using Newarr, not newobj. On the other hand, all other arrays (more than one dimension, or one-dimensional but not zero-based) are created using newobj.
Value types are not usually created using newobj. They are usually allocated either as arguments or local variables, using newarr (for zero-based, one-dimensional arrays), or as fields of objects. Once allocated, they are initialized using Initobj. However, the newobj instruction can be used to create a new instance of a value type on the stack, that can then be passed as an argument, stored in a local, and so on.
OutOfMemoryException is thrown if there is insufficient memory to satisfy the request.
MissingMethodException is thrown if a constructor method ctor with the indicated name, class and signature could not be found. This is typically detected when MSIL instructions are converted to native code, not at run time.
The following Emit method overload can use the newobj opcode: