I have used VB5 and VB6 Excuse my ignorance but what is VB.NET
I see .NET Everywhere?
Printable View
I have used VB5 and VB6 Excuse my ignorance but what is VB.NET
I see .NET Everywhere?
.net is the newest version of vb. It is based on the classic vb language, but they have changed so much about it, it isn't even close to vb any more.
[opinion] I think vb6 is better [/opinion]
[joke] My .net teacher jokes and says the reason is called .net is because there are a million "." everywhere.[/joke]
Moved to General Developer
VB.NET is the lastest in programming language platforms produced by Microsoft.
It is a language in an of itself and provides a lot more functionality and flexibility than Visual Basic (although the VB in VB.NET stands for Visual Basic, that is where the similiarlity ends)
You can download a free copy of VS 2008 so you can see the differences for yourself.
And, I would suggest you do so.Quote:
Originally Posted by RhinoBull
Microsoft has dropped support for VB6, and it is being replaced in the market place and in the corporate world with the .NET platform.
Just for kicks, go to a job posting site and see how many companies have placed ads for VB6 programmers.
Now do the same search for VB.NET programmers.
Is there a big difference in the programming language ?
Is there a big difference between a Volkswagan and a Mazerarti?Quote:
Originally Posted by KenBZim
Yes, there is a HUGE difference. It is a new programming language.
Thanks RhinoBull Unfortunately I cannot download files that Size even a couple of megabytes is a problem on the telephone lines and modems where we are.
I will have to try and find somewhere that I can buy The CDs/DVD I would assume that it would be a DVD?
Oh yeah. You can probably purchase this straight from Microsoft.
I think the reason you think so is because you see VB6 and VB .Net as different versions of eachother, you dont like VB.Net because its too different from VB6. Am I right?Quote:
Originally Posted by Mxjerrett
If you gave VB.Net a chance whilst keeping in mind that it is a completely different language (None of the things you know from VB6 applies here, except for most of the syntax), I think (and hope) your views will change.
I'm not even sure this is true. There may be syntax similarities, but, by in large, even that is different.Quote:
Originally Posted by Atheist
I have never seen VB.NET and to be honest I am a bit scared.
I started with GW Basic in the 80's then Turbo basic and QB then saw Visual basic 5 in the nineties after being out of the computer world for some time.
I was used to Dos BAsed programming and had never used a mouse.
It was only when I saw VB5 that I got back into programming to me there was little transition from VB5 to VB6, But VB.NET scares me from what I have read on the forums, will I be able to cope with VB.NET???
I was thinking of the basic grammatics like subroutine blocks, IF/While/For statements etc. But you're right, much has changed.Quote:
Originally Posted by Hack
Yes defenitly, I can almost guarantee you that if you just get a decent VB.Net book, you'll be feeling secure in the language already after finishing the book. And if you have any questions there'll always be people in the VB.Net section to help.Quote:
Originally Posted by KenBZim
Oh, yes, right. So the OP won't think 100% different, those kinds of blocks still exist and function in the same manner, which would only make it 99% different than VB6. :DQuote:
Originally Posted by Atheist
Hack - Earlier you said that VB6 Won't run on Vista Is this VB6 platform OR applications which have been written in VB6 and then compiled to exe format?
Surely once compiled to stand alone exe they would run on any OS or am I wrong?
Atheist - Many thanks for your confidence!!!!
Does VB.NET use forms and modules like VB6 and OCX files like FlexGrid Listview etc.????
Other simple objects like text box, combo box etc???
Yes, VB.Net has plenty of controls to work with and most of them are more flexible than those found in VB6.
Flexibility however comes with price - object hierarchy could be much more complex (usualy is).
I first looked at .NET with the 2002 version. It was so different from VB6 that I stayed away at first. Eventually though, I had to start into it because there was no other good VB solution for portable apps (PDAs, phones, etc.). Once I got started into it, I began to like it more and more, and now I would never willingly return to VB6. With the experience you have had, I suspect you will rapidly feel the same way. Change and new learning can always appear daunting, but in this case, many of the changes are for the better. One of the nicest is the IDE, which I find very helpful and well organized relative to VB6. Intellisense may be more necessary with .NET than it ever was before, but it is also a bit more effective, too. Also, don't get too hung up on Object Oriented, it is there to use as you choose. It's a useful thing, but you can ease into it.Quote:
Originally Posted by KenBZim
Lastly, you have found a great resource for any help.
M$ are receiving a huge backlash over the dropping of support for classic vb, may have been a mistake imho.Quote:
Originally Posted by Hack
vb.net worth a look for multi threading alone would be my call.
Now trying to work out what MS are calling ajax, they have another name or something brewing away. Yes decided the first MCSD paper I would do would be the asp.net one.
Ken,Quote:
Originally Posted by KenBZim
You do not need to be scared over this. Yes, the .Net platform is a completely new one and has a steep learning curve. HOWEVER ... here's the deal. (I use both VB6 and VB.Net so I'm qualified to say this).
If you are interested in developing Windows desktop applications only then you will not hurt yourself to continue to develop them in VB6. Even though Microsoft has removed support for the product that does NOT mean that stuff you produce using it is going to just stop working. VB6 has an absolutely huge 3rd-party support mechanism which simply isn't going to go away any time soon. Even if you target Vista - most of what you write is going to work, unless you are doing something sophisticated. Offhand I'd say stick with XP as you development platform but your applications should run on Vista unmodified for the most part.
VB.Net [as well as the other languages in the .Net product] produce Windows desktop software AND web-enabled code (ASP.Net). The "market" as such is moving toward this platform, however to say that it is completely replacing what you can do in VB6 yet is a stretch.
In my particular case I am the developer responsible for maintaining the business-rules code in our product. (A large time-and-attendance system with thousands of clients). Much of our code has been "ported" over to the .Net platform (including my rules engine) - however much of it has not. The maintenance program used to configure this monster is a big VB6 program. While we may some day port it to .Net - it isn't going to be done as long as it remains a Windows desktop program. There just isn't any point in rewriting a program that's 50,000 lines of VB6 code in .Net just to re-present it as a .Net desktop program. If we decide we want it to present itself as a web-based program at some point then I'll rewrite it in VB.Net - but not until then.
What I am doing is simply learning to use .Net a bit at a time while I continue to work with VB6. Anything that already exists in VB6 (of substance, anyway) is not being ported until and IF a web presence is required of it; it just doesn't make sense to "re-platform" code that took 10 years to write just because .Net exists.
Make sense?
-Max :D
Which one would you recommend to learn vB.net or VB6?
while this has been discussed ad nauseam on this forum, the general feeling is that unless you really have a good reason to stay with VB6, learn VB.NET (if you have any VB exposure) or C#.NET (if exposed to any other language).Quote:
Originally Posted by freeappleipodtouch
-tg
Yeah, even considering what I said about VB6 above - if you're coming into this from scratch and are only going to use one of them then I'd agree that VB.Net should be the direction to go. The learning curve is going to be a bit steeper but it's still best to make an entry at .Net since that will be the supported technology in the future.Quote:
Originally Posted by techgnome
However if you're planning to stay within the Windows Desktop (as some of us "old dogs" are) then VB6 is still an excellent platform to work with.
-Max
Some of us "old dogs" would rather learn a new trick and go chase cars that sit up on the porch and lament the changing of the seasons....Quote:
Originally Posted by Max Peck
<rant>
As for those that are griping about dropping support for VB6.... call some one who cares. We've known FOR YEARS that support would go away... attitudes like that would have MS still supporting VB3/4 and Windows 3/3.1.... get over it. Seriously. Besides, just because MS isn't supporting it, doesn't mean you have to stop using it. It just means no more service packs. It means that I have the opportunity to move my career forward and learn new cool stuff I couldn't do before.
Old salt VB6'ers are starting to remind me of old sat COBOLers from the 90's lamenting the passing of COBOL, p!$$ing and moaning, "I don't wanna change."
Quite honestly, I'm getting sick and tired of hearing it.
</rant>
-tg
Aww stick it in your ear. I didn't say I wasn't learning - if you read my posts you see that I use *both*.Quote:
Originally Posted by techgnome
Smart-ass kid. You don't know the definition of "tired". The likes of you are a dime-a-dozen.
-Max
If in terms of job opportunities C# over vb.net to be honest. If starting out go .net right off the bat, vb6 is sunlet technology.Quote:
Originally Posted by freeappleipodtouch
Just wonder what was that supposed to mean? :confused:Quote:
Originally Posted by Max Peck
VB.Net and C# both offer superb environment for developing very rich desktop apps so why would you have to stick with 10+ years old technology?
Huh... "kid" huh? ..... haven't been called that in a looooooong time. For the record... the rant wasn't aimed at you... just the old dog comment.... the rant was sparked by another post in this thread...Quote:
Originally Posted by Max Peck
"tired" maybe, maybe not.... how about "sleepy"? Works for me.
-tg
(sorry Max, I actually read it that way the first time, so I thought I'd share it).Quote:
Originally Posted by Max Peck
If you know VB6, and don't have any pressing reason to change, then don't. On the other hand, if you do change, it is unlikely that you will regret it.