New to Telerik UI for WinForms? Start a free 30-day trial

Telerik UI for WinForms Converter

The Telerik UI for WinForms Converter is an automated migration tool that converts existing Microsoft WinForms applications to use Telerik UI for WinForms controls. The converter is integrated into the Telerik WinForms MCP Server and works with AI-powered IDEs such as Visual Studio and Visual Studio Code to guide you through the entire migration process.

The converter uses Microsoft Roslyn — the .NET compiler platform — to parse, analyze, and transform your C# and VB.NET source code. Unlike simple find-and-replace or regex approaches, Roslyn provides a full understanding of the code structure through Abstract Syntax Trees (ASTs), enabling accurate, context-aware transformations.

The WinForms Converter replaces the legacy Visual Studio Extension-based converter, which was limited to Visual Studio 2019. The new converter works in any MCP-compatible IDE and supports modern .NET versions.

Prerequisites

To use the Telerik UI for WinForms Converter, you need:

• An active Telerik user account.
• A Telerik Subscription license or a Telerik UI for WinForms trial.
• An MCP-compatible IDE — Visual Studio with Copilot or VS Code with GitHub Copilot Agent mode.
• A configured Telerik WinForms MCP Server with the server name telerik-winforms-assistant.
• A connection established to the Telerik NuGet server.
• A WinForms application that uses Microsoft WinForms controls. It can be either .NET Framework or .NET project.
• Preferably, have the Telerik.UI.for.WinForms.AllControls NuGet package installed.

A Subscription license and a configured Telerik WinForms MCP Server are required.

How It Works

The Telerik UI for WinForms Converter exposes a set of MCP tools that the AI agent calls in sequence. The agent acts as the orchestrator — it calls the tools, interprets results, builds the project, fixes errors, and guides you through the process step by step.

The typical migration workflow is:

1. Get the migration plan — The AI agent calls telerik_get_migration_plan to understand the recommended workflow, rules, and anti-patterns.
2. Analyze the project — The AI agent calls telerik_analyze_project to inspect the .csproj file and determine target framework, project style, and existing Telerik references.
3. Add Telerik NuGet packages — The AI agent calls telerik_add_package_reference to add the Telerik.UI.for.WinForms.AllControls NuGet package.
4. Convert files one at a time — The AI agent calls telerik_convert_file for each form, converting the Designer.cs file first, then the corresponding .cs file. After each pair, the agent builds and fixes errors before moving to the next form.
5. Apply a theme — The AI agent calls telerik_get_theme_setup to configure a Telerik theme (for example, Fluent).
6. Final build — The agent runs a final build to verify the completed migration.

The converter follows a Divide and Conquer strategy. Even when you ask to convert an entire project, the AI agent converts one form or user control at a time. This keeps the error surface small, prevents error accumulation, and ensures each form works before moving on.

Supported Type Mappings

Standard Microsoft WinForms control types are mapped to their Telerik equivalents:

The full mapping database is embedded in the converter and covers a comprehensive set of Microsoft WinForms controls and their properties, events, and enum values.

Supported Languages

The converter supports both C# and VB.NET source files:

The language is automatically detected from the file extension. Both languages share the same mapping configuration.

License Requirements

Access to the Telerik UI for WinForms Converter depends on your Telerik license type:

* Perpetual license holders do not have access to the WinForms Converter. A Subscription license is required for unlimited conversions.

Security and Safety

The converter implements several safety measures:

• Workspace boundary enforcement
• Backup before overwrite
• Path canonicalization
• Secure XML parsing

See Also

• Getting Started with the WinForms Converter
• Converter MCP Tools, Prompts, and Engine Reference
• Configure the Telerik WinForms MCP Server