Printable View
so i downloaded the 2005 beta environment for VB .NET
i LOVE the new environment, however, i notice that the code structure has changed a bit
im a really ruster programmer as ive not used vb in a little less than a year
i opened up some a of my old vb6 projects and im seein that vb .net doesnt like the old vb6 code - keeps saying it has all these errors and whatnot
is there a significant difference between the 2 in the way you write code altogether or is it telling me my code is sloppy lol
VB6 and VB.NET are different. You can't just copy and paste vb6 code into the vb.net ide. You have to convert it to vb.net syntax first. I don't know if VS2005 comes with a vb6 to vb.net upgrade utility.
well i did convert itQuote:
Originally Posted by mendhak
but even with the new code it still gave me errors - thats why im posting this :-\
i think it would be great if you will start coding your vb6 code to vb.net style.
especially in OOP style.
Or if you told us what code is giving you the error. If it's simple you won't need to rewrite it. If it's not simple, you should be rewriting.
The upgrading from VB6 to .NET is pretty poor. I haven't heard of anybody who was happy with it, and most people suggest that you start over rather than convert.
There are two good reasons to start over:
1) You can do a better job the second time around. It is almost always the case that we understand the problem more throughly once we have solved it once.
2) You can change the design to a more OO style. This can be pretty big. VB6 did not encourage encapsulation the way .NET does. Now there are real advantages in considering how chunks of data could be encapsulated.
And one BIG drawback:
1)TIME!
Rewrite it. Take my word for it.
That's the understatement of the century :p.Quote:
Originally Posted by - joker -
When you paste VB6 code, VB.Net will bitzch about it - it doesn't matter whether your code is the jewel of VB6 or utter dogzhit. You can almost say that VB.Net is a completely different language than VB6. If you're interested in migrating, the best way to proceed would be to get familiar with the .Net framework and then pick your strategy (use COM interop to leverage old VB6 code or do a rewrite).Quote:
Originally Posted by - joker -
Cheers,
NTG