I never tried VB Express 2005 before because I did not ever understand the changes that were between VB6 and VB2005. Can someone explain to me like all I need to know to begin developing for VB2005?
Printable View
I never tried VB Express 2005 before because I did not ever understand the changes that were between VB6 and VB2005. Can someone explain to me like all I need to know to begin developing for VB2005?
The number one thing you need to know is that VB.NET is fully object-oriented. That is the biggest stumbling block for VB6 developers migrating. There are several links in my signature I'd suggest you take a look at. The first one is a must for all new to Windows application development in an OO language. Also, the eBook from Microsoft on upgrading from VB6 to VB 2005 is bound to be useful. The Start VB.NET tutorial also has a section dedicated to OOP. There's lot's of other good stuff in there too. The main thing you need to do is assume that everything you do will be different from how you did it in VB6. There will be some things that turn out to be the same but if you look for things to be the same you'll end up fighting the language and having a less fruitful experience.
Download and read the book provided for free by registering VB 2005 Express edition, it provides a good overview of basic program development in the .NET era, information that should give you the grounding for migrating your existing VB6 skills over to the .NET platform.
Also, welcome aboard the .NET ship, you won't be disappointed :bigyello:
Also note that VB.NET is not like VB6 at all. The language has been completely redone from the ground up, and the syntax has been changed tremendously, making it closely like Java, C++, and C#, only without the semicolons. The reason why the syntax is now closely related to the other languages is so it makes it easier for you to be able to learn another language.
Actually I don't agree with that, the syntax structure is the same, it's really only the OOP side that's changed, once you understand OOP, classes, objects, inheritance, it's the same thing, just the way it should've been implemented. For it to be what you say, it would have to remove things like WithEvents and the like, it's still VB, just with a twist.
Learning the .NET way - especially OOP but also navigating the class libraries - is a struggle in the beginning for vb6ers, I had VS2002 installed for months before I really tried it, I got put off by it everytime I tried something.
Nowadays I truly hate vb6, when I look at some code (and the terrible hacks you needed to do something really interesting), I shudder. The .NET libraries eliminate the need for PAGES full of APIs.
Everything is different, for the better.
Personally I prefer C#, it is more strict by itself and the syntax is more logical when you get used to it. If you have coded in C++ or in JAVA then I don't need to tell you this I guess.
There is nothing we can tell you that will give you all the answers to your question but if you just start out on your first 05 project I'm sure you will see the diffs. and come up with a question or two that we can answer for you. :)
That's not necessarily true because if the syntax structure were the same, the code would be backwards compatible, although the Microsoft.VisualBasic namespace helped somewhat. When I convert my projects from VB to VB.NET, you have no idea how many times I had to change nearly half of my code cause of all the errors I had received. :rolleyes:Quote:
Originally Posted by Ideas Man
Dont use that stupid wizard at all. Its useless and you spend more time fixing its errors that it couldnt convert. Also, its not the best logic or performance that way either.
Who said I even used that lame wizard? I was talking about by hand. The wizard just makes things worse.
What does syntax have to do with compatibility?
Not much I think.
Because you said you had to convert your vb 6 code and got all kinds of errors. If your not using the wiz then are you actually trying to paste in your vb5/6 code? If so then of course yur going to get all kinds of errors. If your not using the wiz to convert it then you should be doing a complete re-write instead.
:confused: That is so not true. C++, Java and C# all use a C-based sybtax, but none of them IS C. VB.NET uses a VB-based syntax, but it is not VB6, but it is so not like C++, Java and C# either. They have made some changes to make using different .NET languages more consistent, but if you were to place the VB.NET syntax on a scale of 1 to 100, where 1 is VB6 and 100 is C, it would fall in the 1 to 10 range. As for syntax and compatibility, as I said, C++, Java and C# all use a C-based syntax but none of them is "compatible".Quote:
Originally Posted by Jacob Roman
The syntax as not changed at all, all that's changed are class and method names, and believe me, that is NOT syntax! If you start saying "the syntax has changed" then your going to put people off, syntax is the rules of the language, correct if I'm wrong, but MessageBox.Show() over MsgBox(), not only does it look better, easier to use, but it's a function, which although changed, has NOT changed the syntax of the language at all.
A syntax change would be to force each line to end with a semicolon, that's a syntax change.
I can't dare to convert my vb6 data app to .net, as I have 79 forms and 18 data & crystal reports + 35000 lines of code, and I am in learning phase of vb.net, As Robdog said don't use wizard, it will take a bit long time to convert it manually and fix its logical bugs.
can you please give a link to download the bookQuote:
Ideas Man Download and read the book provided for free by registering VB 2005 Express edition,
Register the IDE and they'll give you the link. It's one of the Registration Benefits. Also, Microsoft provide a free eBook on upgrading from VB6 to VB 2005. See my signature for a link.Quote:
Originally Posted by sanjaylimbikai
I'm afraid not, as jmcilhinney said, register it from inside the IDE (I think it's in the help menu) and it will appear on Microsoft Connect, along with some other goodies such as some icons and things. Your not supposed to distribute it because it is an electronic copy of their printed book, but if you do it before around October/November, you should be able to get it no worries.Quote:
Originally Posted by sanjaylimbikai