# Configuring Package Sources

> Point NuGet at TX Spell .NET for WPF: the Offline Packages folder of the setup, the private feed for TXSpell.WPF.SDK with an API token, or nuget push to a feed.

- **Product:** TX Spell .NET for WPF
- **Section:** Documentation
- **Kind:** Topic
- **Path:** TX Spell .NET for WPF > Installation Guide > NuGet Packages > Configuring Package Sources
- **1414 words**
- **Web URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/nuget/sources/
- **LLMs URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/nuget/sources/llms.txt
- **LLMs-Full URL:** https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/nuget/sources/llms-full.txt

---

The NuGet packages of TX Spell .NET for WPF are not published on nuget.org, so NuGet has to know where to find them. On a development machine, the setup takes care of this; a build server or a pipeline needs a source of its own. Three sources are possible, and a project can use any of them.

### Which Source to Use

| Source | Where it is | Use it for |
|---|---|---|
| **Text Control Offline Packages** | A folder on your development machine, added by the setup | Development in Visual Studio |
| **Text Control Private NuGet Feed** | `https://www.textcontrol.com/nuget/v3/index.json`, with your email address and an API token | Build servers and CI/CD pipelines |
| Your own feed | For example Azure Artifacts, with the packages copied from the offline folder | Build systems in your organization |

### Text Control Offline Packages

The setup of TX Spell .NET, the full or the trial version, adds the package source **Text Control Offline Packages** to NuGet. It holds the packages of all Text Control products installed on the machine, so TX Spell .NET and TX Text Control share it. In Visual Studio, select it in the **Package source** list of the NuGet Package Manager; [Installing and Updating Packages](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/nuget/install-update/llms-full.txt) shows the steps.

For builds with the .NET CLI on the same machine, name the folder of the source in a *nuget.config* file next to the solution. The setups of Text Control install the packages in *C:\\Program Files (x86)\\Text Control GmbH\\NuGetPackages*:

```xml
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="Text Control Offline Packages" value="C:\Program Files (x86)\Text Control GmbH\NuGetPackages" />
  </packageSources>
</configuration>
```

Without a `<clear />` element, nuget.org stays available for the other packages of the project.

### Text Control Private NuGet Feed

The private feed serves the packages of the products your license covers, with the license already inside: for TX Spell .NET for WPF, `TXTextControl.TXSpell.WPF.SDK`. `TXTextControl.TXSpell.Core.SDK` comes from the offline source of the setup. After a service pack, the feed has the new versions.

To use the feed:

1. The owner of your Text Control account assigns your serial number to you under **Manage Products**, with your email address.
2. You receive an email with a link to your personal *nuget.config*. The API token in it is created for you and is valid for 365 days; further tokens are created under **Manage API tokens**.
3. Put the *nuget.config* next to the solution. It looks like this, with your email address and your token:

    ```xml
    <?xml version="1.0" encoding="utf-8"?>
    <configuration>
      <packageSources>
        <clear />
        <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
        <add key="TextControl" value="https://www.textcontrol.com/nuget/v3/index.json" />
      </packageSources>
      <packageSourceCredentials>
        <TextControl>
          <add key="Username" value="you@example.com" />
          <add key="ClearTextPassword" value="YOUR-API-TOKEN" />
        </TextControl>
      </packageSourceCredentials>
    </configuration>
    ```
4. In Visual Studio, the source appears as **TextControl** in the NuGet Package Manager.

- **Keep the file out of source control.** It contains your credentials. On a build server, store the email address and the token as secrets and write the file during the build.
- **If Visual Studio doesn't pick up the file,** open **Tools** > **NuGet Package Manager** > **Package Manager Settings** > **Configuration Files** and replace the contents of your configuration file with it.

The blog article [Text Control Private NuGet Feed](https://www.textcontrol.com/blog/2026/02/09/text-control-private-nuget-feed/) describes the feed and its tokens in detail. [Build Servers](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/licensing/build-servers/llms-full.txt) covers pipelines.

### Your Own Feed

An organization that runs its own feed, such as Azure Artifacts, can push the packages from the offline folder into it with `nuget push`, and point its builds at that feed. The blog article [Azure Pipelines with TX Text Control .NET for WPF and Windows Forms 32.0 with Azure DevOps and Artifacts](https://www.textcontrol.com/blog/2024/01/05/azure-pipelines-with-tx-text-control-net-for-wpf-and-windows-forms-320-with-azure-devops-and-artifacts/) shows the approach for TX Text Control; the packages of TX Spell .NET are pushed the same way.

### Related Pages

- [Installing and Updating Packages](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/nuget/install-update/llms-full.txt): install a package from the source.
- [Installation and Package Restore](https://docs.textcontrol.com/tx-spell-dotnet-wpf/troubleshooting/installation/llms-full.txt): when the package isn't found.
- [Installing the Product](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/setup/llms-full.txt): the setup that adds the offline source.

---

## Nearby

- **Previous:** [Package Overview](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/nuget/packages/llms-full.txt)
- **Next:** [Installing and Updating Packages](https://docs.textcontrol.com/tx-spell-dotnet-wpf/installation/nuget/install-update/llms-full.txt)