|
|
|
|
In order to deploy the TX Text Control document editor to Azure App Services as part of an ASP.NET Core (.NET 5/6) Web Application, the synchronization service can be deployed separately to a VM.
This way, the web application itself can be deployed to Azure App Services or other container based deployment services. This best practice article shows how to deploy the required backend and how to connect the editor to it. |
|
|
|
|
| Deploying the TX Text Control Document Viewer to Azure App Services |
Unlike the 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 separate instance when deployed to Azure App Services or Linux.
This article shows how to deploy the backend and how to connect the viewer to this application. |
| Learn more |
|
| Load Balancing: Using Different TCP Service Locations using a Custom WebSocketHandler |
| 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. |
| Learn more |
|
| See TX Text Control 30.0 at NDC Oslo 2021 |
Missing conferences?
Good news then! We can't wait to get back to Norway for NDC Oslo located at the great venue Oslo Spektrum. With 2 full workshop days and 3 days of conference sessions, it will be one of the largest in-person events for us this year with more than 2000 attendees.
We will be exhibiting in the expo area to present our latest products and new releases including TX Text Control 30.0. |
| Learn more |
|
Text Control respects your online time and privacy. We only send this newsletter to customers and people who have signed up to receive it. However, if you would prefer not to receive future issues of the newsletter, you may unsubscribe at any time.
Unsubscribe | Privacy Policy | Imprint
|
|
