api0 Summary for E1 Summary for E1.Value1 Summary for E2 Summary for E2.A Extension methods for the enumeration. Retrieves the constant that describes . The instance on which this method operates. Retrieves the value named by . The name of the constant to retrieve. Summary for E3 Summary for E3.ErrorA Extension methods for the enumeration. The extension method for the enumeration can be used to fetch the error domain associated with these error codes. Returns the error domain associated with the XmlDocumentation.E3 value The enumeration value See the for information on how to use the error domains when reporting errors. Summary for E4 Summary for E4.Bit1 Summary for E4.Bit3 Summary for Notification1 The Objective-C class handle for this class. The pointer to the Objective-C class. Each managed class mirrors an unmanaged Objective-C class. This value contains the pointer to the Objective-C class. It is similar to calling the managed or the native objc_getClass method with the type name. Creates a new with default values. Constructor to call on derived classes to skip initialization and merely allocate the object. Unused sentinel value, pass NSObjectFlag.Empty. This constructor should be called by derived classes when they completely construct the object in managed code and merely want the runtime to allocate and initialize the . This is required to implement the two-step initialization process that Objective-C uses, the first step is to perform the object allocation, the second step is to initialize the object. When developers invoke this constructor, they take advantage of a direct path that goes all the way up to to merely allocate the object's memory and bind the Objective-C and C# objects together. The actual initialization of the object is up to the developer. This constructor is typically used by the binding generator to allocate the object, but prevent the actual initialization to take place. Once the allocation has taken place, the constructor has to initialize the object. With constructors generated by the binding generator this means that it manually invokes one of the "init" methods to initialize the object. It is the developer's responsibility to completely initialize the object if they chain up using this constructor chain. In general, if the developer's constructor invokes the corresponding base implementation, then it should also call an Objective-C init method. If this is not the case, developers should instead chain to the proper constructor in their class. The argument value is ignored and merely ensures that the only code that is executed is the construction phase is the basic allocation and runtime type registration. Typically the chaining would look like this: A constructor used when creating managed representations of unmanaged objects. Called by the runtime. Pointer (handle) to the unmanaged object. This constructor is invoked by the runtime infrastructure () to create a new managed representation for a pointer to an unmanaged Objective-C object. Developers should not invoke this method directly, instead they should call as it will prevent two instances of a managed object pointing to the same native object. Notifications posted by the class. This class contains various helper methods that allow developers to observe events posted in the notification hub (). The methods defined in this class post events that invoke the provided method or lambda with a parameter, which contains strongly typed properties for the notification arguments. Strongly typed notification for the constant. The handler that responds to the notification when it occurs. Token object that can be used to stop receiving notifications by either disposing it or passing it to . This method can be used to subscribe to notifications. { Console.WriteLine ("Observed ANotification!"); }; // Stop listening for notifications token.Dispose (); ]]> Strongly typed notification for the constant. The specific object to observe. The handler that responds to the notification when it occurs. Token object that can be used to stop receiving notifications by either disposing it or passing it to . This method can be used to subscribe to notifications. { Console.WriteLine ($"Observed ANotification for {nameof (objectToObserve)}!"); }; // Stop listening for notifications token.Dispose (); ]]> Summary for P1 Summary for PA1.PMethod Summary for PA1.PProperty Extension methods to the interface to support all the methods from the P1 protocol. The extension methods for interface allow developers to treat instances of the interface as having all the optional methods of the original P1 protocol. Since the interface only contains the required members, these extension methods allow developers to call the optional members of the protocol. Summary for P1.PMethod Summary for P1.PProperty Summary for P1.PProperty Summary for PA1.PMethod Summary for PA1.PProperty Summary for T1 The Objective-C class handle for this class. The pointer to the Objective-C class. Each managed class mirrors an unmanaged Objective-C class. This value contains the pointer to the Objective-C class. It is similar to calling the managed or the native objc_getClass method with the type name. Creates a new with default values. Constructor to call on derived classes to skip initialization and merely allocate the object. Unused sentinel value, pass NSObjectFlag.Empty. This constructor should be called by derived classes when they completely construct the object in managed code and merely want the runtime to allocate and initialize the . This is required to implement the two-step initialization process that Objective-C uses, the first step is to perform the object allocation, the second step is to initialize the object. When developers invoke this constructor, they take advantage of a direct path that goes all the way up to to merely allocate the object's memory and bind the Objective-C and C# objects together. The actual initialization of the object is up to the developer. This constructor is typically used by the binding generator to allocate the object, but prevent the actual initialization to take place. Once the allocation has taken place, the constructor has to initialize the object. With constructors generated by the binding generator this means that it manually invokes one of the "init" methods to initialize the object. It is the developer's responsibility to completely initialize the object if they chain up using this constructor chain. In general, if the developer's constructor invokes the corresponding base implementation, then it should also call an Objective-C init method. If this is not the case, developers should instead chain to the proper constructor in their class. The argument value is ignored and merely ensures that the only code that is executed is the construction phase is the basic allocation and runtime type registration. Typically the chaining would look like this: A constructor used when creating managed representations of unmanaged objects. Called by the runtime. Pointer (handle) to the unmanaged object. This constructor is invoked by the runtime infrastructure () to create a new managed representation for a pointer to an unmanaged Objective-C object. Developers should not invoke this method directly, instead they should call as it will prevent two instances of a managed object pointing to the same native object. Summary for T2.#ctor(String) Summary for T1.Method Summary for PA1.PMethod Summary for PA1.PProperty Summary for P1.PProperty Summary for T1.Property Summary for TG1 The Objective-C class handle for this class. The pointer to the Objective-C class. Each managed class mirrors an unmanaged Objective-C class. This value contains the pointer to the Objective-C class. It is similar to calling the managed or the native objc_getClass method with the type name. Creates a new with default values. Constructor to call on derived classes to skip initialization and merely allocate the object. Unused sentinel value, pass NSObjectFlag.Empty. This constructor should be called by derived classes when they completely construct the object in managed code and merely want the runtime to allocate and initialize the . This is required to implement the two-step initialization process that Objective-C uses, the first step is to perform the object allocation, the second step is to initialize the object. When developers invoke this constructor, they take advantage of a direct path that goes all the way up to to merely allocate the object's memory and bind the Objective-C and C# objects together. The actual initialization of the object is up to the developer. This constructor is typically used by the binding generator to allocate the object, but prevent the actual initialization to take place. Once the allocation has taken place, the constructor has to initialize the object. With constructors generated by the binding generator this means that it manually invokes one of the "init" methods to initialize the object. It is the developer's responsibility to completely initialize the object if they chain up using this constructor chain. In general, if the developer's constructor invokes the corresponding base implementation, then it should also call an Objective-C init method. If this is not the case, developers should instead chain to the proper constructor in their class. The argument value is ignored and merely ensures that the only code that is executed is the construction phase is the basic allocation and runtime type registration. Typically the chaining would look like this: A constructor used when creating managed representations of unmanaged objects. Called by the runtime. Pointer (handle) to the unmanaged object. This constructor is invoked by the runtime infrastructure () to create a new managed representation for a pointer to an unmanaged Objective-C object. Developers should not invoke this method directly, instead they should call as it will prevent two instances of a managed object pointing to the same native object. Summary for TG1.TGMethod Summary for TG1.TGProperty