Merge pull request #557 from telerik/yoan/nuget-v2-kb

Extracted NuGet v2 warning in a KB

Author: dessyordanova

getting-started/Installation/install-nuget-packages.md

@@ -46,8 +46,6 @@ This article describes how you can install the Document Processing Libraries usi
 
 Before you can install Telerik NuGet packages, you must configure the Telerik NuGet server (https://nuget.telerik.com/v3/index.json) as a package source in Visual Studio:
 
->caution The old **https://nuget.telerik.com/nuget** server is deprecated and we encourage our clients to switch to the v3 API. The new v3 API is faster, lighter, and reduces the number of requests from NuGet clients. The **NuGet v2** server at https://nuget.telerik.com/nuget will be sunset in **November 2024**. The new v3 protocol offers faster package searches and restores, improved security, and more reliable infrastructure. To redirect your feed to the NuGet v3 protocol, all you have to do is to change your NuGet package source URL to https://nuget.telerik.com/v3/index.json.  
-
 1\. In the Visual Studio Solution Explorer, right-click a Project, select **Manage NuGet Packages...**, and then select the **Settings** icon:
 
 ![installation-nuget-packages 001](images/installation-nuget-packages001.png)

getting-started/Installation/nuget-packages.md

@@ -12,9 +12,7 @@ position: 6
 
 Telerik provides NuGet packages with the assemblies for all five Document Processing libraries: __RadPdfProcessing__, __RadSpreadProcessing__, __RadSpreadStreamProcessing__, __RadWordsProcessing__, and __RadZipLibrary__. These UI-independent cross-platform libraries enable you to process and convert content in various formats and even work with archive files. We deliver these libraries as a complement to the Telerik UI component suites (UI for ASP.NET, Kendo UI, UI for WPF, UI for WinForms, UI for Xamarin, UI for Blazor), and you don't need to purchase an additional license to use them.
 
-If your workflow relies on NuGet for package management, you can take advantage of the packages that we describe in this article. There is no need to download and install the Document Processing libraries by using other methods.
-
->caution The old **https://nuget.telerik.com/nuget** server is deprecated and we encourage our clients to switch to the v3 API. The new v3 API is faster, lighter, and reduces the number of requests from NuGet clients. The **NuGet v2** server at https://nuget.telerik.com/nuget will be sunset in **November 2024**. The new v3 protocol offers faster package searches and restores, improved security, and more reliable infrastructure. To redirect your feed to the NuGet v3 protocol, all you have to do is to change your NuGet package source URL to https://nuget.telerik.com/v3/index.json.  
+If your workflow relies on NuGet for package management, you can take advantage of the packages that we describe in this article. There is no need to download and install the Document Processing libraries by using other methods. 
 
 #### This article contains the following sections:
 

getting-started/first-steps.md

@@ -21,8 +21,6 @@ Since we distribute Telerik Document Processing libraries as an addition to seve
 
 >tipRegardless of the Telerik UI components suite that you use, you can always get the Document Processing assemblies as NuGet packages from the [Telerik NuGet server]({%slug installation-nuget-packages%}).
 
->caution The old **https://nuget.telerik.com/nuget** server is deprecated and we encourage our clients to switch to the v3 API. The new v3 API is faster, lighter, and reduces the number of requests from NuGet clients. The **NuGet v2** server at https://nuget.telerik.com/nuget will be sunset in **November 2024**. The new v3 protocol offers faster package searches and restores, improved security, and more reliable infrastructure. To redirect your feed to the NuGet v3 protocol, all you have to do is to change your NuGet package source URL to https://nuget.telerik.com/v3/index.json.  
-
 | UI Components suite | Installation instructions | Default location of the Document Processing assemblies |
 |--------------------|---------------------------|------------------------------------------------|
 | UI for ASP.NET AJAX | [Installing Telerik UI for ASP.NET AJAX](http://docs.telerik.com/devtools/aspnet-ajax/installation/which-file-do-i-need-to-install) | <ul><li>`C:\Program Files (x86)\Progress\Telerik UI for ASP.NET AJAX [version]\AdditionalLibraries\Bin40`</li><li>`C:\Program Files (x86)\Progress\Telerik UI for ASP.NET AJAX [version]\AdditionalLibraries\Bin45`</li></ul> |

knowledge-base/nuget-v2-server-deprecation.md

@@ -0,0 +1,42 @@
+---
+title: Telerik NuGet v2 Server Deprecation
+description: Learn how to migrate from Telerik's deprecated NuGet v2 server to the new v3 API endpoint
+type: how-to
+page_title: Telerik NuGet v2 Server Deprecation
+slug: nuget-v2-server-deprecation
+tags: telerik, nuget, server, v2, v3, api, deprecation, migration, document, processing
+res_type: kb
+---
+
+## Environment
+
+| Version | Product | Author | 
+| --- | --- | ---- | 
+| All versions | Document Processing Libraries |[Yoan Karamanov](https://www.telerik.com/blogs/author/yoan-karamanov)| 
+
+## Description
+
+Since **November 2024**, the old **NuGet v2** server at `https://nuget.telerik.com/nuget` is decommissioned. To reflect this change you need to migrate to the new **NuGet v3** API (https://nuget.telerik.com/v3/index.json) endpoint. For more details, head to the [Sunsetting the NuGet v2 Server](https://www.telerik.com/blogs/sunsetting-nuget-v2-server) blog.
+
+### Why migrate to NuGet v3?
+
+The new v3 API offers several advantages:
+- Faster package searches and restores
+- Reduced number of requests from NuGet clients
+- Improved security
+- More reliable infrastructure
+- Lighter resource consumption
+
+### How to redirect your feed?
+
+1. Open your NuGet configuration (Visual Studio NuGet Package Manager, nuget.config file, or CI/CD pipeline configuration).
+2. Change your Telerik NuGet package source URL from https://nuget.telerik.com/nuget to https://nuget.telerik.com/v3/index.json.
+   
+No other changes are required. Your authentication credentials will continue to work with the new endpoint.
+
+## See Also
+
+- [Install using NuGet Packages]({%slug installation-nuget-packages%})
+- [Available NuGet Packages]({%slug available-nuget-packages%})
+- [Troubleshooting Telerik NuGet]({%slug dpl-troubleshooting-nuget%})
+- [Restoring NuGet Packages in Your CI Workflow]({%slug using-nuget-keys%})