# Ported Application Ice Porter generates a complete Visual Studio project that can be opened right after the conversion process. The new project is fundamentally different from the original OpenText Team Developer application and it's important to understand the structure and organization of the new .NET project to be able to find things quickly. The biggest difference is that each single class or form template is in a separate file, while in the original application a SAL file may contain several classes and other objects. Also SAL has a number of items that do not belong to any class and are considered to be global, while in .NET (just like Java) everything must be in a class. Therefore Ice Porter also generates some "global" classes that contain the static members that have been ported from the original application global items. Another big difference is that in Visual Studio you cannot design a form if the application is not fully compiled. That is because in .NET everything is in the code and there is no meta-data used to define forms. This gives you great flexibility, but it also creates many more opportunities to write wrong code. In this section of the manual we'll explain the organization of the ported project to help you find your way around the new code. Good luck! --- # Agent Instructions: 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: ``` GET https://docs.iceteagroup.com/general/ported-application.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.