# Deploying .NET Framework Applications > Deploy a .NET Framework Windows Forms app with TX Text Control: Assembly, bin and bin64 files in the application folder, native DLLs as content, ClickOnce. - **Product:** TX Text Control .NET for Windows Forms - **Section:** Documentation - **Kind:** Topic - **Path:** TX Text Control .NET for Windows Forms > Deployment Guide > Deploying .NET Framework Applications - **1079 words** - **Web URL:** https://docs.textcontrol.com/tx-text-control-dotnet-winforms/deployment/dotnet-framework/ - **LLMs URL:** https://docs.textcontrol.com/tx-text-control-dotnet-winforms/deployment/dotnet-framework/llms.txt - **LLMs-Full URL:** https://docs.textcontrol.com/tx-text-control-dotnet-winforms/deployment/dotnet-framework/llms-full.txt --- A .NET Framework application references the assemblies that the setup of TX Text Control .NET for Windows Forms installed, and no publish step gathers the files of TX Text Control for you. You copy them yourself: the managed assemblies from the *Assembly* folder of the installation and the native libraries of your platform from *Assembly\\bin* or *Assembly\\bin64*. Below are the files, the folder rule and two ways to get them into your deployment, including ClickOnce. ### Where the Files Are The setup installs TX Text Control into *C:\\Program Files\\Text Control GmbH\\TX Text Control 34.0.NET for Windows Forms* by default. Below that folder: | Folder | Contains | Deploy it for | |---|---|---| | *Assembly* | The managed assemblies, such as *TXTextControl.dll*, *TXTextControl.Windows.Forms.dll*, *TXTextControl.Server.dll* and *TXDocumentServer.dll* | Every application | | *Assembly\\bin* | The 32-bit native libraries | x86 builds, and AnyCPU builds on 32-bit Windows | | *Assembly\\bin64* | The 64-bit native libraries | x64 builds, and AnyCPU builds on 64-bit Windows | [Managed Assemblies and Native Libraries](https://docs.textcontrol.com/tx-text-control-dotnet-winforms/deployment/assemblies/llms-full.txt) lists the files. The requirements documentation of TX Text Control names the native libraries of an older version; take the names from the *bin* folders of your installation. ### Put All Files Into the Application Folder All files of TX Text Control must be in the application's root folder, at the same level as the executable. If your application is installed as *C:\\Program Files\\My Application\\My Application.exe*, the managed assemblies and the native libraries go into *C:\\Program Files\\My Application*. 1. Copy the managed assemblies from the *Assembly* folder of the installation. 2. Copy the native libraries of your platform: *Assembly\\bin* for x86, *Assembly\\bin64* for x64. For AnyCPU, the set depends on the bitness of the target machine; see [x86, x64, and AnyCPU](https://docs.textcontrol.com/tx-text-control-dotnet-winforms/deployment/x86-x64-anycpu/llms-full.txt). 3. Put everything next to the executable, not into subfolders. 4. Make sure the target machine has the Visual C++ runtime of the same bitness; see [Visual C++ Runtime Dependencies](https://docs.textcontrol.com/tx-text-control-dotnet-winforms/deployment/vc-runtime/llms-full.txt). The license needs no file of its own: the license compiler embedded it into your executable from *licenses.licx* when you built the application. See [Application Licensing](https://docs.textcontrol.com/tx-text-control-dotnet-winforms/deployment/licensing/llms-full.txt). ### Add the Native Libraries to the Project When your installer or deployment takes the files from the build output, add the native libraries to the project, so that each build copies them: 1. Select the project in **Solution Explorer**, and choose **Project** > **Add Existing Item**. 2. Browse to *Assembly\\bin* or *Assembly\\bin64* of the installation, select all files and add them. 3. Select the added files in **Solution Explorer**, set **Build Action** to **Content** and **Copy to Output Directory** to **Copy always**. The build output now contains the assemblies and the native libraries side by side. After an update to a new major version, replace the added files, because the names of the native libraries contain the version. ### Deploy With ClickOnce With ClickOnce, users install your application from a link on a website, and updates you publish to the server reach them automatically. ClickOnce publishes the files the project contains, so the native libraries must be added as described in the previous section. Then: 1. Open the project's properties. 2. On the **Signing** page, select **Sign the ClickOnce manifests**. Visual Studio creates a test certificate when you publish, unless you select a certificate of your own. 3. On the **Security** page, enable the ClickOnce security settings and select **This is a full trust application**. 4. On the **Publish** page, click **Application Files**, and make sure the **Publish Status** of all files is **Include**. 5. Publish the application with the **Publish Wizard** or **Publish Now**. The blog article [Deploying TX Text Control .NET Applications Using ClickOnce](https://www.textcontrol.com/blog/2011/03/24/deploying-tx-text-control-net-applications-using-clickonce/) shows these steps with screenshots of an earlier version of Visual Studio. ### Move to .NET A .NET 8 or higher application gets all files of TX Text Control from the NuGet package, and Visual Studio's publish copies them for the target runtime. [Migrating from .NET Framework to .NET](https://docs.textcontrol.com/tx-text-control-dotnet-winforms/installation/upgrading/from-dotnet-framework/llms-full.txt) describes the move, and [Publishing .NET Applications](https://docs.textcontrol.com/tx-text-control-dotnet-winforms/deployment/dotnet/llms-full.txt) the deployment afterward. ### Related Pages - [Redistribution Overview](https://docs.textcontrol.com/tx-text-control-dotnet-winforms/deployment/redistribution/llms-full.txt): what ships and what never ships. - [Files Are Missing After Deploying a .NET Framework Application](https://docs.textcontrol.com/tx-text-control-dotnet-winforms/troubleshooting/deployment/#files-are-missing-after-deploying-a-net-framework-application): what to check on the target machine. - [Create a .NET Framework Application](https://docs.textcontrol.com/tx-text-control-dotnet-winforms/getting-started/document-editor/dotnet-framework/llms-full.txt): the tutorial for a .NET Framework project. --- ## Nearby - **Previous:** [Publishing .NET Applications](https://docs.textcontrol.com/tx-text-control-dotnet-winforms/deployment/dotnet/llms-full.txt) - **Next:** [Application Licensing](https://docs.textcontrol.com/tx-text-control-dotnet-winforms/deployment/licensing/llms-full.txt)