Writing XMS .NET applications

This section provides information to help you when writing XMS .NET applications, including information about properties, data types, and error handling.

Before you begin

[Deprecated][MQ 9.4.0 Jun 2024][MQ 9.4.0 Jun 2024]From IBM® MQ 9.4.0, in IBM MQ classes for XMS .NET, the methods WriteObject(), ReadObject(), CreateObjectMessage(), and the classes ObjectMessage and XmsObjectMessageImpl used for serialization and deserialization of data are deprecated.

[Removed][MQ 9.4.0 Jun 2024][MQ 9.4.0 Jun 2024]The XMS .NET client library built using.NET Standard 2.0, which was deprecated at IBM MQ 9.3.1, has been removed from the product at IBM MQ 9.4.0.

From IBM MQ 9.2.0, the number of XMS .NET dynamic link libraries has been significantly reduced, to a total of five. The five dynamic link libraries are:
  • IBM.XMS.dll - includes all the national language messages
  • IBM.XMS.Comms.RMM.dll
  • Three policy dynamic link libraries:
    • policy.8.0.IBM.XMS.dll
    • policy.9.0.IBM.XMS.dll
    • policy.9.1.IBM.XMS.dll

In XMS .NET, all strings are passed using the native .NET string. Because this has a fixed encoding, no further information is required to interpret it. Therefore the XMSC_CLIENT_CCSID property is not required for XMS .NET applications.