Sync with Kendo UI Professional

Author: kendo-bot

docs-aspnet/_config-mvc.yml

@@ -14,7 +14,6 @@ bs-config.js,
 build-docs.sh,
 copy_content.sh,
 copy_local.sh,
-deployment/*,
 docs-watcher/*,
 exclude_files.txt,
 install-npm.sh,
@@ -63,7 +62,6 @@ knowledge-base/grid-toolbar-template.md,
 knowledge-base/invalid-template-error-when-using-localization.md,
 knowledge-base/multiselect-post-data-values.md,
 knowledge-base/scheduler-sql-server-database.md,
-knowledge-base/setup-private-nuget-feed-azure.md,
 knowledge-base/treelist-checkbox-column.md,
 knowledge-base/upload-resize-image-before-upload.md,
 knowledge-base/validator-basic-form-validation.md,

docs-aspnet/deployment/ci-cd-build-server.md

@@ -52,7 +52,7 @@ When using Azure pipelines, we encourage you to review the following resource on
 
 * That Service Connection is selected as the credentials source.
 
-* The credentials being used have a UI for ASP.NET Core license.
+* The credentials being used have a {{ site.product_short }} license.
 
 * Make sure that you use `dotnet restore` and not `nuget restore` in your pipeline step.
 

docs-aspnet/deployment/nuget-keys.md

@@ -2,6 +2,7 @@
 title: Restoring NuGet Packages in CI
 page_title: Restoring NuGet Packages in CI
 description: "Get started with {{ site.product }} and use NuGet Keys to authenticate with the Telerik NuGet server and restore packages in your CI or desktop environment."
+previous_url: /installation/nuget-keys
 slug: nuget_keys
 position: 10
 ---
@@ -55,7 +56,7 @@ There are two popular ways to use the Telerik NuGet server in a build:
 
 * [Using a nuget.config file with your projects](#using-a-nugetconfig-file-with-your-projects)
 
-* [Using only CLI commands](#using-only-cli-commands)
+* [Using only CLI commands](#using-only-cli-commands) (requires .NET Core 3.1 SDK or newer)
 
 For more information on how to use NuGet keys in a build, check the [Announcing NuGet Keys](https://www.telerik.com/blogs/announcing-nuget-keys) blog post by Lance McCarthy.
 
@@ -86,7 +87,7 @@ The exact steps to set the `MY_API_KEY` environment variable depend on your work
 
 ### Using Only CLI Commands
 
-You can use the CLI `add source` (or `update source`) command to set the credentials of a package source. This CLI approach is applicable if your CI system doesn't support default environment variable secrets or if you do not use a custom `nuget.config`.
+You can use the CLI `add source` (or `update source`) command to set the credentials of a package source. This CLI approach is applicable if your CI system doesn't support default environment variable secrets or if you do not use a custom `nuget.config`. Using the CLI requires installing .NET Core 3.1 SDK or newer. 
 
 * To set the credentials in Azure DevOps:
 
@@ -110,8 +111,8 @@ If you just start using the Telerik NuGet server in your CI or inter-department
 
 ## See Also
 
-* [Set Up Private NuGet Feed for Azure](https://docs.telerik.com/aspnet-core/knowledge-base/setup-private-nuget-feed-azure)
+* [Set Up Private NuGet Feed for Azure](https://docs.telerik.com/{{ site.platform }}/knowledge-base/setup-private-nuget-feed-azure)
 
 * [Including Client-Side Resources]({% slug copyclientresources_aspnetmvc6_aspnetmvc %})
 
-* [Scaffolding the Telerik UI for ASP.NET Core Project]({% slug scaffolding_aspnetcore %})
+* [Scaffolding the {{ site.product }} Project]({% slug scaffolding_aspnetcore %})

docs-aspnet/deployment/overview.md

@@ -1,14 +1,14 @@
 ---
 title: Overview
 page_title: Deployment Overview
-description: Troubleshooting deployment issues involving the UI for ASP.NET Core suite.
+description: Troubleshooting deployment issues involving the {{ site.product_short }} suite.
 slug: deployment_overview
 position: 0
 ---
 
 # {{ site.product }} Deployment Overview
 
-This article explains the basics about deploying a UI for ASP.NET Core web application. It consists of the following sections:
+This article explains the basics about deploying a {{ site.product_short }} web application. It consists of the following sections:
 
 
 * [Prerequisites](#prerequisites)
@@ -20,14 +20,17 @@ This article explains the basics about deploying a UI for ASP.NET Core web appli
 
 First, make sure you can deploy an ASP.NET Core application without the Telerik components in order to have the entire pipeline working as a baseline.
 
-You can read more about deploying ASP.NET Core applications in MSDN - make sure that you are familiar with this information, as the Telerik UI for ASP.NET Core suite does not add any specific requirements or steps:
-
-* [Host and deploy ASP.NET Core](https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/?view=aspnetcore-5.0)
+You can read more about deploying {{ site.framework }} applications in MSDN - make sure that you are familiar with this information, as the {{ site.product }} suite does not add any specific requirements or steps:
 
+{% if site.core %}
+* [Host and deploy ASP.NET Core](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/?view=aspnetcore-9.0)
+{% else %}
+* [Host and deploy ASP.NET MVC](https://learn.microsoft.com/en-us/aspnet/mvc/overview/deployment/)
+{% endif %}
 
 ## Telerik Components
 
-The Telerik UI for ASP.NET Core components consist of:
+The {{ site.product }} components consist of:
 * assembly - it is distributed through [NuGet]({%slug nuget_install_aspnetmvc6_aspnetmvc%}). You could find the list with the packages related to UI for ASP.NET Core [here]({% slug nuget_install_aspnetmvc6_aspnetmvc%}#list-of-provided-packages)
 * [client-side resources]({%slug copyclientresources_aspnetmvc6_aspnetmvc%}) - the required JavaScript and CSS files needed to run the components
 

docs-aspnet/deployment/troubleshooting.md

@@ -1,22 +1,22 @@
 ---
 title: Deployment Troubleshooting
 page_title: Deployment Troubleshooting
-description: Troubleshooting deployment issues involving the UI for ASP.NET Core suite.
+description: Troubleshooting deployment issues involving the {{ site.product_short }} suite.
 slug: deployment_troubleshooting
 position: 20
 ---
 
 # Deployment Troubleshooting
 
-This page provides information for common issues you may encounter while deploying applications with the UI for ASP.NET Core components.
+This page provides information for common issues you may encounter while deploying applications with the {{ site.product_short }} components.
 
 
 >important The machine that performs the publish build must be able to properly restore the referenced Telerik NuGet packages. See the [CI, CD, Build Server]({%slug deployment_ci_cd_build%}) article for more details on setting automation up.
 
 
 ### Trial Message
 
-`Trial Message` - Such behavior will occur if there is a reference to the UI for ASP.NET Core Trial version left in the application. Make sure that the trial version is removed from the release build pipeline. Follow the steps described in the [Switching to a Developer License]({%slug upgrade_aspnetcore%}#switching-to-a-developer-license) article.
+`Trial Message` - Such behavior will occur if there is a reference to the {{ site.product_short }} Trial version left in the application. Make sure that the trial version is removed from the release build pipeline. Follow the steps described in the [Switching to a Developer License]({%slug upgrade_aspnetcore%}#switching-to-a-developer-license) article.
 
 
 ## See Also

docs-aspnet/installation/nuget-keys.md

@@ -1,10 +1,10 @@
 ---
 title: Setting Up a Private NuGet Feed for Azure
-description: An example on how to set up the private NuGet feed in Azure to publish an ASP.NET Core application that references the Telerik UI for ASP.NET Core assembly.
+description: An example on how to set up the private NuGet feed in Azure to publish an {{ site.framework }} application that references the {{ site.product }} assembly.
 page_title: Set Up Private NuGet Feed for Azure
 type: how-to
 slug: howto_setupprivatefeedazure_aspnetcore
-tags: aspnet, core, nuget, azure
+tags: aspnet, core, mvc, nuget, azure, artifacts
 res_type: kb
 ---
 
@@ -19,7 +19,7 @@ res_type: kb
 
 ## Description
 
-How can I set up the private NuGet feed in Azure to publish an ASP.NET Core application that references the Telerik UI for ASP.NET Core package?
+How can I set up the private NuGet feed in Azure to publish an {{ site.framework }} application that references the {{ site.product }} package?
 
 ## Solution
 
@@ -108,9 +108,14 @@ If you do not want pipelines to have unfettered access to the Telerik account ho
 
 1. You can get the NuGet package file (nupkg) for any Telerik product you're using by going to the downloads page for that product. You can start at the [My Account - Downloads](https://www.telerik.com/account/my-downloads) page.
 
-1. Underneath the installer for the product, you will find the *Other Setup Files* section where the nupkg files will be. For example, here's what it looks like for the [Telerik UI for ASP.NET Core](https://docs.telerik.com/aspnet-core/introduction) packages.
+1. Select the {{ site.product }} product.
 
+1. Underneath the installer for the product, you will find the *Other Setup Files* section where the nupkg files will be. For example, here's what it looks like for the {{ site.product }} packages.
+    {% if site.core %}
     ![{{ site.product_short }} Download nupkg file](images/download-nupkg-file.png)
+    {% else %}
+    ![{{ site.product_short }} Download nupkg file](images/download-nupkg-file-mvc.png)
+    {% endif %}
 
 1. Go to the build pipeline and select that feed for a NuGet Restore step.