VB.NET to C# migration
Move your VB.NET system to C#, and prove nothing broke
Many businesses still run on software written in VB.NET or older versions of .NET. It works, but it's getting harder to hire for, harder to support, and stuck on a platform Microsoft is no longer developing. We move it to C# and modern .NET without a rewrite, and without stopping your business.
- ~2,000code files converted automatically
- ~700screens converted, including Razor views
- 2,827tests passing on old and new
Why not just rewrite it?
Your system holds years of business rules: the exceptions, the special cases, the fixes nobody remembers making. A rewrite throws all of that away and tries to rediscover it, usually over budget and with the business on hold.
Free conversion tools exist, but they translate code line by line and leave you to find out what they got wrong, and they don't touch your web pages at all. On a large system that means weeks of hand-fixing and a lot of crossed fingers.
How we do it
-
Convert automatically
Our tooling converts the whole codebase, including VB Razor views (
.vbhtml), in one step. Every fix goes into the tooling, never into the output, so the conversion can be repeated at any time. -
Prove it's the same
Each conversion has to build cleanly and pass the same tests as the original. We also compare the compiled code of the old and new versions, and screenshot every page of both sites to catch visual differences.
-
Switch over safely
Because conversion is repeatable, your team carries on working on the original while we prepare. Staff can use the converted version side by side with the live one before you switch.
What you get
- Your system in C#, building cleanly, with the same behaviour
- A report of every difference found and how it was resolved
- The option to move on to the latest .NET, using the same step-by-step, checked approach
- Ongoing support afterwards, if you want it
Is this for you?
It's a good fit if:
- your business depends on a VB.NET application, website or Windows program
- you're finding it hard to hire or keep developers who want to work in VB.NET
- you're stuck on .NET Framework and want to move to modern .NET
- a rewrite has been suggested and the cost or risk worries you
We used this approach on a 13-year-old system that runs a busy online retailer, with the business trading throughout. Read the case study.
Common questions
Do we need automated tests already?
They help, but they aren't essential. Comparing the compiled code and screenshotting every page give strong checks on their own, and we can add tests around the most important parts of your system as part of the work.
Do we have to stop development while you work?
No. The conversion is repeatable, so your team keeps working on the original and we regenerate the C# version from the latest code whenever we need to.
What about Windows desktop programs?
Windows Forms and other desktop code converts the same way. The page-by-page screenshot check applies to websites; for desktop programs we rely on the build, the compiled-code comparison and your tests.
How much does it cost?
It depends mostly on the size of the system and how much of it is web pages. We'll look at your code first and give you a fixed price for the conversion before you commit.
Will you need access to our code?
Yes, a copy of the source code and, ideally, a test database. We're happy to sign a non-disclosure agreement first.
Got a VB.NET system you're worried about?
Tell us a little about it. We'll tell you honestly whether migration makes sense, and what it would involve.