> 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/ported-application/project-structure/classes.md). # Classes ## Functional Classes Functional Classes from the original OpenText Team Developer application are all ported to public classes. The files are located either in the main application's directory or in the \Classes subdirectory, depending on the options set in Ice Porter. The structure of the generated classes is simple and reflects the original structure. The description of the class is ported to the \ comments for the class. Variables and functions are grouped together and enclosed in regions. If the class had a ObjectDestructor() method, the code is ported into a destructor in .NET. However, destructors in .NET are not called in a predictable manner because of the garbage collector. This difference in behavior may cause problems in the ported application and needs to be addressed by a developer. The base class for Functional Classes is PPJ.Runtime.SalFunctionalClass. ## Visual Classes Visual classes are all ported to public classes derived from the corresponding control class in the PPJ Framework. The files are located either in the main application's directory or in the \Controls subdirectory, depending on the options set in Ice Porter. The structure of visual classes is compatible with the Visual Studio Designer guidelines. All the visual properties are generated in the InitializeComponent() method. A call to InitializeComponent() is placed in the constructor. For .NET 2.0 and if the appropriate option in Ice Porter has been set, the designer's code is generated into a separate file called \.Designer.cs. Not all visual classes can be designed, however. Visual Studio can design only container classes, unlike SQLWindows/Team Developer that can design also single control classes. Nevertheless, Ice Porter generates designer-compatible code also for single control classes. --- # 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/ported-application/project-structure/classes.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.