Telerik UI for WPF MCP Upgrade Assistant
The telerik_upgrade_assistant tool is part of the Telerik WPF MCP Server (version 1.8.0 and later). It helps you analyze your existing WPF projects for breaking changes when upgrading between Telerik UI for WPF versions.
The tool integrates with the Telerik CLI (telerik migrate analyze command) and returns structured findings to the AI model, which can then interpret and apply the necessary code fixes automatically.
Prerequisites
To use the upgrade tool, you need:
- The Telerik WPF MCP Server version 1.8.0 or later installed and configured.
- The Telerik CLI global .NET tool. If not already installed, the upgrade tool will detect this and prompt you to install it automatically.
- A WPF project (
.csproj) that references Telerik UI for WPF assemblies.
If the Telerik CLI is not installed on your machine, the tool will ask for your permission to install it via
dotnet tool install --global Telerik.CLI. It will also check for available updates and apply them when needed.
Using the Upgrade Tool
To analyze your WPF project for Telerik-related upgrade issues, follow these steps:
-
Open your WPF solution in Visual Studio.
-
Open the Copilot Chat window.
-
Make sure the
telerik-wpf-assistantMCP tool is enabled in the Copilot Chat tool selection dropdown. For setup instructions, see Getting Started with Telerik WPF MCP Server.
-
Type a prompt such as:
@telerik Analyze this WPF project for Telerik-related upgrade issues.You can also specify version details:
@telerik Analyze my WPF project for breaking changes when upgrading from version 2024.4.1111 to 2025.2.513.
-
Grant permissions when prompted (per session, workspace, or always). The AI model automatically invokes the
telerik_upgrade_assistanttool, which runs the analysis and returns a structured report of any breaking changes found in your project. -
Review the results. The AI model presents the findings grouped by file, with line numbers, affected API members, and recommended actions. You can then ask the AI to apply the suggested fixes directly to your code.
The
telerik_upgrade_assistanttool uses the Telerik CLItelerik migrate analyzecommand under the hood. You can also run this command directly from the terminal. For all available command options, see the Telerik CLI Migrate Analyzer article.
Understanding the Results
The upgrade tool returns a structured report that includes:
- File path—The source file where a breaking change was detected.
- Line number—The exact line in the file.
- Member name—The affected API member (property, method, event, or class).
- Change kind—The type of breaking change (removed, renamed, signature changed, etc.).
- Old signature—The previous API signature (when available).
- New signature—The replacement API signature (when available).
- Next steps—Recommended actions for resolving each finding.