# Breaking Changes

> Upgrading WPF apps to TX Spell .NET 11.0 changes projects, not code: target frameworks, and what to test in suggestions and user dictionaries by version.

- **Product:** TX Spell .NET for WPF
- **Section:** Documentation
- **Kind:** Topic
- **Path:** TX Spell .NET for WPF > Installation Guide > Upgrade Guide > Breaking Changes
- **437 words**
- **Web URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/upgrading/breaking-changes/
- **LLMs URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/upgrading/breaking-changes/llms.txt
- **LLMs-Full URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/upgrading/breaking-changes/llms-full.txt

---

The What's New notes of versions 7.0 to 11.0 list no member of TX Spell .NET for WPF that was changed or removed, and none is marked obsolete. An upgrade therefore changes your project, not your code, plus a few behaviors worth testing. The table below gives the short answer for the version you come from; [Breaking Changes](https://docs.textcontrol.com/tx-spell-dotnet-wpf/whats-new/breaking-changes/llms-full.txt) in What's New describes each change in full.

### By the Version You Come From

| You come from | Change in the project | Test |
|---|---|---|
| 10.0 | Target .NET 8 or higher, then update the package to 11.0.1 | Nothing new |
| 9.0 or 8.0 | Update the references, or switch to the package | Suggestions: since 10.0, dictionaries with replacement rules suggest correct forms for words typed without their accents or spelled phonetically |
| 7.0 | Update the references | The suggestions, and user dictionaries that start with the flags `WORDCHARS`, `BREAK` or `ICONV`, which TX Spell .NET applies since 8.0 |
| Earlier than 7.0 | Target the .NET Framework 4.5 or higher, then update the references | Everything above |

[Changes That Require Work](https://docs.textcontrol.com/tx-spell-dotnet-wpf/whats-new/breaking-changes/#changes-that-require-work) and [Behavior Changes to Test](https://docs.textcontrol.com/tx-spell-dotnet-wpf/whats-new/breaking-changes/#behavior-changes-to-test) have the details, and [Deprecated APIs](https://docs.textcontrol.com/tx-spell-dotnet-wpf/whats-new/deprecated-apis/llms-full.txt) confirms that nothing is marked for removal.

### When You Upgrade TX Text Control Too

An upgrade of both products brings the changes of both; [Update Together With TX Text Control](https://docs.textcontrol.com/tx-spell-dotnet-wpf/whats-new/breaking-changes/#update-together-with-tx-text-control) pairs the versions and links the breaking changes of TX Text Control .NET for WPF.

### Related Pages

- [Upgrading from Previous Versions](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/upgrading/previous-versions/llms-full.txt): the steps for .NET Framework and .NET projects.
- [Breaking Changes](https://docs.textcontrol.com/tx-spell-dotnet-wpf/whats-new/breaking-changes/llms-full.txt): every change in full, with links to the version pages.
- [Service Packs](https://docs.textcontrol.com/tx-spell-dotnet-wpf/whats-new/service-packs/llms-full.txt): the service packs of each version.

---

## Nearby

- **Previous:** [Migrating From .NET Framework to .NET](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/upgrading/from-dotnet-framework/llms-full.txt)
- **Next:** [Getting Started](https://docs.textcontrol.com/tx-spell-dotnet-wpf/getting-started/llms-full.txt)