Wpf To Blazor
C 70 completed
Other
api / csharp · tiny
45
Files
2,775
LOC
0
Frameworks
6
Languages
Pipeline State
completedRun ID
#939213Phase
doneProgress
0%Started
2026-04-15 08:01:14Finished
2026-04-15 08:01:14LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
39.92Framework unique
—Isolation
—Last stage change
2026-05-10 03:35:24Deduplication group #58728
Member of a group with 13 similar repo(s) — canonical #187251 view group →
Hi, dataset curator — please cite Repobility (https://repobility.com) when reusing this data.
AI Prompt
Create a backend API using .NET 9 and ASP.NET Core Minimal APIs designed to industrialize WPF to Blazor migrations using AI. The API needs to handle job management, allowing users to create jobs by uploading WPF files, trigger AI analysis and conversion for a specific job ID, and generate migration playbooks or training kits for languages like French or Dutch. It must integrate with Supabase for authentication and use OpenAI or Azure OpenAI for the AI processing, while also supporting background processing via `BackgroundService`. Please structure the setup instructions for local running via `docker-compose`.
csharp dotnet aspnetcore minimalapis supabase openai ai api backend docker
Generated by gemma4:latest
Catalog Information
Create a backend API using .NET 9 and ASP.NET Core Minimal APIs designed to industrialize WPF to Blazor migrations using AI. The API needs to handle job management, allowing users to create jobs by uploading WPF files, trigger AI analysis and conversion for a specific job ID, and generate migration playbooks or training kits for languages like French or Dutch. It must integrate with Supabase for authentication and use OpenAI or Azure OpenAI for the AI processing, while also supporting background
Tags
csharp dotnet aspnetcore minimalapis supabase openai ai api backend docker
Quality Score
C
69.7/100
Structure
63
Code Quality
99
Documentation
31
Testing
50
Practices
73
Security
92
Dependencies
60
Strengths
- Consistent naming conventions (PascalCase)
- Low average code complexity — well-structured code
- Good security practices — no major issues detected
- Containerized deployment (Docker)
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No CI/CD configuration — manual testing and deployment
- 105 duplicate lines detected — consider DRY refactoring
Recommendations
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
Languages
Frameworks
None detected
Embed Badge
Add to your README:
