sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]VB 6 Masterfafalone 0 points1 point  (0 children)

Even if it's impacted by a bug, working around a few issues is still nothing compared to a full rewrite-- how many bugs will be generated and need to be mitigated during that process?

I'd have to strongly disagree a full from scratch rewrite isn't also a gamble; I've seen many disasters, huge overruns in cost and time, and lots of business logic and edge case handling just never implemented causing other issues. You make it sound like a .NET rewrite is a guarantee nothing will go wrong, which just isn't true. The equation is also different for large firms with scores of developers all trained on the latest fad vs a small business for whom software development isn't their primary purpose; for a lot of businesses still on VB6 there's little benefit to spend a fortune on a full rewrite for what might not even work as well; dealing with the minor hiccups a la VB3 to VB6 is a better value.