|
-
Aug 23rd, 2005, 02:42 AM
#1
Thread Starter
Lively Member
converting windows forms (VB6) to .NET individually
I'm trying to convert an old project to the .NET 2003 environment. Sadly the crappy upgrade wizard hangs during conversion. Is there a way to convert old VB6 forms individually to .NET forms without having to run the wizard?
If there was nobody would be using the upgrade wizard or recode their entire project, I realise that... but on the off-chance, is there a way any of you know? :hopeful:
A post brought to you by the Grim Reaper Appreciation Society™
"Buy your lifetime subscription now and save on your coffin"
-
Aug 23rd, 2005, 03:03 AM
#2
Re: converting windows forms (VB6) to .NET individually
better code it in .Net mate.
You have to study .NET and try to remake your vb6 apps to .NET just like some vb6 developer did. Namely Robdogg888..etc..
-
Aug 23rd, 2005, 03:13 AM
#3
Thread Starter
Lively Member
Re: converting windows forms (VB6) to .NET individually
I don't really have the time to code it or team members to give it out to. You know how it is.
Ah well... could use the overtime
A post brought to you by the Grim Reaper Appreciation Society™
"Buy your lifetime subscription now and save on your coffin"
-
Aug 23rd, 2005, 04:37 AM
#4
Re: converting windows forms (VB6) to .NET individually
The wizard can take AGES to convert some projects, especially if they have stupid things like VB6's pseudo "control arrays".
Did you give it long enough?
I don't live here any more.
-
Aug 23rd, 2005, 05:07 AM
#5
Re: converting windows forms (VB6) to .NET individually
Welcome to the dark side.
-
Aug 23rd, 2005, 05:08 AM
#6
Thread Starter
Lively Member
Re: converting windows forms (VB6) to .NET individually
I wish it was just that. Here he simply hangs with the generic M$ bullcrap message that the parsing was halted for the reason du jour.
A post brought to you by the Grim Reaper Appreciation Society™
"Buy your lifetime subscription now and save on your coffin"
-
Aug 23rd, 2005, 12:26 PM
#7
Re: converting windows forms (VB6) to .NET individually
The upgrade wizard to convert your vb6 code will never do a 100% job. It is at best, as stated by MS, a 95% conversion. Either way you need to do allot of work. No easy way around it.
You can spend 20 hours fixing the conversion for ex. or spend 30 hours rewritting i in pure .net code. I'll always take the rewrite since it will end up better and with less bugs.
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum. 
Microsoft MVP 2006-2011
Office Development FAQ (C#, VB.NET, VB 6, VBA)
Senior Jedi Software Engineer MCP (VB 6 & .NET), BSEE, CET
If a post has helped you then Please Rate it! 
• Reps & Rating Posts • VS.NET on Vista • Multiple .NET Framework Versions • Office Primary Interop Assemblies • VB/Office Guru™ Word SpellChecker™.NET • VB/Office Guru™ Word SpellChecker™ VB6 • VB.NET Attributes Ex. • Outlook Global Address List • API Viewer utility • .NET API Viewer Utility •
System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB & SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24" LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6 
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|