.NET Market Survey: Which C# Frameworks Are Chosen for Production in 2025

Survey: Which C# (.NET) Frameworks Are Used in Production

The .NET ecosystem continues to actively develop: new versions are released, performance improves, and cross-platform tools emerge. But what do C# developers actually use in production projects? The team behind the PythonLib portal, together with the DotNetRu community, conducted a survey among 780 respondents — .NET developers from Russia, the CIS, and Europe. We share the key results.

1. ASP.NET Core — the Undisputed Leader

87% of respondents named ASP.NET Core as their primary framework for web applications and APIs. Reasons include: high performance, built-in support for containerization (Docker, Kubernetes), and a rich middleware pipeline. The vast majority of respondents (72%) use .NET 8 or newer.

2. Blazor is Gaining Momentum

Blazor (both Server and WebAssembly) showed growth to 23% in production — 10% more than a year earlier. Developers note that they use it for internal corporate portals and dashboards where rapid development without separating frontend and backend is important. However, for high-traffic public websites, Blazor still lags behind SPA frameworks.

3. WPF and WinForms — Enterprise Classics

Despite their age, WPF (31%) and WinForms (19%) remain in demand in legacy projects in the banking and industrial sectors. Interestingly, 15% of respondents noted a hybrid approach: using WPF together with .NET MAUI to transition to modern platforms.

4. .NET MAUI — Hope and Disappointment

Only 9% of survey participants use MAUI in production. The main complaints are unstable performance on Android, performance issues on iOS, and incomplete support for hot reload. However, after the release of .NET 9, the situation may improve — the community is awaiting refinements.

5. Xamarin.Forms is Fading Away

Usage of Xamarin.Forms has dropped to 4% — most are migrating to MAUI or native solutions (Kotlin/Swift). According to the survey, projects on Xamarin are finishing their last versions and not adding new functionality.

6. Other Frameworks and Libraries

• SignalR — 34% for real-time functionality (chats, notifications).
• gRPC — 21% for microservice architecture.
• Entity Framework Core — 91% paired with any framework.
• Orleans — 6% for distributed systems.

Trends and Conclusions

The .NET market is becoming more mature and diverse. ASP.NET Core remains the uncontested choice for the web, Blazor is actively catching up to React/Angular in the B2B segment, and MAUI has not yet met the expectations of mobile developers. If you are just starting to learn C# for production — focus on ASP.NET Core and EF Core, and leave Blazor as a promising tool for future projects.

Full survey data is available in our Telegram channel PythonLib. Which framework do you use? Share in the comments!