What We Build with C# and .NET
- backends for websites, portals and mobile apps;
- enterprise systems for managing requests, documents, inventory or manufacturing;
- background services that sync data with accounting software or banks every night;
- web interfaces and updates for Windows desktop applications used by office staff.
Most business projects need the first three: systems with a lot of business logic, integrations and users with different permissions.
When We'd Recommend Something Else
If your company isn't tied to Microsoft products and the system is large and long-lived, Java is an equally strong alternative; the choice often comes down to your existing team and infrastructure. For a small website that needs to launch quickly and be easy to hand off for maintenance, PHP and off-the-shelf CMS platforms are more practical, and the same project on .NET often costs more. For mobile apps, we more often recommend native development or Flutter.
Moving from .NET Framework to Modern .NET
.NET Framework still works and receives security fixes, but no new features are being added, and new libraries rarely support it. If you plan to keep developing the system, we recommend planning a move to modern .NET.
Migration is straightforward when a project uses standard libraries, and harder if it relies on Web Forms or other technologies that don't exist on the new platform. We first assess what can be migrated automatically and what has to be rewritten, then move the system over in stages. Our general approach is described on the legacy system modernization page.
Web, CMS and Cloud
For content-heavy sites edited by marketers, we use Umbraco, a .NET-based CMS. For services, customer portals and APIs, we use ASP.NET Core. If your infrastructure is on Microsoft's cloud, we configure that too: databases, message queues, file storage and event-driven functions on Azure. Learn more on our cloud infrastructure and Azure page.
Windows Applications for Employees
Many companies still run C# desktop applications: point-of-sale systems, warehouse apps, operator workstations, label-printing utilities. Often they were written years ago by a single developer, and now nobody dares to touch them. We either stabilize the existing app (upgrade the platform, fix bugs, add data sync with a new accounting system) or gradually move its features to a web interface that opens on any computer. Which option pays off depends on how tightly the app is tied to hardware and local files.
Integrations and Background Processes
Enterprise .NET systems typically exchange data with ERP and accounting systems such as QuickBooks, CRMs, banks and websites. We move these exchanges into separate background services with retries and logging: if an external system is unavailable, data isn't lost but sent later, and you can see what happened.
What to Prepare Before Kickoff
- Access to the existing code, the build process and the servers or Azure subscription, if the system already exists.
- A list of the systems to integrate with and their API documentation.
- Information on how employees sign in today: corporate accounts, Microsoft 365, Active Directory.
- Your uptime and security requirements, so we can plan infrastructure accordingly.
What Affects Cost and Timeline
- Type of work: a new system, enhancements or migration from legacy .NET Framework.
- Amount of business logic: roles, workflows, documents, calculations.
- Integrations: accounting systems, banks, Microsoft products, external APIs.
- Infrastructure: Windows or Linux, on-premises servers or Azure, fault-tolerance requirements.
- Code condition: tests, documentation, the number of outdated technologies.
- Licensing of related products, if the project uses a paid Microsoft database or server OS.
We provide an estimate after an audit or a discussion of your requirements and break it into phases so you understand what the budget covers.
Frequently asked questions
Do we need a Windows server for a .NET system? No. Modern .NET runs on Linux and in Docker containers, which is often cheaper to maintain.
Our system runs on .NET Framework. Can we leave it as is? For a while, yes, since it still gets security updates. But if you plan to keep developing the system, it's better to plan a migration.
Can .NET be combined with a React or Angular frontend? Yes, it's a common setup: .NET handles data and logic, and the interface is built separately.
Can a .NET system be moved to another data center or cloud? Yes. After migrating to modern .NET, the application is packaged in a container and runs wherever you prefer, without being locked into a specific host.
Will you take over a .NET system built by another team? Yes. We inventory the code first: .NET versions, packages, Windows dependencies and parts that won't port to the new platform. Then we propose a phased plan.
Who keeps the system up to date after launch? We can. We update .NET and packages according to Microsoft's support schedule and set up logging and error alerts.
Why Promodex
We say upfront when .NET is the right choice and when a task is easier to solve with other tools. Promodex has been in business since 2015, with 750+ projects in our portfolio. Our developers, designers and marketers are in-house, so accountability for the result isn't spread across subcontractors. You see the scope and phases before work starts, and after launch we support the system and upgrade it to new platform versions.