> For the complete documentation index, see [llms.txt](https://docs.iceteagroup.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iceteagroup.com/general/framework/features/xsal2.md). # 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 should replace XSal code using .NET's native remoting or web services. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.iceteagroup.com/general/framework/features/xsal2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.