Is this the “one in ten” time to rewrite?

Question

I\'m very much against rewriting an application if it can be avoided. I understand the rule that 9 times out of 10, it\'s better to refactor, but I\'m in a situation where it m

Answer 1

Start converting the different modules one at a time, phasing them out of the VB6 application.

Prioritise according to what is mission critical/strategic, so you can also add value as you go along.

Since the database will be the integration point, make sure you fix the relevant parts (relavant to whatever you are working at the time), so you are building on a solid foundation.

In the short term, you will have more work (both VB6 code and .NET to maintain), but with a cleaner architecture, you will be able to start moving away from the legacy application faster and faster.

This way you will have both systems running at the same time for a while, so you have a fall back, and you can add proper structure (architecture, database integrity etc).