Displays Client Types

Many types of remote graphic clients are supported. This page will describe what is required for the installation and configuration of each one of these types of clients.

Rich Clients

Runs as a desktop application, allows blocking the Windows task-switch. This is ideal for process control applications that need high performance and enhanced security.

Smart Clients

Uses Click-Once technology. Installs and updates on remote clients with a single click from a browser and is automatically updated on the remote clients when it is updated on the server. It uses all the power of the remote computer yet retains the advantages of a centralized installation.

Web HTML5 Clients

Runs directly from the Web-Browser with no installation of any software required (nor any active-x controls!). The partial-trust security guarantees it runs in a completely isolated secure environment.

To DO:  (Consolidate)

Runtime Fundamentals

Runtime Components

Execution Modes

Development Mode

• Full diagnostics enabled
• Detailed error messages
• Performance monitoring
• Online configuration changes

Production Mode

• Optimized performance
• Minimal logging
• Security enforced
• Stable operation

Monitoring Runtime

1. Runtime Information
   • Solution Center → Tools → Runtime Info
   • Shows module status, memory, connections
2. Property Watch
   • Monitor tag values in real-time
   • See quality and timestamps
3. Diagnostics
   • View logs and traces
   • Analyze performance

Each client type offers different trade-offs between performance, security, deployment ease, and platform support.

Client Comparison

Rich Client

Desktop application with maximum control and performance.

Rich Clients Setup

A Rich Client is a computer with the FrameworX RichClient installed. The RichClient is a WPF-based desktop application. (in Linux, the Rich Client is a WinForm application)

Advantages:

Program: TRichClient.exe (64-bit)
Port: 3101 (configurable)
Technology: WPF

Web Client (WebAssembly)

Browser-based access with zero installation.

http://<ServerIP>/html5
or
https:// if certificate is installed

Smart Client

One-click deployment with automatic updates.

http://<ServerIP>/smartclient
or
https:// if certificate is installed

Browsers Compatible with ClickOnce

Historically, only Internet Explorer (IE) ever had built-in ClickOnce support.

• ClickOnce was a Microsoft deployment technology (introduced with .NET 2.0) that allowed launching and installing Windows apps directly from a link (.application file).

• IE could recognize and execute those files without add-ons.

Browsers that require a plugin/extension

• Microsoft Edge (Legacy / Chromium)

  • No native support.

  • Possible with the “ClickOnce for Microsoft Edge” extension (Microsoft-published).

  • Extension is available in the Microsoft Edge Add-ons store.

• Google Chrome

  • No native support.

  • Possible with the “Meta4 ClickOnce Launcher” or “ClickOnce for Google Chrome” extension.

  • Extensions pass the .application file to the local ClickOnce handler.

• Mozilla Firefox

  • No native support.

  • Possible with the “FFClickOnce” add-on (popular for years).

• Other browsers (Opera, Safari, etc.)

  • Generally no plugin support for ClickOnce.

  • Workarounds involve downloading the .application file manually and running it with the Windows ClickOnce runtime.

  • Not recommended, the RichClient installation is better in this scenario, or the web client.

Runtime Architecture

Server Components

Deployment Considerations

Security Features

Feature	RichClient	SmartClient	WebClent
User Authentication
Task Switch Block
Encrypted Comm			HTTPS
Sandbox Mode
Certificate Auth

Auto-Start Configuration

Windows Auto-Start

Create shortcut in Startup folder:

Rich: C:\Program Files\FrameworX\TRichClient.exe
Smart: http://server/TSmartClient.application
Web: http://server/html5/index.html

Command Line Options

TRichClient.exe /server:192.168.1.100 /solution:MyProject

Performance Guidelines

Rich/Smart Clients

• Multi-threaded execution
• Local graphics acceleration
• Binary communication
• Cached resources

Web Clients

• Single-threaded JavaScript
• Browser rendering engine
• HTTP overhead
• No local caching

Troubleshooting

Connection Issues:

• Verify server port access
• Check firewall settings
• Test network connectivity
• Review server logs

Update Problems:

• Clear browser cache (Web)
• Reset ClickOnce cache (Smart)
• Reinstall client (Rich)

Performance Issues:

• Check network latency
• Monitor server load
• Verify client resources
• Review display complexity

In this section...

Trade offs:

• Local product installation is required (Solution is remote, only the product is local). Therefore, product updates must be deployed to each client station.

Image Removed

Installation

Install FrameworX on the client computer.

How to start

Run the TRichClient.exe program. For an example of how to automatically start the client when a user logs into Windows, see Automatically Starting Windows Clients in the previous section.

Execution

The project runs in its own window. This client type has strong user security and includes the ability to disable the user from using the Windows Task Switch functionality. The ability to use or not use the Windows Task Switch can be tied to the user login. When running the TRichClientt.exe program on 64-bit machines, the application runs in 64-bit native code. If you need to run the 32-bit version, you can use the TRichClient32.exe program; this can be used to ensure compatibility with legacy COM and Active-X components.

Communication

Communicates with the server using the Windows Communication Foundation (WCF) (port configurable, default 3101).

Smart Clients Setup

A .NET Smart Client automatically downloads the application the first time you execute and also when it is updated on the server. It uses local processing so the hardware requirements are identical to the Rich Client, but there is no local installation of either the product or the project, therefore having all the benefits of a web-based solution plus the performance and security of a desktop solution.

• One-click application installation.
• Application updates are downloaded automatically from the server.
• Allows the blocking of Windows task switching
• Automatically recognize redundant servers

Trade off:

• Only available to Windows computers

Image Removed

Smart clients are client applications that behave like rich clients but either run from the web or can be installed painlessly with a single click. You can deploy your application to be used by Windows smart clients. The smart client runs like the rich client, but it uses ClickOnce™ installation. This technology allows you to have the same functionality as the rich client without having to install the software on your computer.

The first time you access the application, the system automatically downloads the components necessary to run the application. The next time you access the application, the system checks if the local cache is the same version of the application that is on the server, and if necessary, updates the local cache before running the application. If the version is the same, the application starts immediately.

Installation

No installation required. The client computer needs to have the .NET Framework 4.0 and Internet Explorer 8.0 or later. 
The first time you start the application, it will automatically download the required components from the server. Every time the application starts, it automatically verifies if a new version is available on the server.

How to start

From Internet Explorer (or a shortcut) go to the URL:
http://<ServerIPAddressorName>/fs-2018.1/ TSmartClient.application  
For an example of how to automatically start the client when a user logs into Windows, see Automatically Starting Windows Clients in the previous section.

Execution

Runs exactly the same as the rich client. The functionality of the rich client and the smart client are the same; only the installation and activation methods are different.

Communication

Communicates with the server using WCF (port configurable, default 3101).

Web HTML5 Clients Setup

The Web clients run inside the browser.

Advantages:

• Requires only web browser and it is multi-platform.
• No installation required on the client-side Application.
• Updates are downloaded immediately from the web server.

Trade offs:

• Requires a web server (however, FrameworX includes a zero-config Web server).
• Browser does not block Windows task switching (Ctrl+Alt+Del, Alt+Tab, etc).
• Data communication performance, due the HTTP protocols will be slower than SmartClient and redundancy options must have external IP resolving or operator confirmation.

Image Removed

Installation

No installation required. The client computer needs to have the .NET Framework 4.0 and Internet Explorer 8.0 or later. 
The first time you start the application, it will automatically download the required components from the server. Every time the application starts, it automatically verifies if a new version is available on the server.

How to start

From Internet Explorer (or a shortcut) go to the URL:
http://<ServerIPAddressorName>/fs-2018.1 /TWebClient.Xbap
For an example of how to automatically start the client when a user logs into Windows, see Automatically Starting Windows Clients in the previous section.

Execution

Runs inside a web browser window using "Partial Trust" (Sandbox Security).

Communication

Communicates with the server using HTTP or HTTPS (port 80).

Clients Technologies Comparison

The three types of displays supported  (.NET, HTML5 and iOS) have their own benefits and trade offs. Depending on the Application each one, or a combination of more than is more suitable for your application.

Clients Technologies comparison 

Display Type

Comments

.NET Clients

Only to clients running on Windows Operating Systems.

Higher performance of all options, with Multithreading on the client side.

Stronger Security, allowing for instance to disable the Task Switch based on the User Logged.

It is can be executed as a RichClient or SmartClient application.

HTML5 Clients

• All platforms (Android, iOS, Mac, Linux, Windows).

• Working on serveral browsers (Chrome, Firefox, Microsoft Egde, etc).

• Single-threading.

• No "Layouts". 

• No script class and task clients. Only codebehind of displays (Javascript).

• Number of built-in controls lower than .NET but greater than Winforms.

• Thousands of controls on the Internet can be used as external controls

In this section: