Sync with Kendo UI Professional

Author: kendo-bot

docs-aspnet/html-helpers/helper-basics/using-client-templates.md

@@ -16,6 +16,7 @@ The available template types are:
 
 * [Inline Client Templates](#inline-client-templates)
 * [External Client Templates](#external-client-templates)
+* [Partial Client Templates](#partial-client-templates)
 * [Content Security Policy Templates](#content-security-policy-csp-templates)
 
 
@@ -216,6 +217,76 @@ For example, you can define an external client template for a [Grid column]({% s
 
 
 Also, you can integrate Telerik UI for {{ site.framework }} components in the external client templates by using the [HTML Helpers](#adding-html-helpers-inside-external-client-templates) {% if site.core %}or [Tag Helpers](adding-tag-helpers-inside-external-client-templates){% endif %}.
+## Partial Client Templates
+
+As of the R1 SP1 2023 release, the majority of the Telerik UI for {{ site.framework }} components expose the ability to include arbitrary client template content within the boundaries of a Partial View by using the respective component's new `TemplateView` method.
+
+The example below illustrates how to incorporate the Grid Toolbar's template content within a Partial View.
+
+```HtmlHelper
+    @(Html.Kendo().Grid<Kendo.Mvc.Examples.Models.ProductViewModel>()
+        .Name("grid")
+        .Columns(columns => {
+            columns.Bound(p => p.ProductID).Visible(true).Width(100);
+            columns.Bound(p => p.ProductName);
+            columns.Bound(p => p.UnitPrice).Width(150);
+            columns.Bound(p => p.QuantityPerUnit);
+        })
+        .ToolBar(toolbar => {
+            toolbar.ClientTemplateView(Html.Partial("_ToolbarTemplatePartial"));
+        })
+        .DataSource(dataSource => dataSource
+            .Ajax()
+            .ServerOperation(false)
+            .Model(model => model.Id(p => p.ProductID))
+            .Read("ToolbarTemplate_Read", "Grid")
+        )
+    )
+```
+{% if site.core %}
+```TagHelper
+    <kendo-grid name="grid" height="500">
+        <columns>
+            <column field="ProductID" visible="true" width="100">
+                <exportable pdf="true" />
+            </column>
+            <column field="ProductName">
+            </column>
+            <column field="UnitPrice" width="150">
+            </column>
+            <column field="QuantityPerUnit">
+            </column>
+        </columns>
+        <toolbar client-template-view="@Html.Partial("_ToolbarTemplatePartial")">
+        </toolbar>
+        <datasource page="0" type="DataSourceTagHelperType.Ajax" page-size="20" server-operation="false">
+            <schema data="Data" total="Total" errors="Errors">
+                <model id="ProductID"></model>
+            </schema>
+            <transport>
+                <read url="@Url.Action("ToolbarTemplate_Read","Grid")" />
+            </transport>
+        </datasource>
+    </kendo-grid>
+```
+{% endif %}
+```_Partial.cshtml
+    <div class="toolbar">
+     <label class="category-label" for="category">Show products by category:</label>
+     @(Html.Kendo().DropDownList()
+         .Name("categories")
+         .OptionLabel("All")
+         .DataTextField("CategoryName")
+         .DataValueField("CategoryID")
+         .HtmlAttributes(new { style = "width: 150px;" })
+         .DataSource(ds =>
+         {
+             ds.Read("ToolbarTemplate_Categories", "Grid");
+         })
+         .ToClientTemplate()
+     )
+    </div>
+```
 
 ### Adding HTML Helpers inside External Client Templates
 

docs-aspnet/installation/migrating.md

@@ -13,52 +13,64 @@ The MVC technology 3, 4 and 5 has been a wonderful technology for many years. It
 
 ASP.NET Core is the active offering of Microsoft and provides cross-platform ground for building and running .NET apps on Linux, macOS, and Windows. This is the technology that will get updates going forward. So naturally, many people will want to choose developing Core MVC web applications.
 
-Telerik UI has well supported and developed Products for each of these technologies. This article aims to help you with the process of migrating from MVC to Core MVC if this happens to be your decision.
+Telerik UI has well supported and developed products for each of these technologies through its [Telerik UI for ASP.NET MVC](https://demos.telerik.com/aspnet-mvc/) and [Telerik UI for ASP.NET Core](https://demos.telerik.com/aspnet-core/) libraries.
+
+This article aims at helping you with the process of migrating from ASP.NET MVC to ASP.NET Core.
 
 ## Compatibility
 
-The good news is that there is almost 1:1 parity between the two UI toolsets. The transition should be smooth, easy and fully feature covered.
+The good news is that there is almost 1:1 parity between the two UI toolsets. The transition is smooth, easy, and fully feature-covered. For any minor variations, check the [section about exceptions](#exceptions) to find out where the products differ from one another.
 
-For reference, you can compare the Code base of these two live samples and you will notice that the syntax is identical:
+For reference, compare the code base of the following live samples to make sure the syntax is identical:
 
-- [Grid in Telerik UI for MVC](https://demos.telerik.com/aspnet-mvc/grid/local-data-binding).
-- [Grid in Telerik UI for Core MVC](https://demos.telerik.com/aspnet-core/grid/local-data-binding)
+- [Telerik UI for ASP.NET MVC Data Grid](https://demos.telerik.com/aspnet-mvc/grid/local-data-binding).
+- [Telerik UI for ASP.NET Core Data Grid](https://demos.telerik.com/aspnet-core/grid/local-data-binding)
 
 ## Exceptions
 
 There are couple of differences worth mentioning to ease your migration process.
 
-1. MVC Grid server rendered templates should transfer to client rendered templates in Core MVC Grid. Therefore, you will now use `.HeaderTemplate()` instead of `.ClientHeaderTemplate()`.
+1. The MVC Grid server-rendered templates must transfer to client-rendered templates in Core Grid. Therefore, you will now use `.HeaderTemplate()` instead of `.ClientHeaderTemplate()`.
+
+2. Check out the [Migrate to ASP.NET Core MVC from ASP.NET Framework MVC](https://www.telerik.com/blogs/migrate-aspnet-core-mvc-aspnet-framework-mvc) blog post by Joe Guadagno to explore the common code-behind steps while migrating an app to ASP.NET Core MVC.
+
+  Some key takeaways from this blog are:
 
-2. We have a Blog post covering common code-behind steps:
+  - **Separate the Models**–Putting your domain or data transfer objects into a separate project.
+  - **Separate the Data Layer**–Getting data access methods out of the user interface (web app).
+  - **Create a New Project**–Analyzing the structure differences of a project in the new technology: folders, files, and so on.
+  - **Gotchas**–Possible things that may stump you during the migration process.
 
-    [Migrate to ASP.NET Core MVC from ASP.NET Framework MVC](https://www.telerik.com/blogs/migrate-aspnet-core-mvc-aspnet-framework-mvc)
+3. The rest are syntax sugar differences caused by the frameworks themselves. These are present only for some of the components. For instance, here is a Validation action definition of the Upload component in MVC:
 
-3. The rest are syntax sugar differences caused by the frameworks themselves. For instance, here is a Validation action definition of the Upload component in MVC:
-```C#
-        public ActionResult Validation_Save(IEnumerable<HttpPostedFileBase> files)
-        {
-        }
-```
-And this is the equivalent implementation in Core MVC:
-```C#
-        public async Task<ActionResult> Validation_Save(IEnumerable<IFormFile> files)
-        {
-        }
-```
+  ```C#
+          public ActionResult Validation_Save(IEnumerable<HttpPostedFileBase> files)
+          {
+          }
+  ```
 
-4. The same is true for the **Startup.cs** file:
+  The following is the equivalent implementation in Core MVC:
 
-    [JSON serialization in Core](https://docs.telerik.com/aspnet-core/installation/json-serialization)
+  ```C#
+          public async Task<ActionResult> Validation_Save(IEnumerable<IFormFile> files)
+          {
+          }
+  ```
 
-5. You can check this nice MSDN article for general points when migrating:
+4. The same is true for the `Startup.cs` file. Check out the [JSON serialization in Core](https://docs.telerik.com/aspnet-core/installation/json-serialization) article to see how to configure it.
 
-    [Migrate from ASP.NET MVC to ASP.NET Core MVC](https://learn.microsoft.com/en-us/aspnet/core/migration/mvc?view=aspnetcore-7.0)
+5. You can check the [Migrate from ASP.NET MVC to ASP.NET Core MVC](https://learn.microsoft.com/en-us/aspnet/core/migration/mvc?view=aspnetcore-7.0) MSDN article for general points when migrating.
 
+  Some key takeaways from this article are:
+
+  - Install the .NET Upgrade Assistant.
+  - Open Visual Studio and choose the **Upgrade** action in the **Solution Explorer** context menu.
+  - Check the **Summary of Changes** before pressing **Finish**.
 
 ## Migrating from Another Technology
 
-If you are coming from another Telerik UI toolset, we have resources addressing this  situation as well:
- - [From Web Forms to Core](https://www.telerik.com/blogs/review-of-telerik-toolsets-for-aspnet-web-forms-core)
- - [From Web Forms to Blazor](https://www.telerik.com/blogs/review-of-telerik-toolsets-for-asp.net-web-forms-and-blazor-part-1)
- - [From MVC to Blazor](https://www.telerik.com/blogs/migrating-mvc-to-blazor)
+If you are coming from another Telerik UI toolset, refer to the following resources addressing this scenario:
+
+- [From Web Forms to Core](https://www.telerik.com/blogs/review-of-telerik-toolsets-for-aspnet-web-forms-core)–A blog post and whitepaper, which aim to assist developers in familiarizing quickly with the overall idea of ASP.NET Web Forms and ASP.NET Core. They also outline a couple of fundamental steps for customers who’ve decided to create a new application based on ASP.NET Core, or modernize their existing Web Forms app by switching to a Core app.
+- [From Web Forms to Blazor](https://www.telerik.com/blogs/review-of-telerik-toolsets-for-asp.net-web-forms-and-blazor-part-1)–A blog post series divided into three parts. These serve as a guide for developers to learn what Telerik has to offer for both technologies and how to migrate from ASP.NET AJAX to the newest .NET technology - Blazor.
+- [From MVC to Blazor](https://www.telerik.com/blogs/migrating-mvc-to-blazor)–A blog post outlining how to migrate from ASP.NET MVC to Blazor and what pitfalls to look out for while doing so.

docs/api/javascript/ui/pdfviewer.md

@@ -458,7 +458,7 @@ Specifies the localization messages of the toolbar.
 
 ### messages.toolbar.pager.last `String` *(default: "Go to the last page")*
 
-### messages.toolbar.pager.of `String` *(default: " of {0} ")*
+### messages.toolbar.pager.of `String` *(default: "of")*
 
 ### messages.toolbar.pager.page `String` *(default: "page")*
 

docs/controls/charts/get-started.md

@@ -296,7 +296,7 @@ The Chart [`tooltip`](/api/javascript/dataviz/ui/chart/configuration/tooltip#too
 
 ## Next Steps 
 
-* [Referencing Existing Widget Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
+* [Referencing Existing Component Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
 * [Demo Page for the Chart](https://demos.telerik.com/kendo-ui/chart/index)
 
 ## See Also 

docs/controls/data-management/listview/get-started.md

@@ -282,7 +282,7 @@ The ListView allows you to display a scrollbar inside the widget so end-users do
 
 ## Next Steps 
 
-* [Referencing Existing Widget Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
+* [Referencing Existing Component Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
 * [Demo Page for the ListView](https://demos.telerik.com/kendo-ui/listview/index)
 
 ## See Also 

docs/controls/editors/datepicker/get-started.md

@@ -108,7 +108,7 @@ You can customize the format of the displayed date by setting the [`format`](/ap
 
 ## Next Steps 
 
-* [Referencing Existing Widget Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
+* [Referencing Existing Component Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
 * [Demo Page for the DatePicker](https://demos.telerik.com/kendo-ui/datepicker/index)
 
 ## See Also 

docs/controls/editors/dropdownlist/get-started.md

@@ -115,7 +115,7 @@ Among other functionalities, the DropDownList supports filtering. The filtering
 
 ## Next Steps 
 
-* [Referencing Existing Widget Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
+* [Referencing Existing Component Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
 * [Demo Page for the DropDownList](https://demos.telerik.com/kendo-ui/dropdownlist/index)
 
 ## See Also 

docs/controls/editors/numerictextbox/get-started.md

@@ -76,7 +76,7 @@ You can now refer to the NumericTextBox instance and build on top of its existin
 
 ## Next Steps 
 
-* [Referencing Existing Widget Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
+* [Referencing Existing Component Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
 * [Demo Page for the NumericTextBox](https://demos.telerik.com/kendo-ui/numerictextbox/index)
 
 ## See Also 

docs/controls/editors/signature/get-started.md

@@ -73,7 +73,7 @@ $(document).ready(function () {
 
 ## Next Steps 
 
-* [Referencing Existing Widget Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
+* [Referencing Existing Component Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
 * [Demo Page for the Signature](https://demos.telerik.com/kendo-ui/signature/index)
 
 ## See Also 

docs/controls/editors/textbox/get-started.md

@@ -86,7 +86,7 @@ The TextBox enables you to configure the label by using the [`label`](https://do
 
 ## Next Steps 
 
-* [Referencing Existing Widget Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
+* [Referencing Existing Component Instances]({% slug widget_methodsand_events_kendoui_installation %}) 
 * [Demo Page for the TextBox](https://demos.telerik.com/kendo-ui/textbox/index)
 
 ## See Also