Hello,

I am preparing to upgrade a large multitired app, with both web and "fat"
client to VB. net. I was wondering what are the biggest risks, most
complicated points etc. I have already encountered some very nasty
type-checking over Variant code. Anyone wth more expirience on upgrade?

Thanks

Dominic,
Depending on how clean or not clean your VB6 code is, you may be in for a
bumpy ride.

To help smooth out this bumpy ride, I find having clean, object oriented
code in VB6 a definite benefit before you upgrade.

I find if you have relatively clean VB6 code (which the Code Advisor helps
identify) using the upgrade wizard is a definite plus.

Due to the shift from object based programming in VB6 to object oriented
programming in VB.NET some suggest you simply rewrite (redesign). If your
VB6 programs aren't even object based, the migration may make less sense.

Most of my VB6 programs have been as close as possible to object oriented as
VB6 allows, so upgrading for me made sense. After I upgraded I slowly
refactor (http://www.refactoring.com) the upgraded project to better
leverage the OO features of .NET (inheritance & the framework itself).

The Upgrade Wizard is part of VS.NET, while the Code Advisor is a download
from MS.

http://msdn.microsoft.com/vbasic/downloads/codeadvisor/default.aspx

The Code Advisor will allow you to modify your VB6 project, so that the
upgrade wizard does a better job of upgrading it. Such as flagging variants
& other code the Upgrade Wizard has trouble with. You can add your own
checks to the Code Advisor.

Hope this helps
Jay


[quoted text, click to view]