Printable View
Hi everyone. I'm new to the forum and I'm seeking guidance on deciding which direction to turn next. I have been programming VB6 for quite some time now. When VB.NET first came out in beta I was deep into a large VB6 project that I could not change to VB.NET. Now I want to learn something new and think I want to go for VB 2005. Can you please enlighten me? Is 2005 the way to go? Or should I wait for VB 2008? Thanks for your input.
VB 2005 IS the latest version of VB .Net.
Visual Basic 2005 Express Edition can be downloaded for free from MSDN , and I really think you should do that since .Net is the way to go and 2005 is the latest you can get at this point.
Go to 2005. I never heard of 2008 coming out before, but if it does, I won't expect much change in code. Start 2005 and by the time 2008 comes out, you'll be ready to go. :)
Never heard of VB 2008-how certain are you that the next version will be out by then? How willing are you to wait if it's late?
Interestingly, I read today that MS will support VB6 & VB05 in Wista, but not VB03 or any earlier versions of VB.Net. (Actually I believe the statement referred to all .Net languages, but I only really remember about VB.)
VB 6 is only supported with the extended support until 2008 and then its completely dead.
XP's mainstream support will be ending soon as MS only supports OS' for a 5 year standard period.
The next version of VS.NET is currently code named "Orcas" as can be read on the ms blogs. Its going to be coming out on Beta 1 soon but still about a year out from public release I would say. So during the mean time you can learn the FW as there will be improvements and code depreciations which shouldnt stop you from learning .NET completely.
Dear Rob,
So VB will not effectivly work on Vista FlatForm.How about the VBA programms.
What do you mean "flat form"?
VB 6 does run on Vista nad the core runtimes are supported. I have it installed and only minor issues have arisen so far but not big deal.
What do you mean "after 2008 VB6 will be completely dead"? Are you referring to the fact that MS will not provide support for it any longer? Or are you hinting at the fact that the VB6 runtimes may not be shipped with the OS anymore?Quote:
Originally Posted by RobDog888
Honestly, I couldn't care less about MS support (I have never asked for it in my life), whereas having to ship all of the VB runtimes with my applications would be a real headache.
Thanks to you all for your input. Based on the info you've provided I just bought VS 2005 Pro and have registered in an online course for VB 2005, to start next week. And I apologize for my comment regarding waiting for VB 2008. I was joking because of the way MS seems to come out with a new technology to replace the old one that I'm finally starting to get (fairly) good at. I figure that by the time I get comfortable with VB 2005, they'll replace it with something new. Thanks. :thumb:
I mean that MS will not have any extended (paid) support for it. The next OS version will not have any of the VB 6 runtimes and possibly may not be able to run them.
@OddMan, but still even when it does get replaced it wont be a drastic change so allot of what you will be learning with 2005 will still apply in Orcas.
Did MS say that? If they did, where can I read it?Quote:
Originally Posted by RobDog888
I read it recently somewhere on the MS site when researching VB 6 on Vista.
I assume that the next version of the OS will break compatibility with 32-bit software, otherwise I can't see any reason why the VB6 runtimes may not run.Quote:
Originally Posted by RobDog888
If MS made such a choice, they may just shoot themselves in the foot: the amount of 32-bit software in circulation is just countless. Even under Vista, the majority of developers are still going to target the 32-bit unmanaged kernel (how many customers of yours have asked for 64-bit software so far?).
I think Linux fans can't wait for MS to make such a mistake.
I dont think they will drop 32 bit as it may be more of a reason that VB 6 is already almost 10 years old. By the time the next OS comes out VB 6 will be around 15 years old. Why support something that is that old? Also, they probably want to have the main apps be .net and C++ etc. Anything other then VB 6.
Basically, you are saying that they are not going to break compatibility with any 32 bit software developed with any programming language except VB6. Once again, the only tools not to be compatible with Windows are those produced by MS! So, this is one more good reason to switch to alternative development tools such as Delphi, REALbasic etc. How can people rely on MS products again? Sick world...Quote:
Originally Posted by RobDog888
No thats not what I am saying. I am saying that its my understanding that VB 6 will not be supported on the next OS. Nothing about 32 bit or not, just VB 6 by itself. Show MS still support QBasic on Vista perhaps as the logic you are suggesting about keeping old obsolite technology alive?
Sorry, but to me it sounds like six of one and half a dozen of the other. VB6 (i.e. MS tool) will not be supported anymore, whereas applications developed in Delphi, REALbasic etc. will continue to work because they don't need the MS runtimes. Honestly, I think MS should have made a little effort and continued to support VB6. That way they would have sent a very effective message to their customers: buy MS products and you will never be left alone. On the contrary, it looks like VB6 users have just been abandoned. If you want to produce umanaged code, C++ is the only tool that MS offers you, as far as I know. And C++ is far more complex than VB6.Quote:
Originally Posted by RobDog888
There is a difference between a DOS based programming language and a Windows based one. VB6 allows you to develop professional applications targeting the latest versions of the MS OS. And you can hardly distinguish an executable developed in .NET from one developed in VB6. QBasic rests on a GUI that clearly belongs to the past. In other words, QBasic is obsolete, VB6 is not.Quote:
Originally Posted by RobDog888
I think you are overreacting a bit. We are just going by what MS almost did with VB 6 and Vista. Now stating that even after extending the support for VB 6 to 2008 it leaves little question about VB 6's future. Are they going to drop it? No one really will be able to definately say. So until the next OS is out in a CTP or Beta 1, we shouldnt start worring just yet. ;)
All this "should" and "shouldn't" is purely academic. Microsoft is a business and they will make their decisions based business outcomes. If they perceive that maintaining VB6 support is best for their business then that's what they'll do. If they perceive that getting developers to use their new tools is more beneficial to them then that's what they'll do, and their shareholders will say that that's what they should do.
IT moves forward at a very rapid rate, as we all know. How many people are using hardware or software that was created back when VB6 was released? Not many I'd say. Rapid change is a fact of life in IT. VB6 has had a good run but it's can't go on forever. It's easy for me to say because I don't use VB6 but now is as good a time as any to end its life. For those who want to keep using it there's never going to be a good time, but it cannot be supported forever.
IT companies are not warm and fuzzy. They'll do what suits them. If Microsoft choose not to support VB6 then it is obsolete. You can still keep using something that's obsolete if you like, but noone has a responsibility to facilitate it.
And if you continue to use legacy technology then you are only limiting yourself as a developer and your marketability in the job market (or moving up in your current employment).
John made some good points and with everything already being said I think this thread has gone off topic long enough. ;)
Off topic for sure, but I *would* like to refute the claim that few people use old software. (I'm not as certain about hardware.) Few businesses replace old software with new "because it's new". If the old software works then they continue using it-check out the extent of use in 'dead' languages (both COBOL & C are still widely used, among others).
One of the strongest computer support adages I know is "If it ain't broke then don't fix it". I'll admit that the adage opposes progress, but so do most companies-at least when they're profitable. (It's a business contradiction: when a company's profitable they don't want to change things; when it's unprofitable they generally don't have the resources to significantly change things.)
Regarding VB6, I'll take your word-you undoubtedly are more tuned in to what M$ will do than I, but based on your statements in this thread you don't seem as tuned in to the wider business world.
I have worked for several companies (not small ones either) and yes, its true that companies dont like to spend money on software upgrades because its just a new version. What they ask is what is the new features and what would be the benefit from upgrading, ROI, etc. This is the wider business worlds thinking. You have your opinions and are entitled to them but this thread is resolved and yes its now going off topic. If you would like, a new thread in the general developer forum would be a more appropriate place to continue on with such topic like "do companies upgrading software and why" type of discussion. :)