XSal2

Most of the features in the XSal2 library are implemented in the PPJ.Runtime.XSal assembly. The names of the methods and the classes are unchanged. Static functions are implemented as static methods in the XSal class, therefore what was XSalToolboxCreate() is now XSal.ToolboxCreate().

All XSal2 functions and controls are implemented using .NET native controls. The constants defined in the XSal2 library are converted to enumerations with similar names.

Unsupported Features

XSalMap

XSalMap functionality should be replaced using one of the many Dictionary collections available in the .NET Framework. The XSal implementation was very limited due to constraints in TD and cannot be ported effectively to .NET.

XSalRemoteObjects

Remoting in XSal is achieved using a proprietary protocol and is not supported in the PPJ. Applications using XSalRemoteObjects need an explicit replacement communication contract, such as a service API. Do not introduce .NET Remoting for a modern .NET target; it is unsupported there. See unavailable .NET Framework technologies.

Replacement Design

For XSalMap, choose dictionary key comparison, duplicate-key behavior, ordering, and null handling deliberately. For remote objects, document authentication, serialization, failure handling, and object lifetime; replacing the transport alone does not preserve these behaviors.