diff --git a/_config.yml b/_config.yml
index 271f8bf3d..5f827bf74 100644
--- a/_config.yml
+++ b/_config.yml
@@ -26,7 +26,7 @@ navigation:
title: Visual Studio Extensions
position: 4
core:
- title: NET Core
+ title: .NET Support
position: 5
winforms-converter:
title: WinForms application modernization wizard
@@ -43,18 +43,21 @@ navigation:
styling-and-appearance:
title: Styling and Appearance
position: 9
+ ai-coding-assistant:
+ title: AI Coding Assistant
+ position: 10
tools:
title: Tools
- position: 10
+ position: 11
integration-with-other-telerik-products:
title: Integration with Other Telerik Products
- position: 11
+ position: 12
testing:
title: Testing
- position: 12
+ position: 13
deployment-and-distribution:
title: Deployment and Distribution
- position: 13
+ position: 14
security:
title: Security
position: 15
diff --git a/ai-coding-assistant/copilot-extension.md b/ai-coding-assistant/copilot-extension.md
new file mode 100644
index 000000000..9a33c2970
--- /dev/null
+++ b/ai-coding-assistant/copilot-extension.md
@@ -0,0 +1,82 @@
+---
+title: Copilot Extension
+page_title: Telerik WinForms GitHub Copilot Extension
+description: Learn how to add and use the Telerik WinForms GitHub Copilot extension as a WinForms AI coding assistant and code generator for better developer productivity. The Telerik WinForms GitHub Copilot extension provides proprietary context about Telerik UI for WinForms to AI-powered software.
+slug: ai-copilot-extension
+tags: telerik, WinForms, ai, coding assistant, ai server
+position: 1
+---
+
+# Telerik WinForms GitHub Copilot Extension
+
+The Telerik WinForms [GitHub Copilot](https://github.com/features/copilot) extension is an AI-powered coding assistant that provides specialized knowledge about [Telerik UI for WinForms components](https://www.telerik.com/products/winforms.aspx).
+
+This extension enhances GitHub Copilot with proprietary context about Telerik WinForms controls, helping you:
+
+* Generate code snippets using Telerik WinForms components.
+* Get contextual suggestions for component properties and methods.
+* Access best practices and implementation patterns.
+* Speed up development with AI-powered code completion.
+
+## Prerequisites
+
+Before using the Telerik WinForms GitHub Copilot extension, ensure you have:
+
+* An active [GitHub Copilot](https://github.com/features/copilot) subscription. You can enable or configure GitHub Copilot on the [Copilot Settings page in your GitHub account](https://github.com/settings/copilot).
+* A [Telerik user account](https://www.telerik.com/account/?_gl=1*rbcezh*_gcl_au*NzA0NDU3NzU1LjE3NTA2NTk3NDY.*_ga*ODUxNTg5NDI5LjE2OTU2NDQ2ODI.*_ga_9JSNBCSF54*czE3NTQ1NDQ5MTQkbzE0NSRnMSR0MTc1NDU3MjMxMiRqMzAkbDAkaDA.).
+* An active [DevCraft or Telerik UI for WinForms license](https://www.telerik.com/purchase/individual/winforms.aspx) or a [Telerik UI for WinForms trial](https://www.telerik.com/try/ui-for-winforms).
+* A [WinForms application that includes Telerik UI for WinForms](https://docs.telerik.com/devtools/winforms/getting-started/first-steps).
+* The latest version of your [Copilot-enabled app](https://docs.github.com/en/copilot/building-copilot-extensions/about-building-copilot-extensions#supported-clients-and-ides) (for example, Visual Studio or Visual Studio Code).
+
+## Installation
+
+Follow these steps to install and configure the Telerik WinForms Copilot extension:
+
+1. Go to the [Telerik WinForms GitHub App](https://github.com/apps/telerikwinforms) page and click the **Install** button.
+1. You will see a list that includes your GitHub account and all GitHub organizations that you are part of. Select your GitHub account.
+1. Click the **Install & Allow** button. This will allow the GitHub Copilot extension to integrate with your GitHub account.
+1. Enter your GitHub password when prompted.
+1. You will be redirected to telerik.com. Enter your Telerik account credentials if prompted. This step links the GitHub Copilot extension with your Telerik account.
+1. Upon successful Telerik authentication, you will be redirected to a confirmation page that indicates successful Copilot extension installation.
+1. Restart your [Copilot-enabled app](https://docs.github.com/en/copilot/building-copilot-extensions/about-building-copilot-extensions#supported-clients-and-ides) (for example, Visual Studio and Visual Studio Code).
+1. Start a new chat session in Copilot.
+
+## Usage
+
+To use the Telerik WinForms Copilot extension:
+
+1. Open the GitHub Copilot chat window in your [Copilot-enabled app](https://docs.github.com/en/copilot/building-copilot-extensions/about-building-copilot-extensions#supported-clients-and-ides) (for example, Visual Studio or VS Code).
+1. Ensure you are in **Chat** mode and not in **Edit** or **Agent** mode. The Edit and Agent modes do not use the Telerik Copilot extension. However, the Agent mode can use the [Telerik WinForms MCP server]({%slug ai-mcp-server%}).
+1. Start your prompt with `@telerikmaui` and type your request. Verify that `@telerikmaui` is recognized and highlighted; otherwise, the extension may not be properly installed.
+1. Look for a status label such as **Telerik WinForms working...** or **Telerik WinForms generating response...** in the output to confirm the extension is active.
+1. Grant permission to the Telerik WinForms extension to read your workspace files when prompted.
+1. For unrelated queries, start a new chat session in a new window to avoid context pollution from previous conversations.
+
+### Sample Prompts
+
+The following examples demonstrate useful prompts for the Telerik WinForms extension:
+
+* "`@telerikwinforms` Generate a Grid with sorting and paging enabled."
+* "`@telerikwinforms` Create a Telerik RadDropDownlist for WinForms with multiple selection enabled."
+* "`@telerikwinforms` Show me how to implement a ChartView with line series."
+* "`@telerikwinforms` Show me how to size all columns in GridView to take all the available space."
+
+## Number of Requests
+
+A Telerik [Subscription license](https://www.telerik.com/purchase/faq/licensing-purchasing) is recommended in order to use the Telerik WinForms AI Coding Assistant without restrictions. Perpetual license holders and trial users can make a limited [number of requests per year]({%slug ai-overview%}#number-of-requests).
+
+## Troubleshooting
+
+If you encounter issues:
+
+* Ensure the `@telerikwinforms` mention is properly highlighted in your prompt.
+* Verify that you have an active GitHub Copilot subscription.
+* Restart your IDE after installation.
+* Check that you're in Chat mode, not Edit or Agent mode.
+
+## See Also
+
+* [GitHub Copilot Documentation](https://docs.github.com/en/copilot)
+* [GitHub Copilot Tutorials](https://github.com/features/copilot/tutorials)
+* [Telerik WinForms MCP Server]({%slug ai-mcp-server%})
+* [Telerik UI for WinForms Documentation](https://docs.telerik.com/devtools/winforms/introduction)
diff --git a/ai-coding-assistant/mcp-server.md b/ai-coding-assistant/mcp-server.md
new file mode 100644
index 000000000..f381e8f99
--- /dev/null
+++ b/ai-coding-assistant/mcp-server.md
@@ -0,0 +1,212 @@
+---
+title: MCP Server
+page_title: Telerik WinForms MCP Server
+description: Learn how to add and use the Telerik WinForms MCP Server as a WinForms AI coding assistant and code generator for better developer productivity. The Telerik WinForms MCP server provides proprietary context about Telerik UI for WinForms to AI-powered software.
+slug: ai-mcp-server
+tags: telerik,winforms,ai,ai server,coding assistant
+position: 2
+---
+
+# Telerik WinForms MCP Server
+
+The Telerik WinForms [MCP (Model Context Protocol) Server](https://modelcontextprotocol.io/introduction) enhances your AI-powered development experience by providing specialized context about Telerik UI for WinForms components.
+
+This MCP server enables AI-powered IDEs and tools to generate more accurate, tailored code that leverages [Telerik UI for WinForms components](https://docs.telerik.com/devtools/winforms/introduction) and APIs. You can ask complex questions about Telerik components, request specific implementations, and generate comprehensive code solutions.
+
+## Prerequisites
+
+To use the Telerik WinForms MCP server, you need:
+
+* [Node.js](https://nodejs.org/en) 18 or newer.
+* An [MCP-compatible client](https://modelcontextprotocol.io/clients) that supports **MCP tools** (latest version recommended).
+* A [Telerik user account](https://www.telerik.com/account/?_gl=1*rbcezh*_gcl_au*NzA0NDU3NzU1LjE3NTA2NTk3NDY.*_ga*ODUxNTg5NDI5LjE2OTU2NDQ2ODI.*_ga_9JSNBCSF54*czE3NTQ1NDQ5MTQkbzE0NSRnMSR0MTc1NDU3MjMxMiRqMzAkbDAkaDA.).
+* An active [DevCraft or Telerik UI for WinForms license](https://www.telerik.com/purchase/individual/winforms.aspx) or a [Telerik UI for WinForms trial](https://www.telerik.com/try/ui-for-winforms).
+* A [WinForms application that includes Telerik UI for WinForms](https://docs.telerik.com/devtools/winforms/getting-started/first-steps).
+
+## Installation
+
+Install the Telerik WinForms MCP server using npm:
+
+```bash
+npm i @progress/telerik-winforms-mcp
+```
+
+### Configuration
+
+Use these settings when configuring the server in your MCP client:
+
+| Setting | Value |
+|---------|-------|
+| Package Name | `@progress/telerik-winforms-mcp` |
+| Type | `stdio` (standard input/output transport) |
+| Command | `npx` |
+| Arguments | `-y` |
+| Server Name | `telerikWinFormsAssistant` (customizable) |
+
+### License Configuration
+
+Add your [Telerik license key]({%slug license-key%}) as an environment parameter in your `mcp.json` file using one of these options:
+
+Option 1: License File Path (Recommended)
+
+ ```json
+ "env": {
+ "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE"
+ }
+ ```
+
+Option 2: Direct License Key
+
+ ```json
+ "env": {
+ "TELERIK_LICENSE": "YOUR_LICENSE_KEY_HERE"
+ }
+ ```
+
+> Option 1 is recommended unless you're sharing settings across different systems. Remember to [update your license key]({%slug license-key%}#updating-your-license-key) when necessary.
+
+## Visual Studio
+
+For complete setup instructions, see [Use MCP servers in Visual Studio](https://learn.microsoft.com/en-us/visualstudio/ide/mcp-servers).
+
+> Early Visual Studio 17.14 versions require the Copilot Chat window to be open when opening a solution for the MCP server to work properly.
+
+### Workspace-Specific Setup:
+
+1. Add `.mcp.json` to your solution folder:
+
+ ```json
+ {
+ "servers": {
+ "telerikWinFormsAssistant": {
+ "type": "stdio",
+ "command": "npx",
+ "args": ["-y", "@progress/telerik-winforms-mcp@latest"],
+ "env": {
+ "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
+ // or
+ "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
+ }
+ }
+ }
+ }
+ ```
+
+2. Restart Visual Studio.
+3. Enable the `telerikWinFormsAssistant` tool in the [Copilot Chat window's tool selection dropdown](https://learn.microsoft.com/en-us/visualstudio/ide/mcp-servers?view=vs-2022#configuration-example-with-github-mcp-server).
+
+### Global Setup:
+
+Add the `.mcp.json` file to your user directory (`%USERPROFILE%`, e.g., `C:\Users\YourName\.mcp.json`).
+
+## Visual Studio Code
+
+For complete setup instructions, see [Use MCP servers in Visual Studio Code](https://code.visualstudio.com/docs/copilot/chat/mcp-servers).
+
+> Visual Studio Code 1.102.1 or newer is required to use the Telerik MCP Server
+
+The basic setup in Visual Studio Code follows these steps:
+
+1. Enable [`chat.mcp.enabled`](vscode://settings/chat.mcp.enabled) in Visual Studio Code settings.
+2. Create `.vscode/mcp.json` in your workspace root (or user folder for global setup):
+
+ ```json
+ {
+ "servers": {
+ "telerik-winforms-assistant": {
+ "type": "stdio",
+ "command": "npx",
+ "args": ["-y", "@progress/telerik-winforms-mcp@latest"],
+ "env": {
+ "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
+ // or
+ "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
+ }
+ }
+ }
+ }
+ ```
+
+3. For global discovery, enable [`chat.mcp.discovery.enabled`](vscode://settings/chat.mcp.discovery.enabled) in `settings.json`:
+
+ ```json
+ {
+ "chat.mcp.discovery.enabled": true
+ }
+ ```
+
+4. Restart Visual Studio Code.
+
+## Cursor
+
+For complete setup instructions, see [Model Context Protocol](https://docs.cursor.com/context/mcp).
+
+Create `.cursor/mcp.json` in your workspace root (or user folder for global setup):
+
+```json
+{
+ "mcpServers": {
+ "telerikWinFormsAssistant": {
+ "type": "stdio",
+ "command": "npx",
+ "args": ["-y", "@progress/telerik-winforms-mcp@latest"],
+ "env": {
+ "TELERIK_LICENSE_PATH": "THE_PATH_TO_YOUR_LICENSE_FILE",
+ // or
+ "TELERIK_LICENSE": "YOUR_LICENSE_KEY"
+ }
+ }
+ }
+}
+```
+
+## Usage
+
+To use the Telerik MCP Server:
+
+1. Start your prompt with one of these triggers:
+ - `/telerik` / `@telerik` / `#telerik`
+ - `/telerikwinforms` / `@telerikwinforms` / `#telerikwinforms`
+ - `#telerik-winforms-assistant`
+
+2. Verify server activation by looking for these messages:
+ - Visual Studio: `Running telerikWinFormsAssistant`
+ - Visual Studio Code: `Running telerik-winforms-assistant`
+ - Cursor: `Calling MCP tool telerikWinFormsAssistant`
+
+3. Grant permissions when prompted (per session, workspace, or always).
+
+4. Start fresh sessions for unrelated prompts to avoid context pollution.
+
+### Improving Server Usage
+
+To increase the likelihood of the Telerik MCP server being used, add custom instructions to your AI tool:
+- [GitHub Copilot custom instructions](https://docs.github.com/en/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot#about-repository-custom-instructions-for-github-copilot-chat)
+- [Cursor rules](https://docs.cursor.com/context/rules)
+
+### Sample Prompts
+
+The following examples demonstrate useful prompts for the Telerik WinForms MCP Server:
+
+* "`/telerik` Generate a DataGrid with sorting and paging. Bind it to a Person model with sample ViewModel."
+* "`/telerikwinforms` Create a ComboBox showing a product list. Include Product class and sample data."
+* "`/telerik` Build a CollectionView with sorting and filtering capabilities."
+
+## Number of Requests
+
+A Telerik [Subscription license](https://www.telerik.com/purchase/faq/licensing-purchasing) is recommended in order to use the Telerik WinForms AI Coding Assistant without restrictions. Perpetual license holders and trial users can make a limited [number of requests per year]({%slug ai-overview%}#number-of-requests).
+
+## Local AI Model Integration
+
+You can use the Telerik WinForms MCP server with local large language models (LLMs):
+
+1. Run a local model, for example, through [Ollama](https://ollama.com).
+2. Use a bridge package like [MCP-LLM Bridge](https://github.com/patruff/ollama-mcp-bridge).
+3. Connect your local model to the Telerik MCP server.
+
+This setup allows you to use the Telerik AI Coding Assistant without cloud-based AI models.
+
+## See Also
+
+* [Telerik WinForms GitHub Copilot Extension]({%slug ai-copilot-extension%})
+* [AI Coding Assistant Overview]({%slug ai-overview%})
diff --git a/ai-coding-assistant/overview.md b/ai-coding-assistant/overview.md
new file mode 100644
index 000000000..989b870b4
--- /dev/null
+++ b/ai-coding-assistant/overview.md
@@ -0,0 +1,76 @@
+---
+title: Overview
+page_title: Telerik UI for WinForms AI Tooling Overview
+description: Learn about the AI-powered developer tools that integrate with your IDE or code editor for greater productivity and enhanced developer experience.
+slug: ai-overview
+tags: telerik,winforms,ai,coding assistant
+position: 0
+---
+
+# Telerik UI for WinForms AI Coding Assistant
+
+The Telerik UI for WinForms AI Coding Assistant enhances your developer experience and increases productivity when building WinForms applications with Telerik UI for WinForms components.
+
+The coding assistant is an AI code generator that provides specialized context to AI models, enabling them to produce higher-quality code samples using the [Telerik UI for WinForms components](https://www.telerik.com/products/winforms.aspx) and APIs.
+
+## Available Tools
+
+The Telerik AI Coding Assistant is available through:
+
+* [Telerik WinForms GitHub Copilot Extension]({%slug ai-copilot-extension%})
+* [Telerik WinForms MCP Server]({%slug ai-mcp-server%})
+
+### Key Differences
+
+| Feature | MCP Server | GitHub Copilot Extension |
+|------------------------|---------------------------------------------------------------------------|------------------------------------------------------------|
+| Prompt Handling | Handles complex, multi-step prompts | Offers shorter, focused code snippets |
+| Client Compatibility | Works with MCP-enabled clients (e.g., Cursor, Copilot Agent mode) | Integrated as a Copilot extension |
+| Code Suggestions | Can directly suggest changes and rebuild applications to verify code | Provides detailed explanations alongside code suggestions |
+| Response Focus | Primarily code-focused | Better for learning and understanding implementation |
+
+## Getting Started
+
+To use the Telerik WinForms AI Coding Assistant, you need:
+
+* A [Telerik user account](https://www.telerik.com/account/?_gl=1*rbcezh*_gcl_au*NzA0NDU3NzU1LjE3NTA2NTk3NDY.*_ga*ODUxNTg5NDI5LjE2OTU2NDQ2ODI.*_ga_9JSNBCSF54*czE3NTQ1NDQ5MTQkbzE0NSRnMSR0MTc1NDU3MjMxMiRqMzAkbDAkaDA.).
+* An active [DevCraft or Telerik UI for WinForms license](https://www.telerik.com/purchase/individual/winforms.aspx) or a [Telerik UI for WinForms trial](https://www.telerik.com/try/ui-for-winforms).
+* A [WinForms application that includes Telerik UI for WinForms](https://docs.telerik.com/devtools/winforms/getting-started/first-steps).
+* A Telerik [Subscription license](https://www.telerik.com/purchase/faq/licensing-purchasing) is recommended in order to use the Telerik WinForms AI Coding Assistant without restrictions. Perpetual license holders and trial users can make a limited number of requests per year.
+
+## Number of Requests
+
+The Telerik WinForms AI Coding Assistant allows the following maximum number of requests based on your [Telerik license type](https://www.telerik.com/purchase/faq/licensing-purchasing):
+
+| License Type | Request Limit |
+|--------------|---------------|
+| Perpetual | 50 requests per year |
+| Subscription | Virtually unlimited with a fair use threshold of 300 requests per day |
+| Trial | 300 requests per trial period (does not reset with new trial activations) |
+
+> All Telerik AI tools share a single request quota for your Telerik account. Usage from the [Telerik Copilot extension]({%slug ai-copilot-extension%}) and [Telerik MCP server]({%slug ai-mcp-server%}) counts toward the same limit. Complex prompts in the MCP server may consume multiple requests.
+
+## Privacy
+
+The Telerik WinForms AI Coding Assistant operates under strict privacy guidelines:
+
+Data Access:
+* No access to your workspace and application code.
+* Exception: when using the Telerik MCP server (or any other MCP server), the LLM generates parameters for the MCP server request, which may include parts of your application code.
+
+Data Usage:
+* Your prompts are not used to train Telerik AI models.
+* Does not generate or access AI responses.
+* Provides enhanced context to improve responses from your chosen AI model (GPT, Gemini, Claude, etc.).
+
+Data Storage:
+* Prompts and context are anonymized and stored only for statistical analysis and troubleshooting.
+* No association between prompts and your Telerik user account.
+* Usage metrics are collected to ensure [license compliance](#number-of-requests).
+
+> Make sure also to review the terms and privacy policies of your selected AI model and AI client.
+
+## Next Steps
+
+* Install the [Telerik WinForms GitHub Copilot Extension]({%slug ai-copilot-extension%})
+* Configure the [Telerik WinForms MCP Server]({%slug ai-mcp-server%}) with an MCP-enabled client
\ No newline at end of file
diff --git a/controls/gridview/ui-automation.md b/controls/gridview/ui-automation.md
new file mode 100644
index 000000000..90ec1aeab
--- /dev/null
+++ b/controls/gridview/ui-automation.md
@@ -0,0 +1,222 @@
+---
+title: UI Automation Support (UI Accessibility)
+page_title: UI Automation Support (UI Accessibility) - RadGridView
+description: UI Automation Support (UI Accessibility) for RadGridView.
+slug: gridview-ui-automation
+tags: radgridview,ui,automation
+published: True
+position: 15
+---
+
+# UI Automation Support
+
+With the __Q3 2025__ version of our controls, RadGridView supports UI Automation. The current implementation of UI Automation for RadGridView is similar to the __MS WinForms RadGridView Control Type__ implementation with some extended functionality. The main goal of this implementation is to ensure compliance with accessibility standards and to provide a common practice for automated testing.
+
+>caption Figure 1: RadGridView UI Automation Tree Structure
+
+| **Control View**|
+|------------------------|
+| ├─ [DataGrid](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-datagrid-control-type) (RadGridView Control )|
+| ├─ [Header](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-header-control-type) (Table Header Row) |
+| └─ [HeaderItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-headeritem-control-type) (Header Cells)|
+| ├─ [DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type) (New Row)|
+| └─ [DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type) (New Row Cells)|
+| ├─ [DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type) (Data Row)|
+| ├─ [HeaderItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-headeritem-control-type) (Row Header Cells)|
+| ├─ [CheckBox](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-checkbox-control-type) (Row Select Cells)|
+| ├─ [Edit](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-edit-control-type) (TextBox Column Data Cell)|
+| └─ [Edit](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-edit-control-type) (Cell TextBox Editor)|
+| ├─ [Spinner](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-spinner-control-type) (Decimal Column Data Cell)|
+| └─ [Spinner](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-spinner-control-type) (Cell Spin Editor)|
+| ├─ [ComboBox](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-combobox-control-type) (ComboBox Column Data Cell)|
+| └─ [ComboBox](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-combobox-control-type) (DropDownList Editor)|
+| ├─ [CheckBox](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-checkbox-control-type) (CheckBox Column Data Cell)|
+| ├─ [Button](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-button-control-type) (Command Column Data Cell)|
+| ├─ [Image](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-image-control-type) (Image Column Data Cell)|
+| ├─ [Hyperlink](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-hyperlink-control-type) (Hyperlink Column Data Cell)|
+| ├─ [DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type) (DateTime Column Data Cell)|
+| ├─ [DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type) (Color Column Data Cell)|
+| ├─ [DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type) (TimeSpan Column Data Cell)|
+| ├─ [DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type) (MultiColumnComboBox Column Data Cell)|
+| ├─ [DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type) (Rating Column Data Cell)|
+| ├─ [DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type) (Sparkline Column Data Cell)|
+| └─ [DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type) (Calculator Column Data Cell)|
+| ├─ [ScrollBar](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-scrollbar-control-type) (Vertical ScrollBar)|
+| └─ [ScrollBar](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-scrollbar-control-type) (Horizontal ScrollBar)|
+
+This functionality is enabled by default. To disable it, you can set the __EnableUIAutomation__ property to false.
+
+````C#
+
+this.radGridView1.EnableUIAutomation = false;
+
+````
+````VB.NET
+
+Me.radGridView1.EnableUIAutomation = False
+
+````
+
+## Relevant Properties
+
+The table below outlines the __UI Automation__ properties most important for understanding and interacting with RadGridView control.
+
+### Rows
+
+This table describes the UI Automation support for different types of rows within RadGridView. Each row type is associated with a corresponding provider implementation, making them accessible to screen readers and automation tools.
+
+|Row Element|Telerik UIA Row Provider|UIA Control Type|
+|------|------|------|
+|Data Row|DataRowHeaderItemUIAutomationProvider|[DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type)|
+|New Row|NewRowUIAutomationProvider|[DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type)|
+|Table Header Row|TableHeaderRowUIAutomationProvider|[Header](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-header-control-type)|
+
+#### DataRowUIAutomationProvider
+
+This provider supports automation for standard data rows.
+
+* AutomationElementIdentifiers.ControlTypeProperty.Id => ControlType.DataItem.Id
+* AutomationElementIdentifiers.LocalizedControlTypeProperty.Id => "data item"
+* AutomationElementIdentifiers.NameProperty.Id
+* AutomationElementIdentifiers.OrientationProperty.Id
+* AutomationElementIdentifiers.IsContentElementProperty.Id
+* AutomationElementIdentifiers.HasKeyboardFocusProperty.Id
+* AutomationElementIdentifiers.IsSelectionItemPatternAvailableProperty.Id
+* AutomationElementIdentifiers.IsScrollItemPatternAvailableProperty.Id
+* AutomationElementIdentifiers.IsGridItemPatternAvailableProperty.Id
+* AutomationElementIdentifiers.IsTableItemPatternAvailableProperty.Id
+
+The following items outlines the supported automation patterns by the **DataRowUIAutomationProvider**.
+
+* [Selection Item Pattern](https://learn.microsoft.com/en-us/dotnet/api/system.windows.automation.provider.iselectionitemprovider?view=windowsdesktop-9.0)
+* [Scroll Item Pattern](https://learn.microsoft.com/en-us/dotnet/api/system.windows.automation.provider.iscrollitemprovider?view=windowsdesktop-9.0)
+* [Grid Item Pattern](https://learn.microsoft.com/en-us/dotnet/api/system.windows.automation.provider.igriditemprovider?view=windowsdesktop-9.0)
+* [Table Item Pattern](https://learn.microsoft.com/en-us/dotnet/api/system.windows.automation.provider.itableitemprovider?view=windowsdesktop-9.0)
+
+#### NewRowUIAutomationProvider
+
+This provider targets the "Add New Row" functionality.
+
+* AutomationElementIdentifiers.ControlTypeProperty.Id => ControlType.DataItem.Id
+* AutomationElementIdentifiers.LocalizedControlTypeProperty.Id => "data item"
+* AutomationElementIdentifiers.NameProperty.Id => "TableAddNewRow"
+* AutomationElementIdentifiers.OrientationProperty.Id
+* AutomationElementIdentifiers.IsContentElementProperty.Id
+* AutomationElementIdentifiers.HasKeyboardFocusProperty.Id
+
+#### TableHeaderRowUIAutomationProvider
+
+This provider targets the table header row.
+
+* AutomationElementIdentifiers.ControlTypeProperty.Id => ControlType.Header.Id
+* AutomationElementIdentifiers.LocalizedControlTypeProperty.Id => "header"
+* AutomationElementIdentifiers.NameProperty.Id => "TableHeaderRow"
+* AutomationElementIdentifiers.OrientationProperty.Id
+* AutomationElementIdentifiers.IsContentElementProperty.Id
+* AutomationElementIdentifiers.HasKeyboardFocusProperty.Id
+* AutomationElementIdentifiers.IsKeyboardFocusableProperty.Id
+
+
+### Cells
+
+This section provides a breakdown of the supported cell types in RadGridView and their corresponding UI Automation providers. Each cell type is linked to a provider responsible for handling its accessibility representation and available patterns.
+
+Several provider classes in this list: **DataRowHeaderItemUIAutomationProvider, DataCellSpinnerUIAutomationProvider, DataRowSelectCellUIAutomationProvider, and DataCellEditUIAutomationProvider** — derive from the base **DataCellUIAutomationProvider** class. This base class defines the core automation behavior that these providers extend for their specific cell types.
+
+|Column Cells|Telerik UIA Cell Provider|UIA Control Type|
+|------|------|------|
+|GridViewRowHeaderColumn|DataRowHeaderItemUIAutomationProvider|[HeaderItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-headeritem-control-type)|
+|GridViewSelectColumn|DataRowSelectCellUIAutomationProvider|[CheckBox](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-checkbox-control-type)|
+|GridViewTextBoxColumn|DataCellEditUIAutomationProvider|[Edit](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-edit-control-type)|
+|GridViewDecimalColumn|DataCellSpinnerUIAutomationProvider|[Spinner](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-spinner-control-type)|
+|GridViewDateTimeColumn|DataCellUIAutomationProvider|[DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type)|
+|GridViewCheckBoxColumn|DataCellCheckboxUIAutomationProvider|[CheckBox](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-checkbox-control-type)|
+|GridViewHyperlinkColumn|DataCellHyperLinkUIAutomationProvider|[Hyperlink](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-hyperlink-control-type)|
+|GridViewCommandColumn|DataCellCommandUIAutomationProvider|[Button](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-button-control-type)|
+|GridViewComboBoxColumn|DataCellComboBoxUIAutomationProvider|[ComboBox](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-combobox-control-type)|
+|GridViewBrowseColumn|DataCellEditUIAutomationProvider|[Edit](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-edit-control-type)|
+|GridViewCalculatorColumn|DataCellUIAutomationProvider|[DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type)|
+|GridViewColorColumn|DataCellUIAutomationProvider|[DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type)|
+|GridViewTimeSpanColumn|DataCellUIAutomationProvider|[DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type)|
+|GridViewImageColumn|DataCellImageUIAutomationProvider|[Image](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-image-control-type)|
+|GridViewMaskBoxColumn|DataCellEditUIAutomationProvider|[Edit](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-edit-control-type)|
+|GridViewColorColumn|DataCellUIAutomationProvider|[DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type)|
+|RadMultiColumnComboBoxElement|DataCellUIAutomationProvider|[DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type)|
+|GridViewRatingColumn|DataCellUIAutomationProvider|[DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type)|
+|GridViewSparklineColumn|DataCellUIAutomationProvider|[DataItem](https://learn.microsoft.com/en-us/dotnet/framework/ui-automation/ui-automation-support-for-the-dataitem-control-type)|
+
+
+#### DataRowHeaderItemUIAutomationProvider
+
+Used primarily for row header cells, this provider ensures that header elements are correctly announced and interactable through assistive technologies.
+
+* AutomationElementIdentifiers.ControlTypeProperty.Id => "header item"
+* AutomationElementIdentifiers.LocalizedControlTypeProperty.Id => "header item"
+* AutomationElementIdentifiers.IsOffscreenProperty.Id
+* AutomationElementIdentifiers.NameProperty.Id
+* AutomationElementIdentifiers.IsContentElementProperty.Id
+* AutomationElementIdentifiers.IsControlElementProperty.Id
+* AutomationElementIdentifiers.IsKeyboardFocusableProperty.Id
+* AutomationElementIdentifiers.IsInvokePatternAvailableProperty.Id
+
+The following items outlines the supported automation patterns by the **DataRowHeaderItemUIAutomationProvider**.
+
+* [InvokePattern](https://learn.microsoft.com/en-us/dotnet/api/system.windows.automation.provider.iinvokeprovider?view=windowsdesktop-9.0)
+
+#### DataRowSelectCellUIAutomationProvider
+
+this provider enables UI Automation support for selection cells, typically rendered as checkboxes.
+
+* AutomationElementIdentifiers.ControlTypeProperty.Id => ControlType.CheckBox.Id
+* AutomationElementIdentifiers.LocalizedControlTypeProperty.Id => "check box"
+* AutomationElementIdentifiers.IsOffscreenProperty.Id
+* AutomationElementIdentifiers.NameProperty.Id
+* AutomationElementIdentifiers.IsContentElementProperty.Id
+* AutomationElementIdentifiers.IsControlElementProperty.Id
+* AutomationElementIdentifiers.IsKeyboardFocusableProperty.Id
+* AutomationElementIdentifiers.IsInvokePatternAvailableProperty.Id
+
+The following items outlines the supported automation patterns by the **DataRowSelectCellUIAutomationProvider**.
+
+* [TogglePattern](https://learn.microsoft.com/en-us/dotnet/api/system.windows.automation.provider.itoggleprovider?view=windowsdesktop-9.0)
+
+#### DataCellUIAutomationProvider
+
+A general-purpose provider used for various content cells.
+
+* AutomationElementIdentifiers.AutomationIdProperty.Id
+* AutomationElementIdentifiers.ControlTypeProperty.Id => ControlType.CheckBox.Id
+* AutomationElementIdentifiers.LocalizedControlTypeProperty.Id => "data item"
+* AutomationElementIdentifiers.IsOffscreenProperty.Id
+* AutomationElementIdentifiers.NameProperty.Id
+* AutomationElementIdentifiers.IsContentElementProperty.Id
+* AutomationElementIdentifiers.IsControlElementProperty.Id
+* AutomationElementIdentifiers.IsKeyboardFocusableProperty.Id
+* AutomationElementIdentifiers.IsInvokePatternAvailableProperty.Id
+
+The following items outlines the supported automation patterns by the base **DataCellUIAutomationProvider**.
+
+* [Invoke Pattern](https://learn.microsoft.com/en-us/dotnet/api/system.windows.automation.provider.iinvokeprovider?view=windowsdesktop-9.0)
+* [Value Pattern](https://learn.microsoft.com/en-us/dotnet/api/system.windows.automation.valuepattern?view=windowsdesktop-9.0)
+* [Selection Item Pattern](https://learn.microsoft.com/en-us/dotnet/api/system.windows.automation.provider.iselectionitemprovider?view=windowsdesktop-9.0)
+* [Scroll Item Pattern](https://learn.microsoft.com/en-us/dotnet/api/system.windows.automation.provider.iscrollitemprovider?view=windowsdesktop-9.0)
+* [Grid Item Pattern](https://learn.microsoft.com/en-us/dotnet/api/system.windows.automation.provider.igriditemprovider?view=windowsdesktop-9.0)
+* [Table Item Pattern](https://learn.microsoft.com/en-us/dotnet/api/system.windows.automation.provider.itableitemprovider?view=windowsdesktop-9.0)
+
+#### DataCellEditUIAutomationProvider
+
+This provider handles editable cells and reports them as ControlType.Edit.
+
+* AutomationElementIdentifiers.ControlTypeProperty.Id => ControlType.Edit.Id
+* AutomationElementIdentifiers.LocalizedControlTypeProperty.Id => "edit"
+* AutomationElementIdentifiers.IsControlElementProperty.Id => true
+
+#### DataCellSpinnerUIAutomationProvider
+
+Spinner cells, such as those in numeric columns, are handled by this provider.
+
+* AutomationElementIdentifiers.ControlTypeProperty.Id => ControlType.Spinner.Id
+* AutomationElementIdentifiers.LocalizedControlTypeProperty.Id => "spinner"
+
+
+
diff --git a/controls/map/providers/azure-map/azuremapprovider.md b/controls/map/providers/azure-map/azuremapprovider.md
new file mode 100644
index 000000000..4064068c2
--- /dev/null
+++ b/controls/map/providers/azure-map/azuremapprovider.md
@@ -0,0 +1,73 @@
+---
+title: Azure Map Custom Provider
+page_title: Azure Map Custom Provider - RadMap
+description: RadMap can visualize tile data from the Azure API services as well as from the local file system.
+slug: map-providers-azure-overview
+tags: map, providers,azure
+published: True
+position: 0
+---
+
+# Azure Map Provider
+
+The RadMap control supports visualizing tile data using the Azure Maps services. This is done via the AzureMapProvider class. This provider supports both raster and vector sources.
+
+>important The AzureMapProvider class is introduced with the Q3 2025 official version of our controls.
+
+
+
+## Setting the AzureMapProvider
+
+To use this provider, create a new AzureMapProvider instance and add it to the `Providers` collection of the RadMap control. After that, you will need to set the subscription key of the user's Azure account to the `AzureAPIKey` property of the AzureMapProvider instance. To obtain a key, you can review the [Manage authentication in Azure Maps](https://learn.microsoft.com/en-gb/azure/azure-maps/how-to-manage-authentication#view-authentication-details/) article.
+
+#### Using AzureMapProvider
+
+````C#
+
+string cacheFolder = @"..\..\cache";
+AzureMapProvider provider = new AzureMapProvider();
+provider.TileSetID = AzureTileSet.Road;
+provider.AzureAPIKey = AzureAPIKey;
+LocalFileCacheProvider cache = new LocalFileCacheProvider(cacheFolder);
+provider.CacheProvider = cache;
+this.radMap1.Providers.Add(provider);
+
+````
+````VB.NET
+
+Dim cacheFolder As String = "..\..\cache"
+Dim provider As New AzureMapProvider()
+provider.TileSetID = AzureTileSet.Road
+provider.AzureAPIKey = AzureAPIKey
+Dim cache As New LocalFileCacheProvider(cacheFolder)
+provider.CacheProvider = cache
+Me.radMap1.Providers.Add(provider)
+
+````
+
+{{endregion}}
+
+
+## Language
+
+The Azure Maps services provide a culture parameter in its URL address and the AzureMapProvider allows you to utilize it. To do so, set the `LanguageCulture` property to the desired culture string.
+
+````C#
+
+provider.LanguageCulture = new CultureInfo("bg-BG");
+
+````
+````VB.NET
+
+provider.LanguageCulture = new CultureInfo("bg-BG")
+
+````
+
+
+
+
+## Azure API Version
+
+The AzureMapProvider provides the functionality to specify the [Render](https://learn.microsoft.com/en-us/rest/api/maps/render?view=rest-maps-2025-01-01) Rest API version of the Azure Maps services. This is done via the `AzureAPIVersion` property of the provider. The lastest version of the Render Rest API is __2024-04-01__ and the AzureMapProvider uses it.
+
+
diff --git a/controls/map/providers/azure-map/images/azure_map_provider_1.png b/controls/map/providers/azure-map/images/azure_map_provider_1.png
new file mode 100644
index 000000000..5e943326e
Binary files /dev/null and b/controls/map/providers/azure-map/images/azure_map_provider_1.png differ
diff --git a/controls/map/providers/azure-map/images/azure_map_provider_2.png b/controls/map/providers/azure-map/images/azure_map_provider_2.png
new file mode 100644
index 000000000..f6849c413
Binary files /dev/null and b/controls/map/providers/azure-map/images/azure_map_provider_2.png differ
diff --git a/controls/map/providers/azure-map/images/map-providers-azure-search001.gif b/controls/map/providers/azure-map/images/map-providers-azure-search001.gif
new file mode 100644
index 000000000..7ade2e18e
Binary files /dev/null and b/controls/map/providers/azure-map/images/map-providers-azure-search001.gif differ
diff --git a/controls/map/providers/azure-map/properties-methods-events.md.md b/controls/map/providers/azure-map/properties-methods-events.md.md
new file mode 100644
index 000000000..f582558e8
--- /dev/null
+++ b/controls/map/providers/azure-map/properties-methods-events.md.md
@@ -0,0 +1,52 @@
+---
+title: Properties, Methods and Events
+page_title: Properties, Methods and Events - AzureMapProvider
+description: Telerik RadMap AzureMapProvider
+slug: map-providers-azure-properties
+tags: azuremapprovider, methods, properties, events
+published: True
+position: 1
+---
+
+# Properties, Methods and Events
+
+This article provides reference tables with the [Properties](#properties), [Methods](#methods) and [Events](#events) in RadMap - AzureMapProvider.
+
+## Properties
+
+|Property|Description|
+|----|----|
+|__AzureAPIKey__|Gets or sets the Azure key.|
+|__AzureAPIVersion__|Gets or sets the Azure API version.|
+|__LanguageCulture__|Gets or sets the language and culture used for Azure Maps requests.|
+|__Initializing__|Gets or sets a value indicating whether this __AzureMapProvider__ is currently in the initialization process.|
+|__TileSetID__|Gets or sets the imagery set. The possible values are: *DarkGrey*, *HybridDarkGrey*, *HybridRoad*, *LabelsDarkGrey*, *LabelsRoad*, *Road*, *TrafficAbsoluteMain*, *TrafficDelayMain*, *TrafficReducedMain*, *TrafficRelativeDark*, *TrafficRelativeMain*, *WeatherInfraredMain*, *WeatherRadarMain*
+|__Initialized__|Gets or sets a value indicating whether this __AzureRestMapProvider__ is initialized.|
+|__MaxZoomLevel__|Gets or sets the maximum zoom level.|
+|__MinZoomLevel__|Gets or sets the minimum zoom level.|
+|__TileSize__|Gets the tile size.|
+|__CacheProvider__|Gets or sets the provider used for data caching.|
+|__EnableCaching__|Gets or set a value whether the caching is enabled.|
+|__TileDownloader__|Gets or sets the tile downloader.|
+
+## Methods
+
+|Method|Description|
+|----|----|
+|__Initialize__|Initializes this provider.|
+|__GetTile__|Gets the tile uri.|
+|__GetTileImage__|Gets the tile image.|
+|__SearchAsync__|Performs search request asynchronously.|
+|__CalculateElevationAsync__|Calculates the elevation asynchronously.|
+|__GetSupportedViews__|Gets the supported views.|
+|__SetView__|Sets the view in the AzureMapProvider.|
+
+## Events
+
+|Event|Description|
+|----|----|
+|__InitializationComplete__|Fires when the initialization is completed.|
+|__InitializationError__|Fires when an error during the initialization occurs.|
+|__ProviderUpdated__|Fires when the provider has been updated, e.g. when a tile is downloaded.|
+|__SearchCompleted__|Fires when the search request has completed.|
+|__SearchError__|Fires when an error|
diff --git a/controls/map/providers/azure-map/search.md b/controls/map/providers/azure-map/search.md
new file mode 100644
index 000000000..ff185f10b
--- /dev/null
+++ b/controls/map/providers/azure-map/search.md
@@ -0,0 +1,181 @@
+---
+title: Search
+page_title: Search - WinForms Map Control
+description: WinForms Map allows you to implement search functionality, that will let the user search for a specific location on the map.
+slug: map-providers-azure-search
+tags: map, providers, search
+published: True
+position: 2
+---
+
+# Search
+
+__RadMap - AzureMapProvider__ allows you to implement search functionality, that will let the user search for a specific location on the map. The search is performed through an __IMapBaseSearchProvider__, which communicates with the respective map provider's services. __AzureMapProvider__ implements the __IAzureMapSearchProvider__ interface that inherits the __IMapBaseSearchProvider__.
+
+>caption Figure 1: Azure search
+
+
+
+In order to use the built-in search bar that __RadMap__ offers set the __ShowSearchBar__ property to *true*. Depending on the amount of control you want to have over the search you can do one of three things.
+
+* First, you can subscribe to the __MapSearchBarElement__'s __SearchCriteriaChanged__ event. In the event handler you will receive the search criteria and you are responsible for the rest of the search handling. That is __RadMap__ will not perform any further actions related to the search.
+
+* Second, if you have not subscribed to the __SearchCriteriaChanged__ event you can set the SearchBarElement.__SearchProvider__ property to an __IMapBaseSearchProvider__ instance. When you do this __RadMap__ will initiate a new search through that provider. You should still handle the search result through the provider's __SearchCompleted__ and __SearchError__ events.
+
+* Third, if you have not subscribed to the event and you have not set the SearchBarElement.__SearchProvider__ property __RadMap__ will go through its __Providers__ collection and will initiate a search through the first provider that implements the __IMapBaseSearchProvider__. Results will be displayed in a layer named *Search*. If the layer does not exist it will be added by __RadMap__. You should note that all overlays will be removed from the *Search* layer when a new search is initiated.
+
+In this example we will use the second approach by setting the MapElement.SearchBarElement.__SearchProvider__ property to the __AzureMapProvider__ that the map is currently using. Then, subscribe to the __SearchProvider__'s __SearchCompleted__ and __SearchError__ events. The __SearchCompletedEventArgs__ gives you the __Locations__ result which can be used to place a __MapPin__ to the added *pins* __MapLayer__ for each search result. The __SearchError__ event is the place for handling any kind of errors that occur during the search operation.
+
+#### Azure search
+
+````C#
+
+protected override void OnLoad(EventArgs e)
+{
+ base.OnLoad(e);
+
+ this.radMap1.ShowSearchBar = true;
+ AzureMapProvider azureProvider = this.radMap1.Providers[0] as AzureMapProvider;
+ Telerik.WinControls.UI.MapLayer pinsLayer = new MapLayer("Pins");
+ this.radMap1.Layers.Add(pinsLayer);
+ this.radMap1.MapElement.SearchBarElement.SearchProvider = azureProvider;
+
+ azureProvider.SearchCompleted += AzureProvider_SearchCompleted;
+ azureProvider.SearchError += AzureProvider_SearchError;
+}
+
+private void AzureProvider_SearchError(object sender, SearchErrorEventArgs e)
+{
+ RadMessageBox.Show(e.Error.Message);
+}
+
+private void AzureProvider_SearchCompleted(object sender, AzureSearchCompletedEventArgs e)
+{
+ Telerik.WinControls.UI.Map.RectangleG allPoints = new Telerik.WinControls.UI.Map.RectangleG(double.MinValue, double.MaxValue, double.MaxValue, double.MinValue);
+ this.radMap1.Layers["Pins"].Clear();
+
+ foreach (Result result in e.AzureResponse.Results)
+ {
+ var latitude = result.Position.Latitude;
+ var longitude = result.Position.Longitude;
+ Telerik.WinControls.UI.Map.PointG point = new Telerik.WinControls.UI.Map.PointG(latitude, longitude);
+ MapPin pin = new MapPin(point);
+ pin.Size = new System.Drawing.Size(20, 40);
+ pin.BackColor = Color.Red;
+ pin.ToolTipText = result.Address.FreeformAddress;
+
+ this.radMap1.MapElement.Layers["Pins"].Add(pin);
+ allPoints.North = Math.Max(allPoints.North, point.Latitude);
+ allPoints.South = Math.Min(allPoints.South, point.Latitude);
+ allPoints.West = Math.Min(allPoints.West, point.Longitude);
+ allPoints.East = Math.Max(allPoints.East, point.Longitude);
+ }
+ if (e.AzureResponse.Results.Length > 0)
+ {
+ if (e.AzureResponse.Results.Length == 1)
+ {
+ var latitude = e.AzureResponse.Results[0].Position.Latitude;
+ var longitude = e.AzureResponse.Results[0].Position.Longitude;
+ this.radMap1.BringIntoView(new Telerik.WinControls.UI.Map.PointG(latitude, longitude));
+ }
+ else
+ {
+ this.radMap1.MapElement.BringIntoView(allPoints);
+ this.radMap1.Zoom(this.radMap1.MapElement.ZoomLevel - 1);
+ }
+ }
+ else
+ {
+ RadMessageBox.Show("No result found for the provided search query!");
+ }
+}
+
+````
+````VB.NET
+
+Protected Overrides Sub OnLoad(e As EventArgs)
+ MyBase.OnLoad(e)
+
+ Me.radMap1.ShowSearchBar = True
+ Dim azureProvider As AzureMapProvider = TryCast(Me.radMap1.Providers(0), AzureMapProvider)
+ Dim pinsLayer As New Telerik.WinControls.UI.MapLayer("Pins")
+ Me.radMap1.Layers.Add(pinsLayer)
+ Me.radMap1.MapElement.SearchBarElement.SearchProvider = azureProvider
+
+ AddHandler azureProvider.SearchCompleted, AddressOf AzureProvider_SearchCompleted
+ AddHandler azureProvider.SearchError, AddressOf AzureProvider_SearchError
+End Sub
+
+Private Sub AzureProvider_SearchError(sender As Object, e As SearchErrorEventArgs)
+ RadMessageBox.Show(e.Error.Message)
+End Sub
+
+Private Sub AzureProvider_SearchCompleted(sender As Object, e As AzureSearchCompletedEventArgs)
+ Dim allPoints As New Telerik.WinControls.UI.Map.RectangleG(Double.MinValue, Double.MaxValue, Double.MaxValue, Double.MinValue)
+ Me.radMap1.Layers("Pins").Clear()
+
+ For Each result As Result In e.AzureResponse.Results
+ Dim latitude = result.Position.Latitude
+ Dim longitude = result.Position.Longitude
+ Dim point As New Telerik.WinControls.UI.Map.PointG(latitude, longitude)
+ Dim pin As New MapPin(point)
+ pin.Size = New System.Drawing.Size(20, 40)
+ pin.BackColor = Color.Red
+ pin.ToolTipText = result.Address.FreeformAddress
+
+ Me.radMap1.MapElement.Layers("Pins").Add(pin)
+ allPoints.North = Math.Max(allPoints.North, point.Latitude)
+ allPoints.South = Math.Min(allPoints.South, point.Latitude)
+ allPoints.West = Math.Min(allPoints.West, point.Longitude)
+ allPoints.East = Math.Max(allPoints.East, point.Longitude)
+ Next
+
+ If e.AzureResponse.Results.Length > 0 Then
+ If e.AzureResponse.Results.Length = 1 Then
+ Dim latitude = e.AzureResponse.Results(0).Position.Latitude
+ Dim longitude = e.AzureResponse.Results(0).Position.Longitude
+ Me.radMap1.BringIntoView(New Telerik.WinControls.UI.Map.PointG(latitude, longitude))
+ Else
+ Me.radMap1.MapElement.BringIntoView(allPoints)
+ Me.radMap1.Zoom(Me.radMap1.MapElement.ZoomLevel - 1)
+ End If
+ Else
+ RadMessageBox.Show("No result found for the provided search query!")
+ End If
+End Sub
+
+````
+
+>note Enter some text in the search box and press `Enter` to start searching.
+
+>note The **MapSearchBarElement** can be setup with no explicit search provider. In this case the search element will traverse the providers collection of **RadMapElement** for a **IMapBaseSearchProvider** instance. The MapSearchBarElement.**ShowMessageBoxOnError** property determines whether a messagebox will be displayed upon error or not when the **SearchProvider** property of the element is not set. The default value of the property is set to *true*.
+
+## Azure Search Request
+
+You can perform searching programmatically by using a __AzureSearchRequest__:
+
+
+````C#
+
+AzureSearchRequest request = new AzureSearchRequest();
+request.Query = "San Marino";
+request.SearchOptions.Count = 10;
+AzureMapProvider azureMapProvider = this.radMap1.Providers[0] as AzureMapProvider;
+azureMapProvider.SearchAsync(request);
+
+````
+````VB.NET
+Dim request As New AzureSearchRequest()
+request.Query = "San Marino"
+request.SearchOptions.Count = 10
+Dim azureMapProvider As AzureMapProvider = TryCast(Me.radMap1.Providers(0), AzureMapProvider)
+azureMapProvider.SearchAsync(request)
+
+
+````
+
+
+>note It is necessary to handle the __AzureMapProvider__'s __SearchCompleted__ and __SearchError__ events as it is demonstrated above.
+
+## See Also
+* [AzureMapProvider]({%slug map-providers-azure-overview%})
diff --git a/controls/map/providers/azuremapprovider.md b/controls/map/providers/azuremapprovider.md
deleted file mode 100644
index 6c3f590d4..000000000
--- a/controls/map/providers/azuremapprovider.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Azure Map Custom Provider
-page_title: Azure Map Custom Provider - RadMap
-description: RadMap can visualize tile data from the Azure API services as well as from the local file system.
-slug: winforms/map/providers/azure
-tags: map, providers,azure
-published: True
-position: 1
----
-
-# Azure Map Custom Provider
-
-As of June 30, 2025, [Bing Maps](https://www.bingmapsportal.com/) will be deprecated. To support this transition, we’ve provided an [SDK example in our GitHub repository](https://github.com/telerik/winforms-sdk/tree/master/Map/Custom%20Azure%20Provider) that demonstrates how to create a custom provider leveraging the Azure Maps API. Developers intending to use this approach will need to obtain a valid Azure Maps subscription key.
-
diff --git a/controls/map/providers/overview.md b/controls/map/providers/overview.md
index e15536329..ff1df91eb 100644
--- a/controls/map/providers/overview.md
+++ b/controls/map/providers/overview.md
@@ -12,7 +12,7 @@ position: 0
The __RadMap__ control needs a provider of imagery data in order to display a map. Currently, __RadMap__ supports the following providers:
-* [AzureMap Custom Provider]({%slug winforms/map/providers/azure%})
+* [AzureMapProvider]({%slug map-providers-azure-overview%})
* [BingRestMapProvider]({%slug winforms/map/providers/bingrestmapprovider%})
* [OpenStreetMapProvider]({%slug winforms/map/providers/openstreetmapprovider%})
* [LocalMapProvider]({%slug winforms/map/providers/localmapprovider%})
diff --git a/controls/richtexteditor/events.md b/controls/richtexteditor/events.md
index 34d37e48d..7ee0d176e 100644
--- a/controls/richtexteditor/events.md
+++ b/controls/richtexteditor/events.md
@@ -87,7 +87,7 @@ The __RadRichTextEditor__ control raises the following specific events:
* An __EventArgs__ object.
-* __HyperlinkClicked__ - Occurs when the users clicks on a hyperlink in the current document. The event allows you to either cancel or replace the navigation logic. HyperlinkClicked event can be used as a confirmation from the end-user whether to proceed or not with opening a hyperlink due to security reasons. The event handler receives two arguments:
+* __HyperlinkClicked__ - occurs when the users clicks on a hyperlink in the current document. The event allows you to either cancel or replace the navigation logic. HyperlinkClicked event can be used as a confirmation from the end-user whether to proceed or not with opening a hyperlink due to security reasons. The event handler receives two arguments:
* The sender argument contains the __Span__ containing the hyperlink's content. This argument is of type object, but can be cast to the __Span__ type.
@@ -114,7 +114,12 @@ The __RadRichTextEditor__ control raises the following specific events:
* The sender argument contains the __RadRichTextEditor__. This argument is of type object, but can be cast to the __RadRichTextEditor__ type.
* A __SelectedLayoutBoxChangedEventArgs__ object.
-
+
+* __BeforeOpenFile__ - occurs before a file is opened, before the open file dialog is shown. Subscribe to this event to customize the OpenFileDialog properties (like FileName, Title, Filter, InitialDirectory, etc.) before it is displayed to the user. Allows to be canceled by setting e.Cancel to true.
+
+* __BeforeSaveFile__ - occurs before the file is saved, before the save file dialog is shown. Subscribe to this event to customize the SaveFileDialog properties (like FileName, Title, Filter, InitialDirectory, etc.) before it is displayed to the user. Allows to be canceled by setting e.Cancel to true.
+
+
# See Also
* [Getting Started]({%slug winforms/richtexteditor-/getting-started%})
diff --git a/controls/spreadsheet/events.md b/controls/spreadsheet/events.md
index c214628a9..9037996e0 100644
--- a/controls/spreadsheet/events.md
+++ b/controls/spreadsheet/events.md
@@ -106,9 +106,36 @@ End Sub
* **WorkbookContentChanged**: Occurs when the content of the workbook is changed.
+* **BeforeOpenFile**: Occurs before a file is opened, before the open file dialog is shown. Subscribe to this event to customize the OpenFileDialog properties (like FileName, Title, Filter, InitialDirectory, etc.) before it is displayed to the user. Allows to be canceled by setting e.Cancel to true.
-## Workbook Events
+* **BeforeSaveFile**: Occurs before the file is saved, before the save file dialog is shown. Subscribe to this event to customize the SaveFileDialog properties (like FileName, Title, Filter, InitialDirectory, etc.) before it is displayed to the user. Allows to be canceled by setting e.Cancel to true.
+
+#### Example 3: Specify FileName, Title, Filter properties before saving a file in SaveFileDialog
+
+{{source=..\SamplesCS\Spreadsheet\Events.cs region=radspreadsheet-events_4}}
+{{source=..\SamplesVB\Spreadsheet\Events.vb region=radspreadsheet-events_4}}
+````C#
+private void RadSpreadsheet_BeforeSaveFile(object sender, Telerik.WinForms.Controls.Spreadsheet.Worksheets.SaveFileDialogEventArgs e)
+{
+ e.Dialog.FileName = "TelerikSpreadsheet.xlsx"; // Default file name
+ e.Dialog.Title = "Open Spreadsheet File"; // Title of the dialog
+ e.Dialog.Filter = "Spreadsheet files (*.xlsx)|*.xlsx|All files (*.*)|*.*"; // Filter for the file types
+}
+
+````
+````VB.NET
+Private Sub RadSpreadsheet_BeforeSaveFile(ByVal sender As Object, ByVal e As Telerik.WinForms.Controls.Spreadsheet.Worksheets.SaveFileDialogEventArgs)
+ e.Dialog.FileName = "TelerikSpreadsheet.xlsx" ' Default file name
+ e.Dialog.Title = "Open Spreadsheet File" ' Title of the dialog
+ e.Dialog.Filter = "Spreadsheet files (*.xlsx)|*.xlsx|All files (*.*)|*.*" ' Filter the file types
+End Sub
+
+````
+{{endregion}}
+
+
+## Workbook Events
* **ActiveSheetChanged**: Occurs when the active sheet is changed.
@@ -157,7 +184,7 @@ End Sub
* **HyperlinkClicked**: Occurs when a hyperlink in the document gets clicked. The event allows you to either cancel or replace the navigation logic. HyperlinkClicked event can be used as a confirmation from the end-user whether to proceed or not with opening a hyperlink due to security reasons.
With the 2024 Q3 (2024.3.924), the default navigation behavior of the hyperlinks is to automatically open only valid and trusted addresses. The hyperlink navigation can be canceled by either setting the __Handled__ property of the HyperlinkClickedEventArgs to _true_ or __IsTrustedUrl__ to _false_.
-#### Example 3: Using the HyperlinkClicked event to implement confirmation for the clicked links in the document
+#### Example 4: Using the HyperlinkClicked event to implement confirmation for the clicked links in the document
{{source=..\SamplesCS\Spreadsheet\Events.cs region=HyperlinkClickedEvent}}
{{source=..\SamplesVB\Spreadsheet\Events.vb region=HyperlinkClickedEvent}}
@@ -207,7 +234,7 @@ End Sub
* **CellPropertyChanged**: Occurs when a property of a cell is changed. The event arguments are of type **CellPropertyChangedEventArgs** and expose information about the exact property that was changed as well as the affected cell range. **Example 3** demonstrates how you can use the event to get a notification when the users change the fill of a cell.
-#### Example 4: Using the CellPropertyChangedEvent
+#### Example 5: Using the CellPropertyChangedEvent
{{source=..\SamplesCS\Spreadsheet\Events.cs region=radspreadsheet-events_3}}
{{source=..\SamplesVB\Spreadsheet\Events.vb region=radspreadsheet-events_3}}
diff --git a/controls/spreadsheet/features/images/RadSpreadsheet_UI_Selection_14.png b/controls/spreadsheet/features/images/RadSpreadsheet_UI_Selection_14.png
new file mode 100644
index 000000000..5986a2ab9
Binary files /dev/null and b/controls/spreadsheet/features/images/RadSpreadsheet_UI_Selection_14.png differ
diff --git a/controls/spreadsheet/features/ui-working-with-selection.md b/controls/spreadsheet/features/ui-working-with-selection.md
index e55eca5cc..98d0bb4b1 100644
--- a/controls/spreadsheet/features/ui-working-with-selection.md
+++ b/controls/spreadsheet/features/ui-working-with-selection.md
@@ -394,6 +394,55 @@ If a formula is already entered and you would like to see the references used in
+## Working with the Current Region
+
+The current region concept is represented by a **CellRange** object that contains all adjacent non-empty cells around the active cell of the **Selection** object. The range expands around the active cell in all directions, until it reaches empty cells.
+
+
+
+#### Get current region
+
+{{source=..\SamplesCS\Spreadsheet\SelectionCode.cs region=selection_14}}
+{{source=..\SamplesVB\Spreadsheet\SelectionCode.vb region=selection_14}}
+````C#
+Selection selection = this.radSpreadsheet.ActiveWorksheetEditor.Selection;
+CellRange currentRegion = selection.CurrentRegion;
+
+````
+````VB.NET
+Dim selection As Selection = Me.radSpreadsheet.ActiveWorksheetEditor.Selection
+Dim currentRegion As CellRange = selection.CurrentRegion
+
+````
+
+{{endregion}}
+
+To select the current region, call the SelectCurrentRegion method of the CellPosition instance.
+
+#### Select current region programmatically
+{{source=..\SamplesCS\Spreadsheet\SelectionCode.cs region=selection_15}}
+{{source=..\SamplesVB\Spreadsheet\SelectionCode.vb region=selection_15}}
+````C#
+Selection selection = this.radSpreadsheet.ActiveWorksheetEditor.Selection;
+CellPosition activePosition = selection.ActiveRange.ActivePosition;
+bool result = activePosition.SelectCurrentRegion();
+//or
+selection.Select(selection.CurrentRegion);
+
+````
+````VB.NET
+Dim selection As Selection = Me.radSpreadsheet.ActiveWorksheetEditor.Selection
+Dim activePosition As CellPosition = selection.ActiveRange.ActivePosition
+Dim result As Boolean = activePosition.SelectCurrentRegion()
+'or
+selection.Select(selection.CurrentRegion)
+
+````
+
+{{endregion}}
+
+The current region can also be selected using the following keyboard combination: `Ctrl+Shift+Asterisk sign(8*)`
+
# See Also
* [How to Access RadSpreadsheet's Editor]({%slug access-editor-in-spreadsheet%})
diff --git a/core/core-migration.md b/core/core-migration.md
index 7c4bb4abc..fc4d79e3c 100644
--- a/core/core-migration.md
+++ b/core/core-migration.md
@@ -1,29 +1,25 @@
---
-title: Migrating to .NET Core
-page_title: Migrating to .NET Core - NET Core
-description: Learn how to migrate to .NET Core.
+title: Migrating to .NET
+page_title: Migrating to .NET
+description: Learn how to migrate to .NET
slug: core-migration
tags: core, getting, started
published: True
position: 3
---
-# Migrating to .NET Core
+# Migrating to .NET
-## Requirements
+This article shows how to migrate from an existing WinForms .NET Framework project to a .NET project (.NET 8 or later).
Before proceeding with this article please make sure that the following requirements are met:
-* Visual Studio 2017 Update 15.8 or higher and select the .NET desktop development workload with the following options:
- - .NET Framework 4.7.2 development tools
- - .NET Core 2.1 development tools
-* .NET Core 3.0 SDK - DownLoad from here: [.NET Core Daily Builds](https://github.com/dotnet/core/blob/master/daily-builds.md)
-* Telerik UI for Winforms R1 2019 or newer.
-* Visual Studio 2019 to open the .NET Core project.
+* **Visual Studio 2022 v17.0 and newer**
+* **Telerik UI for WinForms NuGet package installed**
## Example
-1\. Create a new WinForms application using one of our [templates]({%slug winforms/visual-studio-templates%}). This way you will have a fully functional application that you will migrate to .NET core (at this point the .NET Core does not provide a designer and this is why you cannot start by creating a new application). You can use any application that uses the Telerik UI for Winforms controls as well.
+1\. Create a new WinForms application using one of our [templates]({%slug winforms/visual-studio-templates%}). This way you will have a fully functional application that you will migrate to .NET. You can use any application that uses the Telerik UI for Winforms controls as well.
In this case I am using the excel inspired template.
@@ -36,7 +32,7 @@ In this case I am using the excel inspired template.
-2\. You need to create a WinForms .NET Core project. Currently this can be done from the Conosle. Open a new *Development Command Prompt for VS2017* and type the following command (you can use any preferred directory).
+2\. You need to create a WinForms .NET project. Currently this can be done from the Conosle. Open a new *Development Command Prompt for VS2017* and type the following command (you can use any preferred directory).
#### Creating WinForms project from the Command Prompt
@@ -47,11 +43,11 @@ Once this is done you will see the following message.
-3\. Now open the project in Visual Studio 2019. Go to the Solution Explorer and right click dependencies and then click Add Reference. Navigate to the install folder of the winforms suite and choose the __NetCore__ folder. Select all required assemblies (you can see them in the standard project).
+3\. Now open the project in Visual Studio 2022. Go to the Solution Explorer and right click dependencies and then click Add Reference. Navigate to the install folder of the winforms suite and choose the __NetCore__ folder. Select all required assemblies (you can see them in the standard project).
-4\. In Visual Studio 2019 go to Project -> Add Existing Item. Navigate to the standard application and select the form files.
+4\. In Visual Studio 2022 go to Project -> Add Existing Item. Navigate to the standard application and select the form files.
diff --git a/core/core-project-and-document-processing-library.md b/core/core-project-and-document-processing-library.md
index c854e58ac..3c7896531 100644
--- a/core/core-project-and-document-processing-library.md
+++ b/core/core-project-and-document-processing-library.md
@@ -1,18 +1,18 @@
---
-title: Document Processing Library and WinForms .NET Core application
-page_title: Document Processing Library and WinForms .NET Core application
+title: Document Processing Library and WinForms .NET application
+page_title: Document Processing Library and WinForms .NET application
description:
slug: core-project-and-document-processing-library
-tags: document processing, WinForms application, .NET Core
+tags: document processing, WinForms application, .NET
published: True
position: 5
---
-# Telerik Document Processing Libraries and WinForms .NET Core application.
+# Telerik Document Processing Libraries and WinForms .NET application
Since the Telerik Document Processing Libraries depend on some types from WPF using any library in a WinForms application requires making changes in the project file. This is not necessary in the .NET framework projects where you can just add the references in Visual Studio.
-By default, when creating a WinForms .NET Core application the **Microsoft.WindowsDesktop.App.WindowsForms** framework is added. This does not include the required WPF references.
+By default, when creating a WinForms .NET application the **Microsoft.WindowsDesktop.App.WindowsForms** framework is added. This does not include the required WPF references.
diff --git a/core/core-toolbox-version.md b/core/core-toolbox-version.md
index 6a6b5f9df..ccbf8036e 100644
--- a/core/core-toolbox-version.md
+++ b/core/core-toolbox-version.md
@@ -1,20 +1,20 @@
---
-title: Adding RadControls to Visual Studio Toolbox in .NET Core Projects
-page_title: NET Core Toolbox Version
+title: Adding RadControls to Visual Studio Toolbox in .NET Projects
+page_title: NET Toolbox Version
description:
slug: core-toolbox-version
-tags: core, designer, toolbox, net core
+tags: core, designer, toolbox, net, .NET, winforms
published: True
-position: 1
+position: 4
---
-# Adding RadControls to Visual Studio Toolbox in .NET Core Projects
+# Adding RadControls to Visual Studio Toolbox in .NET Projects
-Telerik UI for WinForms controls used to be automatically added to Visual Studio's Toolbox during the [installation]({%slug winforms/installation-deployment-and-distribution/adding-radcontrols-to-visual-studio-toolbox%}) process when using **.NET 2.0 (up to 4.8)** Framework in your project. This means that the Toolbox population relies on the Telerik WinForms version available in the Global Assembly Cache.
+Telerik UI for WinForms controls used to be automatically added to Visual Studio's Toolbox during the [installation]({%slug winforms/installation-deployment-and-distribution/adding-radcontrols-to-visual-studio-toolbox%}) process when using **.NET Framework (up to 4.8)** in your project. This means that the Toolbox population relies on the Telerik WinForms version available in the Global Assembly Cache.
-With the introduction of .NET Core/.NET 5 and the WinForms designer, the Toolbox configuration doesn't rely on the GAC anymore and it is not necessary to have an installation of the Telerik UI for WinForms suite.
+With the introduction of .NET and the Visual Studio .NET WinForms designer, the Toolbox configuration doesn't rely on the GAC anymore and it is not necessary to have an installation of the Telerik UI for WinForms suite. The design time assemblies in .NET are resolved via the installed in the project NuGet packages.
->important In order to enable the WinForms Designer, please get familiar with the requirements you need to meet: [Design Time]({%slug core-design-time%}).
+>important In order to enable the .NET WinForms Designer, please get familiar with the requirements here: [Design Time]({%slug core-design-time%}).
## Toolbox Version
@@ -26,17 +26,18 @@ The Toolbox version depends on the version of installed NuGet package:
For example, if you have the UI.for.WinForms.AllControls.NetCore and you want to get another version in the Toolbox, it is necessary to:
-1\. Remove the current version of the **UI.for.WinForms.AllControls.NetCore** package:
+1\. Remove the current version of the **UI.for.WinForms.AllControls.Net** package:
2\. Install the desired NuGet version: [Install using NuGet Packages]({%slug winforms/nuget%})
+>caption Install UI.for.WinForms.AllControls.Net90 vQ2 2025 (2025.2.520)
3\. Rebuild the project.
->note The same approach is also valid for the other Telerik UI for WinForms packages, e.g. UI.for.WinForms.AllControls.Net60, UI.for.WinForms.Common, etc.
+>note The same approach is also valid for the other Telerik UI for WinForms packages, e.g. UI.for.WinForms.AllControls.Net80, UI.for.WinForms.Common, etc.
## Troubleshooting Visual Studio Toolbox
diff --git a/core/deploy-application.md b/core/deploy-application.md
index 646da3714..1268b9f76 100644
--- a/core/deploy-application.md
+++ b/core/deploy-application.md
@@ -1,29 +1,29 @@
---
-title: Deploying WinForms .NET Core Application
-page_title: Deploying WinForms .NET Core Application - NET Core
+title: Deploying WinForms .NET Application
+page_title: Deploying WinForms .NET Application
description:
slug: core-getting-started
-tags: deploy, WinForms application, .NET Core
+tags: deploy, WinForms application, .NET
published: True
position: 4
---
-# Deploying WinForms .NET Core Application
+# Deploying WinForms .NET Application
-This article shows how to deploy a WinForms .NET Core Application using Visual Studio.
+This article shows how to deploy a WinForms .NET Application using Visual Studio.
>tip Read more about the deployment approaches, their benefits and differences, in the [3 Ways to Deploy a WinForms or WPF .NET Core Application](https://www.telerik.com/blogs/3-ways-to-deploy-a-winforms-or-wpf-net-core-application) blog post.
-## Create an Application
+## Create .NET Application
>tip This step is described only for testing purposes. If you prefer, you can go directly to the [Deploy the Application](#deploy-the-application) section of this article.
-1\. Create a new WinForms project using the [Telerik Visual Studio Extensions]({%slug winforms-installation-deployment-and-distribution-visual-studio-extensions%}). If the VSX is installed you will see the **Telerik C# WinForms Application (.NET Core)** template in the Visual Studio's project templates list.
+1\. Create a new WinForms project using the [Telerik Visual Studio Extensions]({%slug winforms-installation-deployment-and-distribution-visual-studio-extensions%}). If the VSX is installed you will see the **Telerik C# WinForms Application (.NET)** template in the Visual Studio's project templates list.
2\. Select one of the application templates from the New Project Wizard. For this example, I use the Excel-Inspired template.
-Currently, Telerik WinForms .NET Core project templates support both .NET Core assembly references (2020.3.915.310) and .NET Core package references (2020.3.915.310 NuGet).
+Currently, Telerik WinForms .NET project templates support both .NET assembly references (2020.3.915.310) and .NET package references (2020.3.915.310 NuGet).
@@ -43,7 +43,7 @@ Currently, Telerik WinForms .NET Core project templates support both .NET Core a
## Deploy the Application
->important The approach shown here is available with the official Visual Studio 2019 and later versions. If you use a previous build of VS, check the [Deploy .NET Core apps with Visual Studio](https://docs.microsoft.com/en-us/dotnet/core/deploying/deploy-with-vs?tabs=vs156) MSDN article.
+>important The approach shown here is available with the official Visual Studio 2019 and later versions. If you use a previous build of VS, check the [Deploy .NET apps with Visual Studio](https://docs.microsoft.com/en-us/dotnet/core/deploying/deploy-with-vs?tabs=vs156) MSDN article.
1\. Right click the project in Visual Studio and select the **Publish** option. This will open the **Pick a publish taget** dialog.
diff --git a/core/design-time.md b/core/design-time.md
index 0886ce949..f8066dda0 100644
--- a/core/design-time.md
+++ b/core/design-time.md
@@ -1,104 +1,50 @@
---
title: Design Time
-page_title: NET Core Design Time
-description:
+page_title: .NET Design Time
+description: Telerik UI for WinForms supports the Visual Studio .NET WinForms designer.
slug: core-design-time
-tags: core, designer
+tags: designer, .net, winforms
published: True
-position: 1
+position: 2
---
# Design Time
-Telerik UI for WinForms supports the Visual Studio .NET Core WinForms designer. All of the Telerik designers are migrated and the controls are populated in the toolbox. We have special control designers, action lists, property builders and editors achieving a design time experience similar to the one seen on the full .NET framework.
-
->important In **R2 2022** we added support for:
->
-* RadItem glyphs
-* RadItem action lists
-* RadItem context menus
-* RadItem default event generation
-* Inline editing
-* Menus and drop-downs
-* Form conversion
-* F1 help integration
-* Layout control, Rotator and Carousel implementations
->
-Now, we have a feature parity with the .NET Framework designer. It is highly recommended using Visual Studio 2022.
-
-
->caption Figure 1: RadGridView .NET Core Designer
+Telerik UI for WinForms fully supports the Visual Studio .NET WinForms designer. All Telerik designers have been migrated, and all of our controls are available in the toolbox at design time. Specialized control designers, action lists, property builders, smart tags and editors provide a design-time experience in .NET that matches the capabilities available in .NET Framework, enabling our customers to take advantage of the new enhancements in the latest .NET.
+
+>caption Figure 1: RadGridView .NET Designer
## Requirements
-The design time assemblies in .NET Core are resolved via the installed in the project NuGet packages. In order use the new designers, please make sure that the following requirements are met:
-
-* **Visual Studio 2022 v17.0 and newer** or **Visual Studio 2019 v16.8 and newer**
- - The VS2022 and VS2019 Preview [versions](https://visualstudio.microsoft.com/vs/preview/) are also supported.
-
- >caution Check the compatibility table below with details about matching Telerik and Visual Studio versions.
-
- - Don’t forget to enable the designer in *Tools > Options > Environment > Preview Features*.
-* **Telerik UI for WinForms NuGet installed in the project**: [Install using NuGet Packages]({%slug winforms/nuget%})
- - Telerik UI for Winforms R3 2020 and newer.
-
- >caution Even though you may have an installation of the Telerik UI for WinForms suite with the correct version according to the compatibility table below, it is not enough to load the designer. It requires installing the appropriate Telerik UI for WinForms NuGet package.
-
- 
-
-* **Target .NET Core 3.1/.NET 5+ in your project**: [https://docs.microsoft.com/en-us/dotnet/standard/frameworks#supported-target-frameworks](https://docs.microsoft.com/en-us/dotnet/standard/frameworks#supported-target-frameworks)
-
->important Our designers target a specific version of the WinForms Designer SDK and this SDK is also inserted into Visual Studio. Sometimes there might be breaking changes in the WinForms Designer SDK and as it is part of Visual Studio itself this will break our designers. As things are dynamically changing one needs to pay attention of the Telerik NuGet version and the Visual Studio version. The table below is a mapping between the Telerik and the Visual Studio versions.
->
-
->note The latest **Telerik UI for WinForms** NuGets should be supported in the latest VS2022 and VS2019 releases. Below is a compatiblity table with our previous versions and a matching Visual Studio release. As it is not needed anymore, this table will no longer be updated.
-
-|Telerik NuGet Version|Visual Studio Version|
-|----|----|
-|R2 2022 v2022.2.510|VS2022: v17.1.+; v17.3.0 Preview 1; VS2019: v16.11.+|
-|Hotfix v2022.1.329-hotfix|VS2022: v17.0.+; v17.2.0 Preview 2; VS2019: v16.11.+|
-|Hotfix v2022.1.322-hotfix|VS2022: v17.0.+; v17.2.0 Preview 2; VS2019: v16.11.+|
-|R1 2022 SP1 v2022.1.222|VS2022 v17.0.+; VS2019 v16.11.+|
-|R1 2022 v2022.1.118|VS2022 v17.0.+; VS2019 v16.11.+|
-|Hotfix v2021.3.1213-hotfix|VS2022: v17.0.+; v17.1.0 Preview 1.1; VS2019: v16.11.+; v16.11.7 Preview 1.0|
-|R3 2021 SP2 v2021.3.1123|VS2022: v17.0.+; v17.1.0 Preview 1.1; VS2019: v16.11.+; v16.11.7 Preview 1.0|
-|R3 2021 SP1 v2021.3.1109|VS2022: v17.0.+; v17.1 Preview 1; VS2019: v16.11.+; v16.11 Preview 1|
-|Hotfix v2021.3.1019-hotfix|VS2022 v17.0 Preview 5, 6 & 7|
-|Hotfix v2021.3.927-hotfix|VS2022 v17.0 Preview 4|
-|R3 2021 v2021.3.914|VS2019 v16.11.+; VS2019 v16.11 Preview|
-|Hotfix v2021.2.802-hotfix|VS2019 v16.11.+; VS2019 v16.11 Preview 4; VS2022 v17.0 Preview 2|
-|Hotfix v2021.2.712-hotfix|VS2019 v16.11.+; VS2019 v16.11 Preview 1 & 2; VS2022 v17.0 Preview 2|
-|R2 2021 SP1 v2021.2.615|VS2019 v16.10.+; VS2019 v16.11 Preview 1 & 2; VS2022 v17.0 Preview 1|
-|Hotfix v2021.2.607-hotfix|VS2019 v16.10.+; VS2019 v16.11 Preview 1|
-|R2 2021 v2021.2.511|VS2019 v16.9.+; VS2019 v16.9 Preview 2 to v16.10 Preview 1|
-|Hotfix v2021.1.329-hotfix|VS2019 v16.9.+; VS2019 v16.9 Preview 2 to v16.10 Preview 1|
-|R1 2021 SP3 v2021.1.326|VS2019 v16.9.+; VS2019 v16.9 Preview 2 to v16.10 Preview 1|
-|R1 2021 SP2 v2021.1.223|VS2019 v16.9.+; VS2019 v16.9 Preview 2 to v16.10 Preview 1|
-|R1 2021 SP1 v2021.1.204|VS2019 v16.9.+ Preview 2 or newer|
-|R1 2021 v2021.1.122|VS2019 v16.9 Preview 2 or newer|
-|Hotfix v2020.3.1215-hotfix|VS2019 v16.9 Preview 2|
-|Hotfix v2020.3.1116-hotfix|VS2019 v16.9 Preview 1|
-|R3 2020 SP1 v2020.3.1020|VS2019 v16.8.+; VS2019 v16.8 Preview 4|
-|R3 2020 v2020.3.915|VS2019 v16.8 Preview 3|
-
->note The toolbox is populated from the UI controls added to the referenced NuGet package/s.
->
-
->important As the *AllControls* package contains all UI controls and themes it should not be installed in projects having other packages containing the UI controls (e.g. *UI.for.WinForms.Common* etc.) or the *UI.for.WinForms.Themes* package. Either use the *AllControls* package or the packages of the separate controls and the themes.
+The design time assemblies in .NET are resolved via the installed in the project NuGet packages. This means that toolbox is populated from the Telerik UI controls added to the referenced Telerik NuGet package/s. In order use the designers in .NET, please make sure that the following requirements are met:
+
+* **Visual Studio 2022 v17.0 and newer**
+
+* **Telerik UI for WinForms NuGet package installed in the project**: [Install using NuGet Packages]({%slug winforms/nuget%})
+ * **UI.for.WinForms.AllControls.Net**** package wraps all Telerik assemblies for specific .Net version in one package. For more information see [Available NuGet Packages]({%slug winforms-available-nugets%})
+
+>note For best results, use the latest version of Telerik UI for WinForms Nuget package and latest Visual Studio 2022 version.
+
+>caption Figure 2: TelerikWinFormsApp in .NET using UI.for.WinForms.AllControls.Net90
+
+
+
+>caution Even though you may have an installation of the Telerik UI for WinForms suite, it is not enough to load the designer. It requires installing Telerik UI for WinForms NuGet package.
+
## Tips and Tricks
Note that the design-time assemblies are resolved from the installed NuGet packages by the new Microsoft SDK which is part of Visual Studio. It is recommended to close all the opened designers when you are about to install or update our NuGets. The same is also true when rebuilding the project. Please have in mind that if you have a designer opened and you rebuild the project, this will kill the .NET Core process hosting the design server, ultimately this will lead to restarting the design surface by starting a new server process. If your form has a complex designer this may slow down Visual Studio so you may consider closing the designers before rebuilding the application.
>important The new architecture is described in more details in our [New Telerik UI for WinForms Designers for .NET Core and .NET 5.0](https://www.telerik.com/blogs/new-telerik-ui-for-winforms-designers-dotnet-core-dotnet-5) blog.
->
+
## See Also
* [New Telerik UI for WinForms Designers for .NET Core and .NET 5.0](https://www.telerik.com/blogs/new-telerik-ui-for-winforms-designers-dotnet-core-dotnet-5)
-* [Migrating to .NET Core]({%slug core-migration%})
+* [Migrating to .NET]({%slug core-migration%})
* [Windows Forms Designer for .NET Core Released](https://devblogs.microsoft.com/dotnet/windows-forms-designer-for-net-core-released/)
* [How to Handle NETSDK1141 Error]({%slug netsdk1141-error%})
* [How to Build Custom Telerik Assemblies when Using .NET Core and Enable Design Time Experience]({%slug build-custom-assemblies-for-net-core%})
diff --git a/core/images/core-designer002.png b/core/images/core-designer002.png
index 03cde2a45..1d7274794 100644
Binary files a/core/images/core-designer002.png and b/core/images/core-designer002.png differ
diff --git a/core/images/core-toolbox-version003.png b/core/images/core-toolbox-version003.png
index 13b8dddb3..4dd601b3a 100644
Binary files a/core/images/core-toolbox-version003.png and b/core/images/core-toolbox-version003.png differ
diff --git a/core/overview.md b/core/overview.md
new file mode 100644
index 000000000..f83a1dd7a
--- /dev/null
+++ b/core/overview.md
@@ -0,0 +1,52 @@
+---
+title: Overview
+page_title: .NET Support Overview
+description: Telerik UI for WinForms support .NET 8 and later
+slug: core-overview
+tags: core, overview, .net, winforms
+published: True
+position: 1
+---
+
+# .NET Support Overview
+
+**Telerik UI for WinForms** comes with support for **.NET 8** and later.
+
+Telerik provides sets of assemblies built against each supported .NET version. To start using the Telerik controls in .NET, simply reference the appropriate Telerik NuGet package for your target framework and start building your application. Whether you're starting a new project or migrating from .NET Framework, Telerik controls will help you develop modern .NET apps, ensuring it can leverage the latest .NET features, performance improvements, and security enhancements.
+
+If you are interested in migrating your app to .NET, see the [Migrating to .NET]({%slug core-migration%}) article.
+
+## .NET 8 Requirements
+
+To use the Telerik UI for WinForms assemblies targeting .NET 8, the following prerequisites must be installed.
+
+* The latest [.NET 8 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/8.0).
+
+* [Visual Studio](https://visualstudio.microsoft.com/downloads/) 2022 (v17.2 or newer).
+
+* The latest version of **Telerik UI for WinForms NuGet package** available at [Telerik NuGet server](https://nuget.telerik.com/v3/index.json).
+
+## .NET 9 Requirements
+
+To use the Telerik UI for WinForms assemblies targeting .NET 9, the following prerequisites must be installed.
+
+* The latest [.NET 9 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/9.0).
+
+* [Visual Studio](https://visualstudio.microsoft.com/downloads/) 2022 (v17.2 or newer).
+
+* The latest version of **Telerik UI for WinForms NuGet package** available at [Telerik NuGet server](https://nuget.telerik.com/v3/index.json).
+
+## Design-Time Support and Visual Studio ToolBox
+
+The Telerik controls can be drag/dropped from the Visual Studio Toolbox. To enable this under .NET you will need to reference the Telerik dlls via nuget package. Installing the nuget packages will add the corresponding controls in the toolbox. Drag and drop from the toolbox is available only for the projects that have the Telerik nuget packages installed.
+
+Additionally, the Telerik controls introduce customized design-time support as using smart tags, design-time selection, and also the standard control properties that can be changed through the Visual Studio Designer.
+
+>important For more information about design-time support and Visual Studio ToolBox see [Design Time]({%slug core-design-time%})
+
+## See Also
+
+* [Design Time]({%slug core-design-time%})
+* [New Telerik UI for WinForms Designers for .NET Core and .NET 5.0](https://www.telerik.com/blogs/new-telerik-ui-for-winforms-designers-dotnet-core-dotnet-5)
+* [Migrating to .NET Core]({%slug core-migration%})
+* [Windows Forms Designer for .NET Core Released](https://devblogs.microsoft.com/dotnet/windows-forms-designer-for-net-core-released/)
diff --git a/installation-and-upgrades/upgrade-project.md b/installation-and-upgrades/upgrade-project.md
index 918c82e6a..54a159589 100644
--- a/installation-and-upgrades/upgrade-project.md
+++ b/installation-and-upgrades/upgrade-project.md
@@ -23,14 +23,12 @@ Upgrading by using NuGet packages is the recommended approach as this method ens
If you are using NuGet packages, upgrade as follows:
-1. Open your project in Visual Studio.
-1. Right-click the project in Solution Explorer and select **Manage NuGet Packages** from the menu.
-1. Go to the **Updates** tab.
-1. Find the **Telerik.UI.for.WinForms.AllControls** package.
+1. In Visual Studio, right-click the project in Solution Explorer and select **Manage NuGet Packages** from the menu.
+1. Go to the **Updates** tab and find the relevant **Telerik.UI.for.WinForms.AllControls** package.
1. Click **Update** to install the latest version, or select a specific version from the dropdown.
1. Wait for the update to complete, then rebuild your project.
-> **Tip:** This is the recommended approach if you are using NuGet packages, as all references are updated automatically.
+>note The recommended approach to upgrade your project is by using Telerik NuGet packages, as all references are updated automatically.
## Upgrade via Telerik Visual Studio Extensions
@@ -38,13 +36,12 @@ You can easily upgrade your Telerik UI for WinForms project using the [Visual St
To upgrade using Telerik Visual Studio Extensions:
-1. Open your project in Visual Studio.
-1. Go to the **Extensions > Telerik > Telerik UI for WinForms > Upgrade Project Wizard**.
+1. In Visual Studio, go to the **Extensions > Telerik > Telerik UI for WinForms > Upgrade Project Wizard**.
1. Follow the prompts in the Upgrade Project Wizard to select the desired Telerik UI for WinForms version and complete the upgrade process.
1. The extension will automatically update the references and resources in your project.
1. Rebuild your project to ensure everything is up to date.
-> **Tip** For more information check [Telerik VS Extensions > Upgrade Project]({%slug winforms/installation-deployment-and-distribution/visual-studio-extensions/upgrade-project%})
+> For more information please check [Telerik VS Extensions > Upgrade Project]({%slug winforms/installation-deployment-and-distribution/visual-studio-extensions/upgrade-project%})
## Manual Assembly Upgrade
@@ -55,7 +52,7 @@ If you are using local assemblies or have just installed Telerik UI for WinForms
1. Right-click on References and select *Add Reference...*. Navigate to the folder of your fresh installation and select the required Telerik assemblies.
1. Clean, then rebuild your project to ensure it uses the new version.
-> **Tip** For more information, please check [Updating Assemblies in a Project]({%slug winforms/installation-deployment-and-distribution/updating-assemblies-in-a-project%})
+> For more information, please check [Updating Assemblies in a Project]({%slug winforms/installation-deployment-and-distribution/updating-assemblies-in-a-project%})
## Upgrade using Progress Control Panel
@@ -67,7 +64,7 @@ If you encounter issues while upgrading your Telerik UI for WinForms project, co
- **Manual Assembly Conflicts:** If you manually update assemblies check [Versions Upgrade]({%slug versions-upgrade%})
- **Check Documentation:** Refer to the official [Telerik documentation]({%slug winforms/overview%})
-- **Contact Telerik Support:** If problems persist, contact Telerik support for further assistance.
+- **Contact Telerik Support:** If problems persist, contact [Telerik support](https://www.telerik.com/support/winforms) for further assistance.
## See Also
diff --git a/integration-with-other-telerik-products/document-processing-libraries.md b/integration-with-other-telerik-products/document-processing-libraries.md
index 3cde85782..7521f0b03 100644
--- a/integration-with-other-telerik-products/document-processing-libraries.md
+++ b/integration-with-other-telerik-products/document-processing-libraries.md
@@ -4,7 +4,7 @@ page_title: Document Processing Libraries - Integration with Telerik Products
description: "Get started with Telerik UI for {{ site.framework }} and learn how to work with the PdfProcessing, SpreadStreamProcessing, WordsProcessing, and ZipLibrary libraries as part of the Telerik Document Processing Libraries."
slug: document-processing-libraries-overview
tags: document, processing, pdf, word, spread, stream, zip, doc, cross-platform
-position: 11
+position: 0
---
# Telerik Document Processing Libraries
diff --git a/integration-with-other-telerik-products/images/telerik_reporting_1.png b/integration-with-other-telerik-products/images/telerik_reporting_1.png
new file mode 100644
index 000000000..11a381da8
Binary files /dev/null and b/integration-with-other-telerik-products/images/telerik_reporting_1.png differ
diff --git a/integration-with-other-telerik-products/images/telerik_reporting_2.png b/integration-with-other-telerik-products/images/telerik_reporting_2.png
new file mode 100644
index 000000000..405e4b927
Binary files /dev/null and b/integration-with-other-telerik-products/images/telerik_reporting_2.png differ
diff --git a/integration-with-other-telerik-products/images/telerik_reporting_3.png b/integration-with-other-telerik-products/images/telerik_reporting_3.png
new file mode 100644
index 000000000..f01c5ea6d
Binary files /dev/null and b/integration-with-other-telerik-products/images/telerik_reporting_3.png differ
diff --git a/integration-with-other-telerik-products/images/telerik_reporting_4.png b/integration-with-other-telerik-products/images/telerik_reporting_4.png
new file mode 100644
index 000000000..0cb608d0f
Binary files /dev/null and b/integration-with-other-telerik-products/images/telerik_reporting_4.png differ
diff --git a/integration-with-other-telerik-products/reporting-libraries.md b/integration-with-other-telerik-products/reporting-libraries.md
new file mode 100644
index 000000000..76fabb527
--- /dev/null
+++ b/integration-with-other-telerik-products/reporting-libraries.md
@@ -0,0 +1,91 @@
+---
+title: Telerik Reporting
+page_title: Telerik Reporting - Integration with Telerik Products
+description: "Get started with Telerik ReportViewer and learn how to use it in WinForms application."
+slug: telerik-reporting-overview
+tags: telerik,reporting, winforms, radform
+position: 1
+---
+
+# Telerik Reporting for WinForms
+
+[Telerik Reporting](https://docs.telerik.com/reporting/introduction) is a .NET-based reporting solution that enables developers to design, view, and export interactive, data-driven reports across web, desktop, and cloud platforms. It supports a wide range of data sources and includes a rich set of components for building visually complex reports, such as tables, charts, graphs, and barcodes.
+
+Typical use cases include generating invoices, financial summaries, dashboards, and analytical reports. With built-in export options to formats like PDF, Excel, and Word, Telerik Reporting streamlines business reporting and enhances data presentation in enterprise applications.
+
+The platform provides UI components called Report Viewers, which allow you to display and interact with reports directly within your application. These viewers are available for various technologies, including Angular, HTML5/JavaScript, WPF, ASP.NET, and WinForms.
+
+## Telerik ReportViewer for WinForms
+
+In this article, we’ll demonstrate how to add a Report Viewer to a WinForms application.
+To get started, you first need to install Telerik Reporting on your machine. The Installation Approaches for [Telerik Reporting](https://docs.telerik.com/reporting/getting-started/installation/installation-approaches) article outlines several ways to install the product.
+
+In this scenario, we'll use the Telerik Reporting MSI installer to install the necessary libraries. You can download the MSI from your [Telerik Account](https://www.telerik.com/account/downloads/product-download?product=REPORTING).
+
+
+
+Once the installation is successful, you can add the Telerik ReportViewer to your WinForms project Form using one of the approaches below, depending on your requirements.
+
+### Add ReportViewer Form
+
+The item template is available in the __Add New Item__ dialog box under the Windows Form category.
+
+
+
+* Build the project and check that the project is using a compatible .NET version.
+* Open the Add New Report Viewer dialog to choose a report definition for the report viewer.
+* If missing add the required Telerik Reporting references:
+
+ * Telerik.Reporting
+ * Telerik.ReportViewer.WinForms
+
+* Add a Form with Windows Form Report Viewer.
+* Setup the viewer's [connection](https://docs.telerik.com/reporting/embedding-reports/display-reports-in-applications/how-to-construct-a-string-to-connect-to-report-engine) depending on selected __engine type__.
+* Show a summary log that list all of the made changes.
+
+If the selected engine is of remote type (__REST Service__ or __Report Server__), the item template will:
+
+* Add a reference to *Telerik.Reporting.Services.HttpClient* to the current project.
+* Add a reference to *System.Net.Http* and *System.Net.Http.Formatting* via NuGet package to the current project.
+
+If the selected engine is __REST Service__ additionally it will do the following:
+
+* Create a new web project that will host the REST service.
+* Register the provided REST service URL into IIS Express virtual directories list.
+* Register all the needed NuGet packages for the REST service.
+
+ >In some cases the solution must be rebuilt in order to restore the NuGet packages and start the REST service project correctly.
+
+If the application needs to be declared as DPI-aware, an additional element must be added to the application manifest file, as explained in [Declaring the application as DPI-aware](https://docs.telerik.com/reporting/embedding-reports/display-reports-in-applications/windows-forms-application/overview#declaring-the-application-as-dpi-aware).
+
+### Add ReportViewer to Windows Form Design Time
+
+You can add the Telerik ReportViewer to the Windows Forms by drag-droping it from the Visual Studio Toolbox.
+
+
+
+* Add a reference to the class library that contains your reports in the WinForms application.
+* Set the ReportSource property of the ReportViewer. For more information, see [How to Set ReportSource for Report Viewers](https://docs.telerik.com/reporting/embedding-reports/display-reports-in-applications/how-to-set-reportsource-for-report-viewers).
+* To run the report, call ReportViewer.RefreshReport() in your application code.
+
+````C#
+
+private void Form1_Load(object sender, EventArgs e)
+{
+ var typeReportSource = new Telerik.Reporting.TypeReportSource();
+ typeReportSource.TypeName = "Telerik.Reporting.Examples.CSharp.ListBoundReport, CSharp.ReportLibrary";
+ this.reportViewer1.ReportSource = typeReportSource;
+ reportViewer1.RefreshReport();
+}
+
+````
+
+
+
+## See Also
+
+* [Getting Started with Telerik Reporting Libraries](https://docs.telerik.com/reporting/getting-started/about-telerik-reporting)
+
+* [Installation Approaches for Telerik Reporting](https://docs.telerik.com/reporting/getting-started/installation/installation-approaches)
+
+* [Telerik Reporting Licensing](https://docs.telerik.com/reporting/licensing/setting-up-your-telerik-reporting-license-key)
diff --git a/telerik-presentation-framework/ui-automation.md b/telerik-presentation-framework/ui-automation.md
index f0b51a77d..26c378566 100644
--- a/telerik-presentation-framework/ui-automation.md
+++ b/telerik-presentation-framework/ui-automation.md
@@ -28,9 +28,24 @@ Here is a list of the controls which support __UI Automation__.
* [RadRadioButton]({%slug radiobutton-ui-automation%})
* [RadCheckBox]({%slug checkbox-ui-automation%})
+## Enable/Disable UI Automation Globally
+
+As of Q3 2025 UI Automation can be controlled globally for all Telerik UI for WinForms controls through the static **RadControl.EnableUIAutomationDefaultValue** property. This allows you to enable or disable UI Automation support for RadControls across your entire application.
+
+>note UI Automation is enabled by default. If you need to disable it globally for all RadControls see [Disable UI Automation](#disable-ui-automation)
+
+### Disable UI Automation
+
+To disable UI Automation globally (if accessibility features are not required in your application) you can set **EnableUIAutomationDefaultValue** to *false*. This setting should be configured early in your application lifecycle, preferably before creating any Telerik control.
+
+```csharp
+RadControl.EnableUIAutomationDefaultValue = false;
+
+```
+
## UI Accessibility
-Each control inside Telerik UI for WinForms suite is tested with the [Accessibility Insights for Windows](https://accessibilityinsights.io/docs/en/windows/overview/) tool. This application executes tests, which check whether the controls have the right UI Automation properties. We've tested all of the controls from the our suite to ensure that there aren't any failed tests.
+Each control in the Telerik UI for WinForms suite is tested with the [Accessibility Insights for Windows](https://accessibilityinsights.io/docs/en/windows/overview/) tool. This application executes tests which check whether the controls have the right UI Automation properties. We've tested all of the controls from our suite to ensure that there aren't any failed tests.
diff --git a/urlrewriter.config b/urlrewriter.config
index decc3122b..3aa8686ed 100644
--- a/urlrewriter.config
+++ b/urlrewriter.config
@@ -432,4 +432,9 @@
+
+
+
+
+
diff --git a/visual-studio-integration/visual-studio-extensions/configure-project.md b/visual-studio-integration/visual-studio-extensions/configure-project.md
index 8d667b0e5..a94fc64f5 100644
--- a/visual-studio-integration/visual-studio-extensions/configure-project.md
+++ b/visual-studio-integration/visual-studio-extensions/configure-project.md
@@ -14,7 +14,7 @@ __Configure Telerik WinForms Application__
You can access the Project Configuration Wizard through the Telerik menu when you need to configure your Telerik WinForms application:
-
+
The wizard could be also reached through the context menu counterparts accessed by right clicking on the project you want to convert.
diff --git a/visual-studio-integration/visual-studio-extensions/create-project.md b/visual-studio-integration/visual-studio-extensions/create-project.md
index 9eb0d7727..2237385c7 100644
--- a/visual-studio-integration/visual-studio-extensions/create-project.md
+++ b/visual-studio-integration/visual-studio-extensions/create-project.md
@@ -47,11 +47,12 @@ When you click the Finish button:
As of **R3 2023** a new step is available in the wizard, called **Toolbox Configuration**, which allows you to specify what version of UI for WinForms suite to be used for the toolbox:
-
+
If the selected version from the drop down in the previous step matches the toolbox version, the step is expected to look like this:
-
+
+
# See Also
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project000.png b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project000.png
new file mode 100644
index 000000000..836bdefbb
Binary files /dev/null and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project000.png differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project001.png b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project001.png
index 7878aa3b2..b2af87d0c 100644
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project001.png and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project001.png differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project002.png b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project002.png
index 73093cdd6..cf4384367 100644
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project002.png and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project002.png differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project003.PNG b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project003.PNG
index c01061d7d..07e714bdc 100644
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project003.PNG and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-configure-project003.PNG differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-create-project002.PNG b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-create-project002.PNG
index 7068e4907..0c7bd92d6 100644
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-create-project002.PNG and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-create-project002.PNG differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-create-project003.png b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-create-project003.png
index 3627e3ca3..956a7db13 100644
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-create-project003.png and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-create-project003.png differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-create-project005.png b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-create-project005.png
index e088052d5..abcddd8e8 100644
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-create-project005.png and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-create-project005.png differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-options-dialog001.png b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-options-dialog001.png
index 9743b3427..96e5764eb 100644
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-options-dialog001.png and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-options-dialog001.png differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview001.png b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview001.png
index a31f38cc6..9fd564342 100644
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview001.png and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview001.png differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview002.png b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview002.png
index 0ecae1acb..7c54e5749 100644
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview002.png and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview002.png differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview003.png b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview003.png
index 62a66b2e1..09227e76b 100644
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview003.png and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview003.png differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview004.png b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview004.png
index 1dbce271e..30a186559 100644
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview004.png and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-overview004.png differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-toolbox-configurator001.png b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-toolbox-configurator001.png
index 96cf38222..6a7d75a4f 100644
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-toolbox-configurator001.png and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-toolbox-configurator001.png differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-toolbox-configurator002.png b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-toolbox-configurator002.png
index bf345f8cf..1e796d095 100644
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-toolbox-configurator002.png and b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-toolbox-configurator002.png differ
diff --git a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-upgrade-project000.png b/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-upgrade-project000.png
deleted file mode 100644
index a48bdbd6f..000000000
Binary files a/visual-studio-integration/visual-studio-extensions/images/installation-deployment-and-distribution-vsx-upgrade-project000.png and /dev/null differ
diff --git a/visual-studio-integration/visual-studio-extensions/overview.md b/visual-studio-integration/visual-studio-extensions/overview.md
index 2a40f48e1..cd7fdfbc9 100644
--- a/visual-studio-integration/visual-studio-extensions/overview.md
+++ b/visual-studio-integration/visual-studio-extensions/overview.md
@@ -9,29 +9,35 @@ position: 0
previous_url: installation-deployment-and-distribution-vsx-overview
---
-# Visual Studio Extensions
+# Visual Studio Extensions Overview
-__Visual Studio Extensions__ for __Telerik UI for WinForms__ aim to help developers when creating WinForms Application with __Telerik UI for WinForms__.
+[Visual Studio Extensions for Telerik UI for WinForms](https://marketplace.visualstudio.com/items?itemName=TelerikInc.TelerikWinFormsVSExtensions) are designed to streamline and enhance the development experience when creating desktop applications with **Telerik UI for WinForms**. These extensions provide comprehensive tooling support that simplifies common development tasks and accelerates project delivery.
-The extensions handle the following major points in the development with __Telerik UI for WinForms__:
+The extensions provide robust support across the entire development lifecycle with **Telerik UI for WinForms**:
-* __Project creation, conversion and configuration__ – reference management.
+* **Project creation, conversion and configuration** – Streamlined reference management and project setup.
-* __Project Upgrade__ - upgrading __Telerik UI for WinForms__ to a new version.
+* **License Key Management** – Automatically downloads the license key file from your account to your home directory (`%appdata%\Telerik`).
-* __Common scenario page creation__ - aid creating pages with basic scenarios in the usage of __Telerik UI for WinForms__.
+* **Project Upgrade** – Seamless upgrading of **Telerik UI for WinForms** to newer versions with dependency management.
-* __Toolbox configuration__ – select what version of Telerik UI to be populated in the Toolbox.
+* **Common scenario page creation** – Wizards and templates for creating frequently-used **Telerik UI for WinForms** scenarios.
-__Visual Studio Extensions__ for __Telerik UI for WinForms__ are distributed with the __Telerik UI for WinForms__ installer. They can be downloaded and installed as separate product from the [Visual Studio Gallery](https://visualstudiogallery.msdn.microsoft.com/) for Visual Studio 2019 and later. The extensions support Visual Studio 2019 and 2022, handling .NET 4.0+ applications.
+* **Toolbox configuration** – Easy selection and configuration of Telerik UI versions to populate in the Visual Studio Toolbox.
->important In 2024 Q1 (version 2024.1.130) the __Visual Studio Extensions__ for Visual Studio 2015 and 2017 is removed and is no longer distributed with the __Telerik UI for WinForms__ installer. The extension for Visual Studio 2015 and 2017 is still available as a separate integration package in the marketplace and can be downloaded from [here](https://marketplace.visualstudio.com/items?itemName=TelerikInc.ProgressWinFormsVSExtensions).
+### Installation and Compatibility
-The __Visual Studio Extensions__ can be accessed through the __Telerik | Telerik UI for WinForms__ menu which has different menu items depending on the selected project in Visual Studio. The extensions can be accessed through the context menu of a WinForms Application as well.
+**Visual Studio Extensions for Telerik UI for WinForms** are distributed with the **Telerik UI for WinForms** installer and can also be downloaded separately from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=TelerikInc.TelerikWinFormsVSExtensions) for Visual Studio 2019 and later versions.
-For Visual Studio 2022 **Visual Studio Extensions** can be accessed through the **Extensions | Telerik | Telerik UI for WinForms menu**.
+>important **Visual Studio Extensions for Telerik UI for WinForms** for Visual Studio 2015 and 2017 were discontinued in 2024 Q1 (version 2024.1.130) and are no longer distributed with the **Telerik UI for WinForms** installer. However, the extensions for Visual Studio 2015 and 2017 remain available as a separate package in the marketplace and can be downloaded [here](https://marketplace.visualstudio.com/items?itemName=TelerikInc.ProgressWinFormsVSExtensions).
-#### Figure 1: __Access Telerik UI for WinForms menu__
+### Accessing the Extensions
+
+The Visual Studio Extensions can be accessed through the **Telerik | Telerik UI for WinForms** menu which has different menu items depending on the selected project in Visual Studio. The extensions are also accessible through the context menu when right-clicking on a WinForms application project in Solution Explorer. For Visual Studio 2022, access the extensions through **Extensions | Telerik | Telerik UI for WinForms**.
+
+Telerik menu adapts its available options based on your current project context:
+
+#### Figure 1: **Telerik UI for WinForms menu (no project selected)**
@@ -44,10 +50,13 @@ For Visual Studio 2022 **Visual Studio Extensions** can be accessed through the
-After installed, the extensions add several project templates to the New Project dialog of Visual Studio:
+### Project Templates
+
+When the extensions are installed, they add several specialized project templates to Visual Studio's New Project dialog, providing quick-start options for different types of Telerik WinForms applications:
#### Figure 4: __Telerik new project templates__
->tip These are available in the language specific nodes of the dialog as well. New Project dialog contains __Telerik WinForms Application__ under both CSharp\Windows and Visual Basic\ Windows nodes.
+
+
diff --git a/visual-studio-integration/visual-studio-extensions/toolbox-configurator.md b/visual-studio-integration/visual-studio-extensions/toolbox-configurator.md
index 461d772c1..f81d2eee8 100644
--- a/visual-studio-integration/visual-studio-extensions/toolbox-configurator.md
+++ b/visual-studio-integration/visual-studio-extensions/toolbox-configurator.md
@@ -23,8 +23,6 @@ The user can make his selection using the dropdown menu which lists all versions
-The __Toolbox Configurator__ is supported in Visual Studio 2008, 2010, 2012, 2013, 2015, 2017 and 2019.
-
>tip The Toolbox Configurator will overwrite the toolbox registration performed during installation. Additionally, the Toolbox Configurator registers the selected version of Telerik UI for WinForms in AssemblyFoldersEx. This makes them visible in the Add Reference dialog and Choose Toolbox Items dialog (accessible from the toolbox context menu).