We have migrated VB6 code to C# in .net.
Posted
by VB
on Stack Overflow
See other posts from Stack Overflow
or by VB
Published on 2010-04-29T11:31:29Z
Indexed on
2010/04/29
11:37 UTC
Read the original article
Hit count: 91
The code was migrated using a third party tool. what ever the tool couldnt do, was done by the .net developers, so that all compile issues were fixed. My question is, for such migration activities, do we not bother running unit tests for the functions.
Secondly, Could anyone suggest if we should use some tool in VSTS 10 to create a UML model of this code to minimize risks of issues that the client might find. How cumbersome is it.
Are there any other suggestions for how quality migrated code can be delivered, in light of the fact that the functionality of the original VB6 application is unknown to us.
© Stack Overflow or respective owner