Click or drag to resize
Global Items

SQLWindows/Team Developer had many objects that are global and shared by all classes in the application. In .NET everything must be in a class, therefore the most natural translation of  global items to convert them to static members contained into static classes. In the Table below you can see the location of global items in the ported code:

SAL Global Item

New location in the .NET application

Internal Functions

Int.cs or Internals.vb

External Functions

Ext.cs or Externals.vb

Global Variables

Var.cs or Variables.vb

User Constants

Const.cs or Constants.vb

System Constants

Const.cs or Constants.vb


Res.cs or Resources.vb

Global Named Menus

App.cs or Application.vb

All global members, in any assembly that is part of the project, are automatically recognized at runtime by the PPJ Framework without the need to scope them. Basically, if a global item (a variable, constant, internal function, etc.) is used in a bind expression or in a SalCompileAndEvaluate expression, there is no need to scope it because it is recognized automatically.