I was just saw that VB is coming out with vb 2005. How is this going to be different that vb 6.0?
Printable View
I was just saw that VB is coming out with vb 2005. How is this going to be different that vb 6.0?
If you Google vb2005 features you'll find a bunch of information.
If everyone googled all day I guess we wouldn't need this forum huh?
vb 2005 is going to be a new version of vb.net not vb6
so the main differences between vb6 and vb 2005 will be the for the most part the same ones that seperate vb6 from vb.net
Looks like we have to join the .NET forum if we are going to upgrade ;-)
I'm planning to upgrade once it comes out. But i haven't decided if i want to stick with VB or move on to C#. I'll probably have to stick with VB at first just so my learning curve is a little easier, but once i get that under control I'd like to make the switch
That sounds like my plan, also. Although, I was wondering about rewriting everything using ASP and having it run like an Web app on the internal LAN.
Moved to General Developer.
Do you have any experience with prior versions of the .NET platform?Quote:
Originally Posted by Jnickrand
By the way, there is no such thing as VB2005. It is VS2005 which stands for Visual Studio and includes ASP.NET, VB.NET and C#.
VB.NET (any version) is as like VB6 as a Lamburgini is like a Chevy. They are, after all, both cars. They both have seats and a steering wheel and brakes and many other things in common.
But the reality is, they are nothing alike.
What are the strengths of re-writting an app in ASP?Quote:
Originally Posted by Pasvorto
VB.NET 2005 is not an upgrade from VB6 in any respect. They are two completely different languages and products. VB6 code will not run in VB.NET 2003 or 2005 without some kind of major conversion/rewritting. 2003 and 2005 are all about OOP where VB6 is not.
.NET is, like Hack put it, a 2006 Ferrari Enzio and VB6 is like a 1951 VW Bug with a 1300 cc engine. :D
Hey hey hey hey....back the car anology up...I said VB6 was like a Chevy...not a VW Bug. A '68 Chevy with .427 hemi ('course a 2006 Ferrari Enzio would beat the snot out of it, but it ain't no VW Bug! :D )Quote:
Originally Posted by RobDog888
:lol: Ok, well I could have used VB 6 as a bicycle and .NET as a motorcycle then. :)
Either way .NET is here to stay and is overtaking VB6 in the professional district. :D
It is overtaking VB in the corporate world, but I'm not seeing a whole lot of .NET products appearing in the market place in the commerical world (at least not in my target audience of large scale insurance companies.)Quote:
Originally Posted by RobDog888
We just hired two new VB6 programmers because the .NET version of our base products are not selling at all. But, we are picking new customers for our VB6 version, and maintaining good working relationships with our existing customer base.
(Raises hand up and waves... :wave: ) I need a good paying job :D
It will probably take some years for it to saturate the market but I have no doubts that it will.
I used to think .Net was hard and confusing since I used VB6, but since if tried VB2005, it is exteremly easy and it has alot more functions.
Hmmmm....
VB .NET has its advantages and disadvantages.
So rather than learn that Im gonna learn c and c++ first :P
.NET is all very nice but it does have a big overhead and sometimes its nice to get your fingers mucky with low-level stuff that .net tries to hide. :D
VB .NET doesn't have a steep learning curve especially if you know a bit of c and c++ and are pretty into vb6 (you'll know what vb6 limits are and then find vb .net's solutions for them)
It will when corporate programmers start churning out stuff in .NET that their management sees and likes.Quote:
Originally Posted by RobDog888
Once that happens, the same management folks will start looking at commerical products made with .NET
Do you really think I'm still a VB6 programmer out of choice?
Not hardly...but, as I said, our .NET version isn't selling so not only is there no need for my company to allow me to learn .NET, there is a strong need for me to stay with VB6. :(