DevExpress Migration Guide via MCP¶
This guide explains how to use the MCP server to access DevExpress migration documentation and implement the 20-prompt migration plan.
Prerequisites
Before using this guide, make sure you've completed the MCP User Guide setup steps.
Automatic Progress Tracking
The MCP server will automatically create MIGRATION_PROGRESS.md in your workspace when you start the migration. The AI assistant will update it as you complete prompts - no manual setup required!
Overview¶
The MCP server provides:
- Tool:
get_migration_prompt- Get detailed implementation guides - Resources: Access to all migration documentation
- Structure: 20 prompts organized in 5 phases
Quick Start¶
1. Understanding the Migration Structure¶
The migration is organized into 5 phases with 20 prompts:
Phase 1: Infrastructure (Prompts 1-4)
- Feature flag system
- DevExpress project setup
- WCF contract updates
- Template conversion workflow
Phase 2: Core Rendering (Prompts 5-10)
- Report.cs refactoring
- REPX template loading
- Basic rendering
- Subreport processing
- Dynamic layouts
- PDF generation
Phase 3: Advanced Features (Prompts 11-15)
- Preview UI
- Print direct
- Complex reports
- DataList reports
- Master reports
Phase 4: Designer Integration (Prompts 16-18)
- Designer launcher
- UI integration
- Template management
Phase 5: Testing & Cleanup (Prompts 19-20)
- Comprehensive testing
- RDLC removal (optional)
Using the MCP Server¶
Method 1: Get Specific Prompts¶
Ask the AI assistant to retrieve a specific prompt:
User: "Show me prompt 1 for the DevExpress migration"
AI: *Calls get_migration_prompt with promptNumber: 1*
AI: *Displays detailed implementation guide*
What you'll get:
- Overview and prerequisites
- Files to modify
- Pre-implementation analysis steps
- Detailed implementation steps
- Feature flag integration points
- 5-level validation procedures
- Common issues and solutions
- Completion checklist
Method 2: Read Migration Documentation¶
Ask the AI to read specific documentation:
User: "What's the overall migration strategy?"
AI: *Reads rdlc://migration/overview*
AI: *Summarizes feature-flagged approach, phases, risks*
Method 3: Browse Prompt Files¶
Access grouped prompts by phase:
User: "Show me all the infrastructure prompts"
AI: *Reads rdlc://migration/prompts-01-07*
AI: *Displays prompts 1-7 covering infrastructure and core rendering*
Example Workflow¶
Starting the Migration¶
User: "I want to start the DevExpress migration"
AI: *Reads rdlc://migration/overview and rdlc://migration/playbook*
"The migration uses a feature-flagged approach with 20 prompts across 5 phases.
You should start with Prompt 1: Feature Flag Infrastructure.
This creates the foundation that allows safe rollback at any time.
Should I show you Prompt 1?"
User: "Yes"
AI: *Calls get_migration_prompt with promptNumber: 1*
*Displays full implementation guide*
"Prompt 1 will:
1. Create ReportEngine.cs enum
2. Add Engine property to ReportSettings.cs
3. Set default to RDLC for safety
Before implementing, I should analyze your current code.
Let me read ReportSettings.cs..."
Implementing a Prompt¶
User: "Implement prompt 1"
AI: *Calls get_migration_prompt with promptNumber: 1*
*Reads current ReportSettings.cs*
*Analyzes structure*
"I'll implement Prompt 1. Here's what I found:
- ReportSettings is serializable
- It has 5 existing properties
- Used in WCF communication
I'll now:
1. Create ReportEngine.cs
2. Add Engine property with RDLC default
3. Build and validate
Creating files..."
*Implements changes*
*Runs build*
"✅ Implementation complete!
Validation checklist:
- [x] Compilation: Success
- [ ] Smoke test: Please run a simple report with RDLC
- [ ] Feature test: N/A (no DevExpress code yet)
- [ ] Integration: N/A
- [ ] Regression: Please test 2-3 different reports
After validation, we can proceed to Prompt 2."
Checking Progress¶
User: "What's next in the migration?"
AI: *Reads rdlc://migration/progress*
"Based on the progress tracker, you should:
1. Complete validation for Prompt 1
2. Update MIGRATION_PROGRESS.md
3. Proceed to Prompt 2: DevExpress Project Setup
Would you like me to show Prompt 2?"
Getting Help with Issues¶
User: "I'm having issues with subreport processing"
AI: *Reads rdlc://migration/safety-checks*
*Calls get_migration_prompt with promptNumber: 8*
"Subreport processing is covered in Prompt 8.
Let me check the 'Common Issues' section...
Common issues:
1. Subreport not found - Check file paths
2. Data binding fails - Verify DataSource names
3. Nested subreports - Ensure recursive processing
Which issue are you experiencing?"
Best Practices¶
1. Follow Sequential Order¶
Always implement prompts in order (1 → 2 → 3 → ... → 20). Each prompt builds on previous ones.
2. Read Before Implementing¶
Ask the AI to show you the prompt first, understand it, then implement.
3. Validate After Each Prompt¶
Run all 5 validation levels:
- Compilation check
- Smoke test (RDLC path)
- Feature test (DevExpress path)
- Integration test
- Regression test
4. Update Progress Tracking¶
Keep MIGRATION_PROGRESS.md updated with:
- Completed prompts
- Validation results
- Issues encountered
5. Use Safety Checks¶
Reference rdlc://migration/safety-checks for:
- Validation procedures
- Rollback steps
- Emergency procedures
- GxP compliance checks
6. Default to RDLC¶
Critical Rule: Keep the default engine as RDLC until Prompt 19 (comprehensive testing) is 100% complete.
Command Reference¶
Get a Specific Prompt¶
"Show me prompt [number]"
"Get prompt [number] for DevExpress migration"
"What does prompt [number] cover?"
Read Documentation¶
"Show me the migration overview"
"What's the migration strategy?"
"How do I validate changes?"
"Show me the safety checks"
Implementation Help¶
"Implement prompt [number]"
"Help me with [feature] migration"
"What files do I need to modify for prompt [number]?"
Progress Tracking¶
See Also¶
- MCP User Guide - Setup and configuration
- RDLC to DevExpress Conversion Guide - Convert individual RDLC files
- Conversion Flow - Understanding the process
- Mapping Rules - Control and expression mappings
- Troubleshooting - Common issues
Last Updated: December 18, 2025