The product TX Text Control .NET Server contains different modules, components and services to provide document processing functionality and backend tasks for visual document editing libraries.

The following diagram shows these features and also illustrates the dependencies for various functionalities.

The Backend Core

TX Text Control .NET Server runs on Windows machines (Server and Desktop) and provides common document processing functionality. The setup must be installed in order to develop using the libraries and services with a developer license. When applications are deployed, a developer license is not required and only the redistributable files need to be copied.

Common Functionalities

The backend offers 3 major common functionalities:

• MailMerge
  The MailMerge class provides the core functionality to merge hierarchical data into templates. This component is taking care of populating fields, images, charts, barcodes and other dynamic elements with associated data fields.

• ServerTextControl
  The ServerTextControl class is the non-UI document processing component to create and edit documents using a fully featured API. This component can be used to load and save various document types including MS Word DOC, DOCX, RTF and Adobe PDF. It can be connected to the MailMerge engine to merge data into documents loaded into ServerTextControl.

• TCP Synchronization Service
  The TCP synchronization service runs on a Windows machine to synchronize the document and calculate rendering information for the visual document editor components. This service enables the true WYSIWYG, pixel-perfect rendering including server-side fonts that can be used with all clients and browsers.

DocumentViewer and WebSocketServer

On top of these common features of TX Text Control .NET Server, the package provides client-side components to display and edit documents.

• MVC DocumentViewer
  The DocumentViewer is a lightweight, cross-browser compatible, mobile-friendly viewer for ASP.NET MVC. It is typically used to display documents and resulting reports in ASP.NET MVC web applications. Documents can be loaded from files resides physically server-side, from data or from JavaScript.

• WebSocketServer
  The WebSocketServer provides the WebSocketHandler which is the communication proxy between the client-side editing components and the TCP Synchronization Service. The client-side components open a consistent WebSocket connection to the WebSocketServer to synchronize the rendering.

Client-Side Document Editing

The client-side document editing components are all based on the WebSocketServer which can be either hosted on Windows or other operating systems.

• MVC Document Editor
  The Web.MVC.TextControl class represents an extension object implementing the rich text editor functionality for ASP.NET MVC applications. It is available as a NuGet package and can be used without any reference to other TX Text Control assemblies. But a connection to a WebSocketServer is required. This component runs on Windows only.

• TX Text Control for Angular
  TX Text Control for Angular represents an Angular component implementing the rich text editor functionality for Angular applications. It is available as an npm package and can be used without any reference to other TX Text Control assemblies. But a connection to a WebSocketServer is required. This component can be used on any platform including Windows and Linux.

• TX Text Control for Node.js
  TX Text Control for Node.js represents a Node.js component implementing the rich text editor functionality for Node.js applications. It is available as an npm package and can be used without any reference to other TX Text Control assemblies. But a connection to a WebSocketServer is required. This component can be used on any platform including Windows and Linux.

Download a trial version of TX Text Control .NET Server to test this on your own.