Getting Started

Below you will find a list of resources that will help you get started with TX Text Control .NET Server for ASP.NET.

Creating an ASP.NET Core Web App with Docker Support and GitHub Packages

Licensing

Docker

Creating an ASP.NET Core Web App with Docker Support and GitHub Packages

This article shows how to create an ASP.NET Core Web App with Docker support. The TX Text Control NuGet packages are hosted on GitHub Packages to get restored during the build process.

TX Text Control Document Editor Deployment Strategies

Backend

TCP Service

TX Text Control Document Editor Deployment Strategies

The TX Text Control document editor requires a server-side backend to synchronize the edited documents. This article gives an overview of best practices deployment strategies.

Unit Testing with NUnit and MSTest and TX Text Control .NET 32.0

Licensing

CI

Unit Testing with NUnit and MSTest and TX Text Control .NET 32.0

Unit testing is a common practice in which code is tested in isolation. This article shows how to use TX Text Control .NET 32.0 in such environments, and in particular how to handle licensing.

Using Azure Pipelines with TX Text Control .NET Server for ASP.NET

Azure DevOps

Build Server

Using Azure Pipelines with TX Text Control .NET Server for ASP.NET

Continuous integration is a common practice in which code is compiled on build servers at regular intervals for testing after commit or at specific stages of development. This article shows how to use TX Text Control .NET Server for ASP.NET 32.0 in such environments, and in particular how to handle licensing.

Document Editor Deployment with Docker and Windows Server Core 2019 and 2022 including Fonts

Docker

Windows Server 2022

Document Editor Deployment with Docker and Windows Server Core 2019 and 2022 including Fonts

This tutorial shows how to create a Docker image that deploys and installs all the requirements to run the ASP.NET Core backend needed for the document editor, using Windows Server Core 2019 and 2022.

Securing ASP.NET Core Web Apps: Protecting TX Text Control Editor and Viewer Endpoints

Security

Securing ASP.NET Core Web Apps: Protecting TX Text Control Editor and Viewer Endpoints

Securing document editing and viewing endpoints within web applications is critical to preventing unauthorized access. This article provides a comprehensive guide on integrating security middleware into ASP.NET Core to fortify these endpoints effectively.

Deploying an ASP.NET Core Web App to Azure App Services

32.0

Docker

Deploying an ASP.NET Core Web App to Azure App Services

This article shows how to create and deploy an ASP.NET Core Web App to Azure App Services with Docker. It shows all the necessary steps to create the application and the Dockerfile to deploy the application to App Services.

Deploying an ASP.NET Core Web App with Docker

32.0

Docker

Deploying an ASP.NET Core Web App with Docker

This article shows how to create and deploy an ASP.NET Core Web App with Docker. It shows all the necessary steps to create the application and the Dockerfile to deploy the application.

Can't Connect to the Server?

Debugging

Can't Connect to the Server?

TX Text Control's online document editor relies on a full-duplex WebSocket connection to a synchronization service. If this connection is somehow failing under rare conditions, users will get a trappable error. This article explains potential reasons and solutions for each case.

ASP.NET Core: Deploying TX Text Control 32.0 SP2 to Linux

Linux

ASP.NET Core: Deploying TX Text Control 32.0 SP2 to Linux

To deploy the TX Text Control 32.0 SP2 Document Editor on Linux as part of an ASP.NET Core Web application, the synchronization service must be deployed separately on a Windows VM. This allows the web application itself to be deployed to Azure App Services or other container-based deployment services.

Comments JavaScript API: Useful Tips and Tricks

Comments

Comments JavaScript API: Useful Tips and Tricks

The Comments JavaScript API is a powerful interface to customize the behavior of comments in the Document Editor. This article provides useful tips and tricks to get the most out of it.

Deploying the Document Viewer to Azure App Services

Linux

Deploying the Document Viewer to Azure App Services

Unlike the document editor, the document viewer doesn't require a TCP synchronization service to render the document. But it also requires a backend that runs on a Windows Server instance. This article shows how to deploy the backend and how to connect the viewer to this backend.

ASP.NET DocumentEditor: Setting the APIRoute

APIRoute

ASP.NET DocumentEditor: Setting the APIRoute

When deploying the ASP.NET DocumentEditor, it is important to define the resource path and the API route when deploying applications to virtual paths other than the root. This article shows how to define these paths.

ASP.NET DocumentEditor: Set Static Files Path

Static Files

Routes

ASP.NET DocumentEditor: Set Static Files Path

In recent versions, the static files path had to be defined for all routes in where the editor is used. A new property has been introduced to define the static files path once for all routes.

Using Different TCP Service Locations

TCP

WebSockets

Using Different TCP Service Locations

The Text Control online document editor requires a backend TCP service to synchronize the document rendering. This article explains how to route the synchronization traffic to different servers dynamically using a custom WebSocketHandler.

Using TX Text Control .NET Server with Build Servers

Azure DevOps

Build Server

Using TX Text Control .NET Server with Build Servers

Continuous Integration is a common practice to compile code on build servers periodically to run tests after commits or at specific development stages. This article shows how to use TX Text Control within such environments and in specific how to handle the licensing.

Deploying the Backend TCP Service Separately

Backend

TCP Service

Deploying the Backend TCP Service Separately

The Angular document editor requires an ASP.NET or ASP.NET Core backend connected to the TCP Service to synchronize the rendering. This article explains how to deploy the TCP Service separately from the backend application.

Angular: Typical Workflow with an ASP.NET Backend

Workflow

Web API

Angular: Typical Workflow with an ASP.NET Backend

This article explains typical workflows of how documents are merged with an ASP.NET Core backend Web API.

Deploying TX Text Control to Azure App Service

Azure

App Services

Deploying TX Text Control to Azure App Service

This article shows how to deploy web applications built with TX Text Control .NET Server to Azure App Service.

Popular Products

Technologies

Get Products

Resources

Getting Started

Support

Ready To Talk?

Text Control is an award-winning vendor of document processing and reporting components for Windows, web, cloud and mobile development technologies.

We ♥ documents.

Sign in Company Contact Us Privacy Policy Legal Notices

Copyright © 2024 Text Control, LLC. All rights reserved. Legal Notices.

TX Text Control, DS Server, ReportingCloud and other product names used herein might be trademarks or registered trademarks of Text Control, LLC and/or one of its subsidiaries or affiliates in the U.S. and/or other countries.

Live Demo