Page History

Upgrade Command

In order to upgrade a legacy project, you just need to put the <project>.tProj file in the folder mapped to the Solutions Manager, so that project will be visible on the Solutions List (press Refresh after changing files in the folders).

Only projects from versions 9.1 and 9.2 can be upgraded directly. For older project files, first use the 9.1 or 9.2 product to upgrade to that version, the bring to the final step on version 10.

When a file with extension .tProj is found, it shows on the Solution list, with the prefix Project. When a legacy project is selected, the Upgrade Version command button is enabled. 

When Upgrading:

• The previous Project file remains intact, the system uses a copy of in the upgrade process. 
• A new Solution (extension dbSln) is created with the same name of upgraded project (only the extensions of the file will be distinct)
• After the upgrade, only the new Solution (.dbSln) will show on the solution list (the legacy project file is kept hidden from the list)

The first time you open an imported solution, the Designer will prompt you to do a Build Command (Runtime→Build And Publish).

Manual Upgrade Corrections

Most of the replacement of new names and properties is executed automatically, but there a few areas that a manual interface is necessary.

RuntimeUsers Database, TableName

The pre-defined value for the table name for RuntimeUsers is version 9.2 or older was: EditSecurityUsers_Runtime. That name was replace by SecurityRuntimeUsers. 

The Upgrade tools already tries to find and correct that name in Scripts and Database connections automatically, but the DATABASE itself you will be connecting, we can't change automatically. Therefore, before commission the version 10 to production, you need to rename the name is the target database, from EditSecurityUsers_Runtime to SecurityRuntimeUsers

Advanced Toolkit applications

Some advanced applications using the product toolkits, and the API for programatic engineering (EngWrapper API), are likely to lack compatibility due the renaming of internal data structures and tables. Contact support if upgrading such applications. 

Themes

The Themes features from 9.2 allowed extensive customization, with the drawback that could be quite complex to manage. 

The Themes features of version was expanded, with more built-in themes, and extremely simplified, but the migration can't be fully automated. Those solutions needs to have a review on the colors of screen and objects that were mapped to theme resources. 

Scripts Asynchronous Methods

Version 10 uses a more modern and efficient programming pattern that is Asynchronous methods. That allows better performance on displays, and it is one the technologies that enabled most of Windows WPF displays, to run also on WEB HTML5 with no modifications. 

When creating new solutions, that is done automatically for you, but legacy Displays that had heavy CodeBehind Scripts, may need to the methods modified to use the async operator. 

For more information on Async programming: https://learn.microsoft.com/en-us/dotnet/csharp/asynchronous-programming/

Solution Server

There are two options for Solution Server: Localhost or Remote. If you select Remote, you will need to set it up.

Solution Location

The Solution Location enables connecting to a remote server to access the solutions. To connect to a remote server, use the IP address and port of the target Solution Server. It can request the Access Key. It refers to the password defined on the target remote server. This configuration is available on the Local Computer Management.

Local Computer Management

The Local Computer Management defines an AccessKey to connect with the Solution Server hosted on the local computer, adding an extra security layer for the remote server. It has configuration fields for setting and verifying the AccessKey, with a "Set AccessKey" field to enter the password and a "Verify" field to re-enter the password for verification. The "Apply" button applies the AccessKey.

Local Search Folders

Local Search Folders manage storage directories, visibility, and remote access definitions. They offer control buttons to add and remove folders from search and checkboxes for configuring folder visibility and remote access. It allows for a granular configuration of privacy and security settings for each folder in your solution's directories.

Connected Server Information

The Connected Server Information shows the operating system, server URL, server IP, installed versions, and services running. By default you have, the SolutionServer runs on the Port:10108, Hardkey, and WebServices. Also, you can set the services (WebServices, MQTT Broker, and Hardkey) to start as Windows services.

Solutions List Built From

Local Computer

The Solutions exhibited in the Solution Selector list are the ones set in Local Search Folders when the application started to run.

If you copy a new Solution (.tproj or .dbsln file) to a folder listed in Local Search Folders, it will not be exhibited in the Solution Selector until you click the Refresh button. To add or remove a folder from the search paths:

1. Click Find Solutions file.

2. Click Add Search Path to insert a new path;

3. Click Remove Search Path to remove a path.

4. Check Allow Remote Access and Allow Remote Run for multi-user development. (Optional) 

Remote Server

To exhibit the Solution List from a remote server, the client computer must be connected to the Solution Server using their IP address and Port.

Suppose you have a computer where the solutions files are stored and managed. Also, suppose you have other computers that you want to work remotely on the solutions files stored in the server. Both computers must have the software platform installed and licensed. The client must be connected to the solution server.  It means that the computer used to access files will use the IP and Port from the computer that stores the solutions to connect with it and access their files. You can also connect the platform to its remote server using the 127.0.0.1 IP address and the Port where the Solution Server is running on your computer. By default, the Solution Server runs on the 10108 port.

The TWebServices must be running to accept remote connections. See Service Verification for more information.

If using the Embedded Web Service (TWebService) platform, no configuration is required. If using Microsoft IIS web server, see Installing on Microsoft IIS.

Finding Solutions Folders

After clicking Find Solutions in the Manager Workspace, you will be addressed to the Server Information, which allows to easily set a Solution to auto-startup and define if the Solution Selector list will exhibit Solutions from a local or remote computer. 

Folder Visibility and Remote Access configuration

Any folder included in Local Search Folders has the controls for visibility and remote access. 

The permissions for remote access is by folder, therefore place your Solutions on the folders accordingly. You can keep many Solutions in one folder, or create a folder for each one. 

To manage your Solutions Folders:

1. After adding a search path, select the one you would like to allow remote access.

2. Check Visible to enable remote access for selected folder.

3. Check Allow Remote to enable Solutions from selected folder to be run by remote users.

In this section: