Link to home
Start Free TrialLog in
Avatar of wjbennett
wjbennettFlag for United States of America

asked on

Badly coded VB3 to dot net or beyond

I've recently acquired the codebase for a full-featured GL & property management product in pretty rough VB3 with Access 1.1 behind it (virtually no error handling!)

I need a functional conversion to a new language and out the door within a year. I have extensive VB6 experience and over ten years interface design, and am happy to deal with that (or drive the conversion team crazy), so the challenge is making it work and cleaning up the mess.  Naturally I have a miniscule budget and a crazy time line. The good news is that I do have a few good beta testers, and lots of old customers.

So, here are my questions:

a) what should the target development environment be - VB.Net, C# or....?
b) anyone have a good outsource reference? (India, Russia, China...) Horror stories are appreciated, too.
c) anyone have a burning desire to do it?

Please submit your arguments, too - I'm more interested in how you think than what you think! ;-) Thanks!
ASKER CERTIFIED SOLUTION
Avatar of dancebert
dancebert

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of wjbennett

ASKER

Thank you for your responses so far. Yes, I completely agree that a complete ground-up re-write is assumed, and that autocoders are not worth the trouble. I also agree that experienced OOP programmers are essential. I guarantee the current Access schema is a counterexample.

I've managed two of these projects with considerable success before (vb3 to vb6 and Vb6 to vb6), just looking for current resources and references.  So we're back to...

1) What's the best language: one vote so far for VB.NET. What are the selling points over C#?
2) Where can I outsource (cheap)? Thanks for the rentacoder response and about MS SQL and,
3) Anyone want to do it?
Avatar of dancebert
dancebert

>I've managed two of these projects with considerable success before (vb3 to vb6 and Vb6 to vb6),

Those were version changes.  Going from VB3 (or any version <= 6) to .Net is as big a leap as going from VB3 to C++, for example,: it's a paradigm shift.  
I think the points should be dividend to all participator because it was a more of a discussion then a question to help wjbennett make a decision.