Damien
Thu Oct 19 02:46:33 CDT 2006
tom c wrote:
> I hate doing estimates of how long things will take, but of course
> people want them. I am doing some modifications on a VB6 system and
> the owner wants an estimate on how long it will take to convert it to
> VB dot net. How would you approach doing a time estimate on this?
>
> I have worked in VB dot net, but I have never converted a system from
> VB6 to dot net.
I'd suggest getting the VB6 Code Advisor from Microsoft:
http://www.microsoft.com/downloads/details.aspx?FamilyID=a656371a-b5c0-4d40-b015-0caa02634fae&DisplayLang=en
And letting it have a chug through your project. If it comes out saying
there's nothing to change, you're probably in fairly good shape. If it
comes out with thousands (or millions) of required changes, you may be
in for a rough ride.
Once it's gone through your project, you need to look at if it's one
single type of issue (possibly even one you can fix with a global find
& replace), or whether the issues are widespread and varied.
Hopefully, this will give you some ideas about the level of changes
that will be required in your application.
Bear in mind, even once you've fixed all of these issues, and
loaded/upgraded the project into .Net, it will still not be as good as
if you re-write some of the code into .Net, but it should at least
compile and be close.
Damien