There is an application that tries to upgrade existing VB6 applications to .Net but ...

-I have taken a look at this upgrader with simple apps and I won't do it with real apps.
-The generated .Net apps is full of wrapper around VB6 controls (instead of converting to .Net controls).
-VB6 is not Object Oriented and .Net is. Why would you port an app not to use these new features?

My recommandation is to maintain existing VB6 apps in VB6 until you really need to re-work them and create new apps in .Net. Meanwhile, you can create .Net DLL that are usable from VB6 to start your transition from one to the other.



>What is involved in converting a VB6 application to VB.Net? Will an existing VB6 application run under VB.Net unchanged?
>
>Are there any articles describing this process.
>
>Thanks,
>
>Jerry