Extended VB6 to .Net Migration -- vb.net upgrade

vb.net upgrade : Extended VB6 to .Net Migration

aww91 NO[at]SPAM yahoo.com
3/16/2006 8:09:14 AM

Considering a phased VB6 to .Net migration approach and looking for
opinions from individuals who may have experienced in this area.

Budget cuts do not allow dedicated planned 12 month effort to migrate
large VB6 application to .Net, therefore considering opportunistic
approach for migrating code segments whenever resources are available;
promoting completed an dtested changes to production, and continuing
this approach until the entire application is migrated over (1 - 2
years). Prioritizations and logical groupings a factor, as well as,
training and rollout of completed pieces. Can anyone who have
considered or gone though this type of experience share their thoughts?

Thanks in advance,

Homer J Simpson
3/16/2006 6:23:00 PM

[quoted text, click to view]

How do you 'roll out' a partially migrated system?

Earl
3/25/2006 3:11:14 PM

What do you consider "large VB6 application"? My experience would say to
migrate the entire application to .Net while maintaining the existing one
until the .Net upgrade is complete. Furthermore, if you do not have .Net
experience, an upgrade will probably only lead to more pain. I would
strongly consider looking into the MSDN resources in this area. While more
tools are available today than 3 years ago, it is still very important to be
able to anticipate where the problems will arise before beginning the
process.

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about vb.net upgrade

home · blog · groups

Questions? Comments? Contact the dn