# Windows > Deploy TX Text Control .NET Server applications to Windows Server: both engines, win-x64 publishing, the runtime and hosting in IIS or as a Windows service. - **Product:** TX Text Control .NET Server - **Section:** Documentation - **Kind:** Topic - **Path:** TX Text Control .NET Server > Deployment Guide > Windows - **742 words** - **Web URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/windows/ - **LLMs URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/windows/llms.txt - **LLMs-Full URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/windows/llms-full.txt --- Windows servers run both engines of TX Text Control .NET Server: the Core engine, which also runs on Linux, and the Classic engine, which uses the graphics and fonts of Windows. An application for Windows is published for 64-bit Windows and hosted either in IIS or as a Windows service, and in both cases the Document Editor backend runs as a separate process next to it. ### What a Windows Server Needs - **A supported version.** The requirements documentation lists Windows 10, Windows 11, Windows Server 2019, Windows Server 2022 and Windows Server 2025 for deployment. See [Operating Systems](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/requirements/operating-systems/llms-full.txt). - **The .NET runtime.** A web application in IIS needs the .NET Hosting Bundle, a worker service the .NET Runtime. `DocumentEditorWorkerManager` starts the Document Editor backend with the 64-bit `dotnet` runtime it locates on the machine, so the 64-bit runtime must be installed on the server. - **The Microsoft Visual C++ Redistributable** for Visual Studio 2017, 2019 and 2022, x64. - **An application published for `win-x64`.** The output contains the TX Text Control assemblies with their native Windows libraries and, for the Core engine, the *Fonts* folder. - **Fonts for the Classic engine.** Classic uses the fonts installed on Windows, and newer systems such as Windows Server 2025 often don't come with a full set. The Core engine brings its own fonts. - **A runtime license** for each server. See [Runtime Licenses](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/licensing/runtime/llms-full.txt). ### Choose How the Application Runs | Hosting | Choose it when | Read | |---|---|---| | IIS | Your application is a web application with the Document Editor or the Document Viewer, and your servers run IIS | [IIS](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/windows/iis/llms-full.txt) | | Windows service | Documents are processed in the background, a web application runs without IIS or the Document Editor backend runs on a machine of its own | [Windows Service](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/windows/windows-service/llms-full.txt) | | Azure App Service on Windows | The application runs in Azure instead of on your own servers | [Azure App Service Windows](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/azure/app-service-windows/llms-full.txt) | | IIS, deployed by hand | Your application is a legacy ASP.NET MVC or Web Forms application on the .NET Framework that references the assemblies of the setup | [.NET Framework Applications](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/windows/dotnet-framework/llms-full.txt) | ### Where to Start 1. [IIS](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/windows/iis/llms-full.txt): install IIS with the WebSocket Protocol and the Hosting Bundle, and configure the application pool for the Document Editor backend. 2. [Windows Service](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/windows/windows-service/llms-full.txt): for background processing and applications without IIS. 3. [WebSocket Architecture](https://docs.textcontrol.com/tx-text-control-dotnet-server/integration/websockets/llms-full.txt): the connection of the Document Editor through IIS, proxies and load balancers. 4. [Troubleshooting IIS](https://docs.textcontrol.com/tx-text-control-dotnet-server/troubleshooting/iis/llms-full.txt): when the application or the editor doesn't start. Applications on the .NET Framework are deployed differently: you copy the TX Text Control files from the setup into the *bin* folder, choose between the 32-bit and 64-bit files and, for the Document Editor, install the TX TextControl Service. [.NET Framework Applications](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/windows/dotnet-framework/llms-full.txt) describes these steps, including the x86 Visual C++ Redistributable that a 32-bit build needs. --- ## In This Section - [.NET Framework Applications](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/windows/dotnet-framework/llms-full.txt): Deploy ASP.NET MVC and Web Forms apps on the .NET Framework by hand: the bin and bin64 files, Copy Local, VC++ runtime, MSXML and the TX TextControl Service. - [IIS](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/windows/iis/llms-full.txt): Host an ASP.NET Core app with TX Text Control in IIS: Hosting Bundle, win-x64 publish, a 64-bit application pool and settings for the Document Editor backend. - [Windows Service](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/windows/windows-service/llms-full.txt): Run TX Text Control in a Windows service: a worker that converts documents with ServerTextControl, installation, paths, fonts, logging and the editor backend. --- ## Nearby - **Previous:** [Deployment Guide](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/llms-full.txt) - **Next:** [IIS](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/windows/iis/llms-full.txt)