RDLC to DevExpress Conversion Guide¶

Converting Individual RDLC Files¶

This guide shows you how to convert RDLC reports to DevExpress REPX format using the MCP server in Cursor.

Prerequisites

Before using this guide, make sure you've completed the MCP User Guide setup steps.

Usage¶

Location: Your Project Workspace

All usage happens in Your Project Workspace where your RDLC files are located.

Converting a Report¶

Open an RDLC file in Cursor (in your project workspace):
```
File → Open → Select your .rdlc file
```
Ask Cursor AI to convert it:

Basic conversion (output to workspace root):

"Convert this RDLC report to DevExpress format"

Specify output directory:

"Convert this RDLC report to DevExpress and save to /path/to/output"

Wait for conversion
A ZIP file is created and automatically extracted:
Default location: Workspace root (if no path specified)
Custom location: Your specified output directory
Cursor AI will extract it to a YourReport-converted/ folder
This keeps all converted files separate from your originals
Contents include:
- YourReport.repx - Main converted report
- YourReport-conversion-guide.md - Manual review instructions
- YourReport-conversion-report.json - Detailed statistics
- subreports/ folder - All converted subreports

What to Expect¶

During Conversion¶

When you ask Cursor AI to convert a report, the AI will:

Identify the .rdlc file you're working with
Call the MCP server tool with the file's absolute path
The MCP server reads the file and sends it to the conversion service
Wait for conversion to complete
Display a summary of the conversion
Create all converted files in your workspace

Output Files¶

All conversions produce a ZIP file that is automatically extracted to a dedicated folder.

Default output (workspace root):

workspace-root/
├── SalesReport-converted.zip               ← ZIP file (created)
└── SalesReport-converted/                  ← Extracted folder (NEW)
    ├── SalesReport.repx                    ← Converted report (NEW)
    ├── SalesReport-conversion-guide.md     ← Manual steps (NEW)
    ├── SalesReport-conversion-report.json  ← Statistics (NEW)
    └── subreports/                         ← Subreports (NEW)
        ├── RegionDetails.repx
        └── ProductList.repx

Benefits:

All conversions use the same consistent format
ZIP file can be easily archived or shared
Clean separation from your original files
Easy to find all conversion output in one place
Simple to move or delete the entire conversion
No risk of overwriting existing files

Conversion Summary¶

You'll see a summary like:

✅ Conversion Complete

📊 Statistics:
   • Total Controls: 45
   • Fully Converted: 42
   • Partial: 3
   • Unsupported: 0

📦 ZIP file created at: /path/to/reports/SalesReport-converted.zip

⚠️ TASK: Extract the ZIP file to: /path/to/reports/

The ZIP contains:
   • Main REPX report
   • Conversion guide (markdown)
   • Conversion report (JSON)
   • Subreports (if any)

Next steps:
1. Open SalesReport-converted/SalesReport.repx in DevExpress Report Designer
2. Review SalesReport-converted/SalesReport-conversion-guide.md for manual adjustments
3. Test the report with your data

Manual Review Items¶

Some RDLC features require manual adjustment in DevExpress:

Common Items Requiring Review¶

Complex nested tables - May need layout adjustment
Custom expressions - Some VB.NET functions need conversion
Advanced formatting - Complex conditional formatting
Custom aggregates - May need manual recreation

Using the Conversion Review Guide¶

Open YourReport-conversion-guide.md to see:

For Partial Conversions:

Quick reference table of all controls needing review
Control-specific checklists (Tablix, Table, Rectangle, Subreport)
Data binding verification steps
Step-by-step instructions for each control

For Manual Tables:

Which nested tables need recreation
Specific steps to fix each item
Before/after examples
Best practices

The guide automatically adapts based on what needs attention in your report!

Troubleshooting¶

Conversion Fails¶

Check API health:

curl http://localhost:5000/health

Should return:

{"status":"ok","service":"RDLC to DevExpress Conversion Service (Internal)","version":"3.0-mcp"}

Common Issues:

RDLC file is corrupted → Try opening it in Visual Studio first
File too large → Check size limits in configuration
Missing dependencies → Ensure all subreports are available

Files Not Created in Workspace¶

Check Cursor console for errors
Verify MCP configuration in ~/.cursor/mcp.json
Ensure write permissions in your workspace
Try a simple test file first

Advanced Configuration¶

Accessing Mapping Rules in Cursor¶

Ask Cursor:

"What are the RDLC to DevExpress mapping rules?"

Cursor will fetch the rules from the MCP resource.

FAQ¶

Q: Can I convert multiple reports at once?
A: Yes, but sequentially. The system processes one file at a time - there's no built-in batch API that accepts multiple files in a single request. However, you can ask Cursor AI to convert multiple files, and it will loop through them one by one. Each conversion is independent, so if one file fails, the others will still complete successfully.

Q: What happens to my original RDLC files?
A: They are not modified. The converter only creates new files.

Q: Can I customize the conversion output?
A: The converter follows standard RDLC to DevExpress mapping rules. For custom requirements, you can modify the converted REPX files in DevExpress Report Designer.