PPJ Manual
HomeCurrent IssuesDownloads
  • Welcome
  • Releases
    • PPJ 2023
  • PPJ 2023
  • PPJ Web API
  • PPJ Desktop API
  • Wisej.NET Documentation
  • General
    • Framework
      • Features
        • SAL and SQL Functions
        • Constants and Variables
        • SalContext
        • Visual Toolchest
        • XSal2
        • Reporting Support
        • LINQ Support
        • SalCompileAndEvaluate
        • Unicode Support
        • Startup Arguments
        • App.config
      • Data Types
        • Automatic Casts
        • Dynamic Arrays
      • Controls
        • ToolBar
        • TabControl
        • TableWindow
        • QuickObject
        • Ribbon Bar
        • NavigationBar
      • SQL Support
        • Configuration
        • ADO.NET Drivers
        • Bind and Into Variables
        • DBP Parameters
        • SqlContext
      • Extensions
        • Table Window
        • Unicode Support
        • Bug Fixes
        • Object Oriented Types
        • Custom Parsers
        • Named Properties
        • Microsoft Charts
        • Tabbed MDI
        • Watermark
        • HTML Rendering
      • Skins and Themes
        • Skin Files
        • Theme Files
        • Configuration
        • Skin Editor
        • Theme Builder
      • Tracing
        • Trace Viewer
        • Default Listeners
        • Tracing the Application
      • Spell Checker
        • Dictionaries
    • Ported Application
      • Project Structure
        • Late Bind Calls
        • Visual Styles
        • Unqualified References
        • Message Actions
        • When SQLError
        • Classes
      • Global Items
      • Forms
      • COM/ActiveX
      • Multiple Inheritance
      • Configuration Tool
      • Issues & Workarounds
    • Ported Reports
      • General
      • Crystal Reports
        • Structure
        • Unsupported Features
      • List & Label
        • Report Conversion
        • Structure
        • Document
        • Input Items
        • Passing Data
        • Unsupported Features
      • Reporting Services
        • Features
      • Stimulsoft
        • Break Groups
        • Fields
        • Formulas
        • Cache Mode
Powered by GitBook
On this page

Was this helpful?

  1. General

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!

PreviousDictionariesNextProject Structure

Last updated 2 years ago

Was this helpful?