Writing XMS .NET applications
The topics in this section provide information to help you when writing XMS .NET applications.
About this task
This section provides information that is specific to writing XMS .NET applications. For general information about writing XMS applications, see Writing XMS applications.
- Data types for .NET
XMS .NET supports System.Boolean, System.Byte, System.SByte, System.Char, System.String, System.Single, System.Double, System.Decimal, System.Int16, System.Int32, System.Int64, System.UInt16, System.UInt32, System.UInt64, and System.Object. Data types for XMS .NET are different from data types for XMS C/C++. We can use this topic to identify the corresponding data types.- Managed and unmanaged operations in .NET
Managed code is executed exclusively within the .NET common language runtime environment and is wholly dependent on the services provided by that runtime. An application is classed as unmanaged if any part of the application runs or calls services outside of the .NET common language runtime environment.- Destinations in .NET
In .NET, destinations are created according to protocol type and can be used only on the protocol type for which they are created.- Properties in .NET
A .NET application uses the methods in the PropertyContext interface to get and set the properties of objects.- Non-existent properties handling in .NET
The handling of non-existent properties in the XMS .NET is broadly consistent with the JMS specification, and also with the C and C++ implementations of XMS.- Error handling in .NET
XMS .NET exceptions are all derived from System.Exception. XMS method calls can throw specific XMS exceptions such as MessageFormatException, general XMSExceptions, or system exceptions such as NullReferenceException.- Use message and exception listeners in .NET
A .NET application uses a message listener to receive messages asynchronously, and it uses an exception listener to be notified asynchronously of a problem with a connection.Parent topic: Developing XMS .NET applications