# Windows Versions

> WPF apps with TX Spell .NET run on Windows 10 and 11, TXTextControl.TXSpell.Core.SDK on Linux too; a target runtime like win-x64 only with TX Text Control.

- **Product:** TX Spell .NET for WPF
- **Section:** Documentation
- **Kind:** Topic
- **Path:** TX Spell .NET for WPF > Installation Guide > System Requirements > Windows Versions
- **565 words**
- **Web URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/requirements/windows/
- **LLMs URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/requirements/windows/llms.txt
- **LLMs-Full URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/requirements/windows/llms-full.txt

---

You develop with TX Spell .NET for WPF on Windows, and a WPF application that uses it runs on Windows. The spell checking engine itself is not tied to Windows: its assemblies are managed code without native libraries, and in code without a user interface it also runs on Linux.

### Windows for Development

The setup of TX Spell .NET for WPF 11.0 is a Windows installer, and Visual Studio with the WPF designer runs on Windows. Develop on one of these versions:

- Windows 10
- Windows 11

Older documentation of TX Spell .NET also lists Windows 7 and Windows 8. .NET 8, which the packages of version 11.0 require, doesn't support them.

### Where Your Application Runs

| Application | Runs on |
|---|---|
| WPF application with `TXTextControl.TXSpell.WPF.SDK` | Windows, like every WPF application |
| .NET Framework application with the assemblies of the setup | Windows |
| Application with `TXTextControl.TXSpell.Core.SDK` and no user interface | Windows and Linux |

TX Spell .NET needs no additional Windows components at run time: the packages contain managed assemblies only, and no native libraries or runtimes. Next to the application, it needs its language data folders, which the packages copy when you build.

### Publishing With and Without TX Text Control

When you publish an application that uses TX Spell .NET together with TX Text Control, select a target runtime in the publish profile, such as `win-x64`, because TX Text Control brings native libraries for a platform. Without TX Text Control, TX Spell .NET is platform-independent, and you can publish without a target runtime.

![The publish profile settings of Visual Studio with the Target runtime list open, showing linux-x64 and win-x64 among the runtimes, and the target framework net8.0.](https://docs.textcontrol.com/assets/img/tx-spell-dotnet-wpf/publish-target-runtime.badc1dc3.webp)

The `linux-x64` runtime applies to server applications, such as an ASP.NET Core application with the Document Editor of TX Text Control .NET Server. The blog article [Document Editor with TX Spell .NET on Linux using ASP.NET Core](https://www.textcontrol.com/blog/2026/01/28/document-editor-tx-spell-net-linux-aspnet-core/) shows such an application in a Linux container.

The build reports CA1416 warnings for the `TXSpell` class, which say that its methods are supported on Windows. They don't stop an application on Linux, as [Checking Text in Code](https://docs.textcontrol.com/tx-spell-dotnet-wpf/getting-started/in-code/#run-the-application) explains.

### Next Steps

- [.NET and .NET Framework](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/requirements/dotnet/llms-full.txt): the frameworks and how TX Spell .NET gets into a project.
- [Visual Studio](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/requirements/visual-studio/llms-full.txt): the Visual Studio version and the project templates.
- [Redistribution Overview](https://docs.textcontrol.com/tx-spell-dotnet-wpf/deployment/redistribution/llms-full.txt): the files you ship with your application.

---

## Nearby

- **Previous:** [.NET and .NET Framework](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/requirements/dotnet/llms-full.txt)
- **Next:** [Visual Studio](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/requirements/visual-studio/llms-full.txt)