|
| 1 | +--- |
| 2 | +title: Handling the 'No packages found" Message when Using the Telerik NuGet Server |
| 3 | +description: Learn how to handle the 'No packages found" message when using the Telerik NuGet Server |
| 4 | +type: how-to |
| 5 | +page_title: How to handle the 'No packages found" message when using the Telerik NuGet Server |
| 6 | +slug: handle-no-nuget-packages-found-message |
| 7 | +tags: telerik, nuget, server, package, dpl, document, processing |
| 8 | +res_type: kb |
| 9 | +ticketid: 1672286 |
| 10 | +--- |
| 11 | + |
| 12 | +## Description |
| 13 | + |
| 14 | +When adding the Telerik NuGet source (https://nuget.telerik.com/v3/index.json) to a .NET 8 (WebApi) project in Visual Studio 2022, the expected Telerik NuGet packages do not appear in the Manage NuGet Packages window, even after entering the correct credentials. This knowledge base article also answers the following questions: |
| 15 | +- How can I ensure Telerik NuGet packages are visible in Visual Studio 2022? |
| 16 | +- What steps should I take if Telerik NuGet packages do not appear after adding the Telerik source? |
| 17 | +- How do I troubleshoot issues with adding Telerik NuGet packages to a .NET 8 project? |
| 18 | + |
| 19 | +## Solution |
| 20 | + |
| 21 | +To resolve the issue of Telerik NuGet packages not appearing in Visual Studio 2022 for a .NET 8 project, follow these steps: |
| 22 | + |
| 23 | +1. **Add Telerik NuGet Source Correctly**: Make sure the Telerik NuGet source is added correctly to Visual Studio 2022. The correct source URL is `https://nuget.telerik.com/v3/index.json`. Refer to the [official Telerik documentation](https://docs.telerik.com/devtools/document-processing/getting-started/installation/nuget-packages) for detailed instructions. |
| 24 | + |
| 25 | +2. **Enter Correct Credentials**: When prompted, enter the correct Telerik account credentials. Ensure you are using an account with an active subscription or trial. |
| 26 | + |
| 27 | +3. **Check for Multiple Accounts**: Verify if you have multiple Telerik accounts and ensure you are using the one with an active subscription. Packages may not appear if the account used has no active licenses. |
| 28 | + |
| 29 | +4. **Reset Telerik NuGet Credentials**: If you have verified the above steps and still face issues, try resetting your Telerik NuGet credentials. This ensures that Visual Studio is using the correct account for authentication. Instructions for resetting credentials can be found in the [Troubleshooting Telerik NuGet](https://docs.telerik.com/devtools/document-processing/troubleshooting/telerik-nuget#issue-resetting-telerik-nuget-credentials) guide. |
| 30 | + |
| 31 | +5. **Download Packages Manually (Optional)**: As a workaround, you can manually download the required Telerik NuGet packages and add them as a local source in Visual Studio. Detailed steps for manual download are provided in the [Manually Download NuGet Packages](https://docs.telerik.com/devtools/document-processing/getting-started/installation/install-nuget-packages#manually-download-nuget-packages) section. |
| 32 | + |
| 33 | +Ensure you follow these steps to add Telerik NuGet packages to your .NET 8 project successfully. |
| 34 | + |
| 35 | +## See Also |
| 36 | + |
| 37 | +- [Available NuGet Packages](https://docs.telerik.com/devtools/document-processing/getting-started/installation/nuget-packages) |
| 38 | +- [Install Using NuGet Packages](https://docs.telerik.com/devtools/document-processing/getting-started/installation/install-nuget-packages) |
| 39 | +- [Restoring NuGet Packages in Your CI Workflow](https://docs.telerik.com/devtools/document-processing/getting-started/installation/nuget-keys) |
| 40 | +- [Troubleshooting Telerik NuGet](https://docs.telerik.com/devtools/document-processing/troubleshooting/telerik-nuget) |
| 41 | + |
| 42 | +--- |
0 commit comments