telerik-wpf-upgrade-plugin

Plugin telerik-wpf-upgrade-plugin from marketplace telerik-ai-plugins in telerik/ai-plugins. Commands read from the repo's manifest — yesterday.

Skills (21)

• telerik-wpf-for-dotnet-framework-upgrade

  Telerik UI for WPF rules for a .NET Framework version upgrade (net4xx to net481) — verify the referenced Telerik version still supports net481, offer (never force) the assembly-to-NuGet migration, preserve the Xaml/NoXaml flavor, and keep licensing consistent with whichever reference mechanism the c

• telerik-wpf-for-dotnet-version-upgrade

  Telerik UI for WPF rules for a .NET version upgrade to newer modern .NET — covers both modern-.NET-to-newer-modern-.NET (B1) and .NET Framework-to-modern-.NET (B2) sources. Determines which situation applies, verifies the Telerik version against the new target TFM, and mandatorily migrates Telerik d

• telerik-wpf-assembly-mapping

  Map direct Telerik UI for WPF assembly references to the NuGet packages that own them, for the project's assembly flavor (Xaml or NoXaml) and target framework, using dependency-aware minimal package selection. Reports any assembly with no known mapping instead of guessing a package name. discovery:

• telerik-wpf-breaking-changes

  Detect and resolve Telerik UI for WPF breaking changes when upgrading between versions. Calls the telerik-upgrade-assistant MCP tool to analyze projects and guides the agent through iterative fix-build-validate cycles. discovery: lazy importance: high traits: .NET|CSharp|VisualBasic|DotNetCore|WPF

• telerik-wpf-component-guidance

  Get Telerik UI for WPF component API guidance by calling the telerik-wpf-assistant MCP tool. Use when fixing breaking changes, implementing new controls, or answering questions about Telerik component usage and configuration. discovery: lazy importance: medium traits: .NET|CSharp|VisualBasic|DotNetC

• telerik-wpf-dependency-management

  Manage Telerik UI for WPF NuGet packages and assembly references. Resolves the package set to install or migrate to from the assembly reference map by default; recommends the flavor-matching AllControls meta-package only for a broad or unreliable reference set, or explicit customer preference. Also

• telerik-wpf-license-detection

  Determine how, and whether, a Telerik UI for WPF project is currently licensed. Read-only — reports the active mechanism, every license artifact found and its precedence, the entry-point/host shape, and whether the referenced Telerik version even requires a license. Never mutates anything and never

• telerik-wpf-license-diagnostics

  Map an observed Telerik UI for WPF licensing symptom or a documented TKL error/warning code to its cause and the lazy skill that fixes it. Read-only — decides the fix, does not apply it. discovery: lazy importance: high traits: .NET|CSharp|VisualBasic|DotNetCore|WPF

• telerik-wpf-license-key-setup

  Guide a customer through obtaining and correctly placing a Telerik UI for WPF license key for the recommended NuGet-based activation path, or the script-key path when NuGet-based activation genuinely is not applicable. Never handles, fabricates, or stores key content. Idempotent. discovery: lazy imp

• telerik-wpf-license-nuget-migration

  Convert a Telerik UI for WPF project from the script-key licensing model (compiled EvidenceAttribute) to the NuGet-based model (Telerik.Licensing package + telerik-license.txt), and clean up what the script-key model left behind. This only changes the licensing mechanism — it does not migrate the Te

• telerik-wpf-license-plugin-hosts

  Set up or fix Telerik UI for WPF license activation for add-in/plugin hosts (e.g. Office VSTO add-ins, Revit, AutoCAD, ArcGIS, Adobe plugins) — the entry-point shape with no standard application context, where the license cannot be evaluated automatically and needs an explicit `TelerikLicensing.Regi

• telerik-wpf-license-verification

  Confirm a Telerik UI for WPF licensing setup actually activates — build the project(s) and check for TKL* warnings/errors, and confirm the resulting mechanism matches what was planned. Idempotent. discovery: lazy importance: high traits: .NET|CSharp|VisualBasic|DotNetCore|WPF

• telerik-wpf-migration-verification

  Restore and build a WPF project after a Telerik reference migration, using the correct build method for Classic-style .NET Framework projects, run the NoXaml theming checks, and report exactly what changed. Idempotent. discovery: lazy importance: high traits: .NET|CSharp|VisualBasic|DotNetCore|WPF

• telerik-wpf-nuget-feed-setup

  Determine which NuGet feed can resolve Telerik UI for WPF packages for a given version, inspect existing NuGet configuration, validate that the feed actually resolves Telerik packages, and guide the user through Telerik NuGet server setup when required. Never handles or stores credentials. discovery

• telerik-wpf-reference-detection

  Detect a WPF project's current Telerik UI for WPF version, reference style (direct assembly reference, NuGet PackageReference, or packages.config), and assembly flavor (Xaml or NoXaml). Read-only — produces the facts that other Telerik skills and scenarios plan from. discovery: lazy importance: high

• telerik-wpf-reference-migration

  Edit a WPF project file to replace direct Telerik UI for WPF assembly references with the resolved NuGet PackageReference set for the project's assembly flavor (Xaml or NoXaml). Prefers PackageReference over packages.config, removes superseded assembly references, and keeps the Telerik UI version co

• telerik-wpf-reference-retargeting

  Update direct Telerik UI for WPF assembly references to a new Telerik version without changing the delivery method or the assembly flavor — validates a customer-supplied DLL location, repoints every `<Reference>`/`<HintPath>` entry to it, and leaves everything else (delivery method, flavor, licensin

• telerik-wpf-xaml-flavor

  Detect whether a WPF project uses the Telerik UI for WPF Xaml or NoXaml assemblies (direct references or NuGet packages), flag mixed or inconsistent usage, and check the theming setup that each flavor needs. Read-only — owns the rule that a migration always preserves the flavor. discovery: lazy impo

• telerik-wpf-assembly-to-nuget

  Migrate a WPF project's direct Telerik UI for WPF assembly references to the equivalent NuGet packages of the same Xaml/NoXaml flavor, keeping the Telerik version and .NET target unchanged. Detects the current version, reference style, and flavor, sets up the right NuGet feed, maps assemblies to pac

• telerik-wpf-licensing

  Set up, fix, or migrate Telerik UI for WPF license activation, independent of any version change. Detects the current mechanism (NuGet-based or script-key), diagnoses TKL* errors and watermarks, sets up the recommended activation path, and migrates to the NuGet-based model when feasible. Not for ver

• telerik-wpf-version-upgrade

  Upgrade the Telerik UI for WPF version used by a WPF application — detect and fix breaking changes, and set up license activation when crossing the Q1 2025 boundary. Works whether Telerik is referenced via NuGet or direct assembly references, and always preserves the Xaml/NoXaml flavor; moving to Nu

MCP servers (1)

• Telerik.WPF.MCP

  runs: dnx Telerik.WPF.MCP --yes --ignore-failed-sources

Similar plugins