# Windows Versions

> Develop Windows Forms spell checking on Windows 10 or 11, run the Core package on Linux, and publish with or without a target runtime such as win-x64.

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

---

You develop with TX Spell .NET for Windows Forms on Windows, and a Windows Forms 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 Windows Forms 11.0 is a Windows installer, and Visual Studio with the Windows Forms 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 |
|---|---|
| Windows Forms application with `TXTextControl.TXSpell.WinForms.SDK` | Windows, like every Windows Forms 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

An application that uses TX Spell .NET together with TX Text Control is published with a target runtime, 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 needs no target runtime. [Publishing .NET Applications](https://docs.textcontrol.com/tx-spell-dotnet-winforms/deployment/dotnet/llms-full.txt) shows the setting, and [TX Text Control .NET Server Document Editor](https://docs.textcontrol.com/tx-spell-dotnet-winforms/integration/document-editor/#linux-and-docker) the `linux-x64` runtime of a server application.

### Next Steps

- [.NET and .NET Framework](https://docs.textcontrol.com/tx-spell-dotnet-winforms/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-winforms/installation/requirements/visual-studio/llms-full.txt): the Visual Studio version and the project templates.
- [Redistribution Overview](https://docs.textcontrol.com/tx-spell-dotnet-winforms/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-winforms/installation/requirements/dotnet/llms-full.txt)
- **Next:** [Visual Studio](https://docs.textcontrol.com/tx-spell-dotnet-winforms/installation/requirements/visual-studio/llms-full.txt)