// blog
Moving a WinForms App to the Web: What Your C# Code Can Keep
When a Windows Forms app moves to the web, its forms and DataGridViews are rebuilt as web screens with the same columns and shortcuts, while C# business classes that don’t touch the screen can often move to the web version’s C# server largely as they are. The SQL Server database can stay, Crystal Reports or RDLC reports become print pages and PDFs, and nobody installs anything on their PC anymore.

Windows Forms apps run a lot of businesses: built in C# or VB.NET in the 2000s and 2010s, installed on every PC, updated by walking from desk to desk. Of all the desktop programs we move to the web, they have the biggest head start.
What gets rebuilt
The forms. DataGridViews, tabs and dialogs become web screens with the same columns, the same order and the same keyboard shortcuts. Code-behind in button handlers is where rules hide, so each rule is written down as a plain sentence and checked by the people who use the app.
What can come along
The web version’s server is C# too. Business classes that don’t touch the screen, like pricing, validation and calculations, can often move across largely as they are. That’s less to rewrite and less to retest.
Your SQL Server database can stay, or move to PostgreSQL. Either way the records are checked against the old app before anyone switches.
What changes for your people
Nothing to install. The app opens in any browser, from the office or from home, and an update reaches everyone at once. Crystal Reports or RDLC reports become print pages and PDFs that look the same.
See how a WinForms app moves to the web. The first call is free.
































































































































