Deploying FrameworX runtime components for production environments.

Parent Page: Deployment (Reference)

Deployment Scenarios

Windows Runtime Deployment

For Windows-only solutions targeting .NET Framework 4.8:

• Install the complete FrameworX platform (same as Designer)
• No separate runtime-only installer exists
• Configure to use only runtime components in production
• Disable Designer access if needed for security

Multiplatform Runtime Deployment (.NET 8)

For solutions targeting Linux, Docker, or edge devices:

Windows Runtime Setup

Since Windows uses the full platform installation:

1. Install FrameworX (see Installation & Licensing)

1. Configure for Runtime Only
   • Solution Center → Runtime → Startup
   • Set solution to auto-start
   • Configure as Windows Service

1. Install as Windows Service

   cmd

   cd C:\Program Files (x86)\Tatsoft\FrameworX
   InstallTStartup.exe /service

1. Service Configuration
   • Service name: FrameworX Runtime
   • Startup type: Automatic
   • Recovery: Restart on failure

.NET 8 Runtime Deployment

Option 1: Runtime-Only (Production)

Deploy minimal components for production:

Required Files:

/opt/frameworkx/
??? TServer.exe
??? TWebServices.exe
??? Driver assemblies
??? Solution files (.tproj, .dbsln)
??? Runtime dependencies

Linux Installation:

bash

# Create directory
sudo mkdir -p /opt/frameworkx

# Copy runtime files
sudo cp -r /source/net8.0/runtime/* /opt/frameworkx/

# Set permissions
sudo chmod +x /opt/frameworkx/*.exe

# Start runtime
./TServer.exe /solution:MySolution.tproj

Option 2: Full Platform (Remote Designer)

Deploy all files to enable ClickOnce Designer access:

Benefits:

• Windows clients access Designer with zero installation
• Browse to http://device-ip:10108/solutions
• Designer runs on client, edits on device
• Supports multiple product versions

Deployment:

bash

# Copy entire platform
sudo cp -r /source/net8.0/* /opt/frameworkx/

# Includes Designer files (not executed on device)
# Size: ~500 MB+

Option 3: TWebServices-Only (Development)

Minimal deployment for development:

• Deploy only TWebServices.exe
• Push solution and runtime remotely
• Not recommended for production (slow)
• Useful for testing and development

Service Configuration

Windows Service

Configure in Runtime → Startup or manually:

xml

<service>
  <name>FrameworXRuntime</name>
  <displayName>FrameworX Runtime Service</displayName>
  <description>FrameworX Solution Runtime</description>
  <startMode>Automatic</startMode>
</service>

Linux systemd

Create /etc/systemd/system/frameworkx.service:

ini

[Unit]
Description=FrameworX Runtime
After=network.target

[Service]
Type=simple
User=frameworkx
ExecStart=/opt/frameworkx/TServer.exe /solution:MySolution.tproj
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

Enable and start:

bash

sudo systemctl enable frameworkx
sudo systemctl start frameworkx

Auto-Start Configuration

TWebServices Auto-Start

Configure TWebServicesRunPrograms.json:

json

{
  "appSettings": {
    "RunPrograms": {
      "Solution1": "/opt/frameworkx/solutions/MySolution.tproj",
      "CustomApp": "/usr/local/bin/customapp"
    }
  }
}

Location: /home/frameworkx/MachineSettings/ (Linux) or C:\Users\Public\Documents\FrameworX\MachineSettings\ (Windows)