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

Having been on a project where we did the app and the database all at once I would recommend trying to get the database correct first and then doing the app after that.

Trying to do both simultaneously could prove very painful. However without being next to you looking at the code it is always tough to say for sure.

I just always feel that if you have the database and you can rely on it you should be able to rewrite using integration tests and then unit tests so much more reliably.

Once you have the database solid I would think a best case scenario would be to try and modularise the code into separate and reusable assemblies (which you should be able to use in .NET) and then gradually mograte those to .NET from VB. That might not be possible if the code is horrendous smelling spaghetti!