A free and open-source web framework that enables developers to create web apps using C# and HTML, developed by Microsoft.
GitHub copilot is the default for visual studio and visual studio code and is the easiest to setup.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I want to build a new project using the ".NET MAUI BLAZOR HYRID and Web App" visual studio template, in additon to SQL Server and Entity Framework. now i want to use AI to help me developing this app, which should produce workable tennis club app that can run as mobile app, desktop app and web app.
so which AI is most suitable for this tasks? ChatGPT, GIT Hub Copilot, Claude or Microsoft Copilot ? and why?
Thanks
A free and open-source web framework that enables developers to create web apps using C# and HTML, developed by Microsoft.
GitHub copilot is the default for visual studio and visual studio code and is the easiest to setup.
Honestly, any of them can help, and the gap between them is smaller than the gap between using one well and badly. For this template, though, I'd pick GitHub Copilot inside Visual Studio as the main tool, and here's why.
It works on your actual solution. The ".NET MAUI Blazor Hybrid and Web App" template gives you three projects (the MAUI app, the web app, and a shared Razor class library), and Copilot in Visual Studio can see all of them, build, read the errors and fix them in agent mode. Pasting code back and forth from ChatGPT or Microsoft Copilot in a browser gets painful fast with that many projects. Claude is also strong for this, but the most useful way to use it here is through a coding agent (Claude Code, or Claude as the model inside Copilot), not the chat website. Copilot lets you switch between models, so you can try both.
Whatever you choose, two things will matter more than the tool:
Give it current .NET docs. AI tools often mix up MAUI and Blazor patterns from older versions. Connect the Microsoft Learn MCP server to your assistant so it can look things up in the official docs instead of guessing.
Get the architecture right before asking it to write features, because AI will happily generate code that works in the web app but is wrong for the phone. The important one for your tennis club app: the mobile and desktop apps shouldn't connect to SQL Server directly. Put Entity Framework and the database behind a Web API (the web project in the template is a natural place for it), and have the MAUI app call that API. Keep your pages and components in the shared Razor class library so all three apps use the same UI.
A good first prompt is to describe that structure (shared UI library, Web API with EF Core and SQL Server, MAUI app calling the API) and ask it to build one small feature end to end, for example "list courts and book a slot". Then check it runs on the web and on Android or Windows before moving on.