jorge Posted October 23, 2003 Posted October 23, 2003 Hey all, I used to have vb.net 2002, there i could update a vb6 project to .net, but i now have vb.net 2003 and it always gives errors when i try, doen anyone know what wrong? Quote Jorge - http://www.blackdot.be/?page=apache.htm
Administrators PlausiblyDamp Posted October 23, 2003 Administrators Posted October 23, 2003 What errors does it give? There is a migration wizard in 2003 (not sure if it's in all versions though). Although it's an improvement over the one in 2002 it's still pretty naff and I would recomend against using it. Quote Posting Guidelines FAQ Post Formatting Intellectuals solve problems; geniuses prevent them. -- Albert Einstein
jorge Posted October 23, 2003 Author Posted October 23, 2003 it give an error about comondialog crontrole, Don't know if this can be the problem, but i remenber i use to have vb6 install on the compiter with vb.net 2002, but befor i installed 2003 i formated my c, so can it be i need to install all the vb6 ocx's? Quote Jorge - http://www.blackdot.be/?page=apache.htm
Administrators PlausiblyDamp Posted October 23, 2003 Administrators Posted October 23, 2003 You will also need VB6 installed to get the customer controls on your system so the wizard can upgrade code that references them. Probably better of just re-writting the code in VB.Net - the wizard generates bad code with lots of VB6 calls and a compatability layer thrown in as well. Trust me - it will probably be easier and better to write it again. Quote Posting Guidelines FAQ Post Formatting Intellectuals solve problems; geniuses prevent them. -- Albert Einstein
jorge Posted October 23, 2003 Author Posted October 23, 2003 hmmz, well maybe i'll rewrite it, only prob is it not my code, it my dad's and we well code a bit deferently anyhow, thanx for letting me know it was becouse i do'nt have vb6 anymore Quote Jorge - http://www.blackdot.be/?page=apache.htm
Jay1b Posted October 24, 2003 Posted October 24, 2003 Most of the can USUALLY be just copied into VB.NET and it will work - the only real problems are when its using Active-X controls. Quote
AndreRyan Posted October 24, 2003 Posted October 24, 2003 Or commands that should be avoided like InStr, Asc, Chr, etc. Quote .Net allows software to be written for any version of Windows and not break like Unmanaged applications unless using Unmanaged procedures like APIs. If your program uses large amounts of memory but releases it when something else needs it, then what's the problem?
Administrators PlausiblyDamp Posted October 24, 2003 Administrators Posted October 24, 2003 Or all the calls into the compatability layer - overhead for no reason. Or all the Database code still being ADO. Quote Posting Guidelines FAQ Post Formatting Intellectuals solve problems; geniuses prevent them. -- Albert Einstein
jorge Posted October 24, 2003 Author Posted October 24, 2003 Ok, i'll try it when i have a lot of time(in 2 days) Thanx for yout help and if it doen't work i'll compile it on my dads comp. Quote Jorge - http://www.blackdot.be/?page=apache.htm
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.