Client Types

Rich Client Deployment

ClickOnce Deployment

Setup on Server:

1. Configure in Displays → Clients → Rich
2. Set ClickOnce publishing location
3. Configure update settings
4. Build and publish

Client Installation:

http://server:10108/RichClient/setup.exe

Features:

• Automatic updates
• Certificate signing
• Offline capability
• Full .NET Framework access

MSI Package Deployment

For enterprise deployment via Group Policy:

1. Generate MSI installer
2. Configure silent installation
3. Deploy via SCCM or Group Policy

Silent Install:

cmd

msiexec /i FrameworXClient.msi /quiet
  SERVER=server.domain.com
  PORT=10108

Smart Client Deployment

Lightweight Windows client with auto-update:

Deployment URL:

http://server:10108/SmartClient.application

Requirements:

• .NET Framework 4.8
• Internet Explorer 11+ or Edge
• XAML Browser Applications enabled

Configuration:

xml

<configuration>
  <appSettings>
    <add key="ServerAddress" value="server.domain.com"/>
    <add key="ServerPort" value="10108"/>
    <add key="UseWindowsAuth" value="false"/>
  </appSettings>
</configuration>

Web Client (HTML5) Deployment

Server Configuration

Enable in Solution:

1. Displays → Clients → HTML5
2. Configure display conversion
3. Set responsive breakpoints
4. Publish to server

Access URL:

http://server:10108/html5/

Browser Requirements

Mobile Optimization

Configure viewport and touch settings:

html

<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="mobile-web-app-capable" content="yes">

Mobile Client Deployment

iOS Deployment

Requirements:

• iOS 14+
• iPhone 8 or newer
• 100 MB storage

Distribution Methods:

1. App Store (public)
2. TestFlight (testing)
3. Enterprise distribution

Android Deployment

Requirements:

• Android 8.0+
• 2 GB RAM minimum
• 100 MB storage

Distribution Methods:

1. Google Play Store
2. APK direct install
3. MDM deployment

Configuration

Mobile client settings:

json

{
  "serverUrl": "https://server.domain.com",
  "port": 10108,
  "useSSL": true,
  "offlineMode": false,
  "syncInterval": 30
}

Client Auto-Start

Windows Auto-Start Methods

Using AutoStartClient.exe:

AutoStartClient.exe automatically starts web pages or thin clients based on server status. It monitors the server and launches client displays when the runtime is ready.

cmd

AutoStartClient.exe /server:192.168.1.100 /port:3101 /display:MainScreen

Parameters:

Windows Startup Folder:

Place shortcut in:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp\

Or for current user only:

C:\Users\[Username]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\

Service Considerations

When the runtime runs as a Windows Service:

• Server components run without user interface
• Client displays MUST be started separately
• Service cannot launch UI components
• Use AutoStartClient.exe or manual shortcuts

Example Batch File for Client Startup:

batch

@echo off
timeout /t 30
cd "C:\Program Files (x86)\Tatsoft\FrameworX\10.1"
AutoStartClient.exe /server:localhost /port:3101 /display:Overview

Rich Client Startup

For Rich Client with specific parameters:

cmd

StartRichClient.bat /server:192.168.1.100 /display:MainScreen /username:Operator

See Runtime Installation (Reference) for complete TStartup.exe parameter list.

Kiosk Mode

Rich Client Kiosk:

cmd

StartRichClient.bat /kiosk /display:KioskDisplay /preventclose
EnableTaskSwitchProtection.bat

Browser Kiosk (Chrome):

cmd

chrome.exe --kiosk --app="http://server:10108/html5/" --no-first-run --disable-translate

Browser Kiosk (Edge):

cmd

msedge.exe --kiosk "http://server:10108/html5/" --edge-kiosk-type=fullscreen

Client Connection Security

Windows Authentication

Configure for domain environments:

xml

<security mode="Transport">
  <transport clientCredentialType="Windows"/>
</security>

SSL/TLS Configuration

For secure connections:

1. Install SSL certificate on server
2. Configure HTTPS binding
3. Update client URLs to use HTTPS
4. Set certificate validation policy

Troubleshooting Client Deployment