Solution Settings Reference

Configure global solution properties.

Reference → Solution →  Designer → Settings and Tools →  Settings | Categories | Import Tags | Import Plugin | Export | History

Settings Sections

Solution Information

Read-only information about the current solution:

Target Platform and License

Core deployment configuration:

Solution Options

Solution-wide options:

Retentive Database Settings

Click gear icon to configure:

Run Modules Inside Main Process

Controls whether each module runs inside the main TServer process or in a dedicated isolated process (TProcessDomain.exe).

When to enable

Enable only when all three of the following conditions are true:

• The target hardware has severely limited CPU (e.g., embedded or edge controllers).
• The target hardware has severely limited memory.
• The solution contains very few modules/channels (typically one or two).

This is a last-resort optimization for resource-constrained deployments. For any normal deployment, leave both disabled.

Trade-offs

Diagnostic: confirming the execution mode at runtime

In the Devices runtime monitor, each channel displays:

• Process Name — shows TServer when the channel runs inside the main process; shows TRunModule when running in a separate process.
• Process PID — the PID of the hosting process.

Python Interpreter

Python integration paths:

Global Script Namespace Declarations

From FrameworX 10.1.6, the Global Script Namespace Declarations field lists namespaces available to every C# and VB.NET script of the solution, with no per-script declaration: Script Tasks, Script Classes, expressions and display code-behind, on the server and on the clients.

• Separate the namespaces with semicolons, for example System.Text.Json;MyCompany.Common.
• Enter plain dotted namespace names. A pasted using or Imports prefix is removed. Aliases and using static are not supported, and invalid entries are ignored.
• A change applies at the next compile, with no Designer restart.
• The global namespaces also feed IntelliSense and appear in the predefined list of the per-script Namespace Declarations dialog.
• A namespace declaration does not add an assembly to the build. For a namespace from an external DLL, add the DLL in Scripts → References. See Scripts References Reference.

In 10.1.5, namespaces are declared per script only, in the Namespace Declarations dialog of the Code Editor.

Provider Support

Database Providers

Configuration Guidelines

Platform Selection

Windows Only - Choose when using:

• Windows Authentication
• OPC Classic
• Canary Historian
• Windows-specific .NET libraries

Multiplatform - Choose when:

• Deploying to Linux
• Using Docker containers
• Cross-platform requirement
• Cloud deployment

License Configuration

Must match production license:

Culture Info Settings

Best Practices Checklist 

Initial Setup

• Set Target Platform before development
• Configure Product Model to match license
• Set Culture Info for target locale
• Configure Python if using scripts

Retentive Database

• Use SQLite for standalone
• Use SQL Server for enterprise
• Test connection before saving
• Document connection string

Module Execution

• Script Tasks and Device Channel(s): leave both disabled unless the hardware is severely resource-constrained (limited CPU, limited memory, very few modules/channels). See Run Modules Inside Main Process above.
• Monitor Process Name in the Devices runtime monitor to confirm which execution mode is active.

Troubleshooting

In this section...