VB6 is a god!!
-
So with the suggestion that Windows 9 will be released this summer, the clock is ticking! ;P
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
I do hope that it does get killed off then :-D
Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
-
Ok - I don't actually believe the statement in the title. But it got your attention and gives you a far more appropriate venue for the puerile comments than Quick Answers or by posting fake answers to questions just to take the p**s. Yes - VB6 is outdated. Yes - VB6 is no longer supported However, Yes - There are still billions of lines of VB6 code still being using in Production systems across the world No! - We cannot just wave a magic wand and convert it all in a single stroke (and test it thoroughly by the way!) . One of the reasons being that there are fewer and fewer developers who will admit to knowing anything about VB6 and people are actively discouraged from finding anything out. Large, Medium and Small companies have kept VB6 (and even earlier tech) going for as long as they can simply because the stuff is already there, it works, it's already tested, it's already been proven, it's a major major investment in time and money to start converting it and doing all of that re-testing. Or perhaps you would like the large banking organisation I work for to just dive in and replace all of their VB6 code with "the latest technologies" ... hey - how about we do that each time a new technology comes a-knocking? Yeah, right! You don't mind some of your money going missing in the meantime I guess? So there will occasionally be questions in CP about VB6. Real questions about real problems (not homework or please do my work for me type questions) and re-writing the entire program/suite/enterprise will not be an option for that OP. So if you don't like VB6, know nothing about VB6, don't want to help the OP or just want to be sarcastic, then butt out of those questions and come here and have a go at me instead. Rant over. http://msdn.microsoft.com/en-us/magazine/jj133813.aspx[^]
-
according to this it can under WOW (now need to check what this is) http://msdn.microsoft.com/en-us/vstudio/ms788708.aspx[^]
Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
-
WOW is basically an emulator ... and you know what they say about emulation ... "Emulation is like masturbation - do it for long enough and you begin to think it's just like the real thing" :laugh:
:laugh: :thumbsup:
Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
-
Ah, VB6 sucks anyway. Ok, I go and play hide.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Do not feed the troll ! - Common proverb
sucking is good.
-
Ok - I don't actually believe the statement in the title. But it got your attention and gives you a far more appropriate venue for the puerile comments than Quick Answers or by posting fake answers to questions just to take the p**s. Yes - VB6 is outdated. Yes - VB6 is no longer supported However, Yes - There are still billions of lines of VB6 code still being using in Production systems across the world No! - We cannot just wave a magic wand and convert it all in a single stroke (and test it thoroughly by the way!) . One of the reasons being that there are fewer and fewer developers who will admit to knowing anything about VB6 and people are actively discouraged from finding anything out. Large, Medium and Small companies have kept VB6 (and even earlier tech) going for as long as they can simply because the stuff is already there, it works, it's already tested, it's already been proven, it's a major major investment in time and money to start converting it and doing all of that re-testing. Or perhaps you would like the large banking organisation I work for to just dive in and replace all of their VB6 code with "the latest technologies" ... hey - how about we do that each time a new technology comes a-knocking? Yeah, right! You don't mind some of your money going missing in the meantime I guess? So there will occasionally be questions in CP about VB6. Real questions about real problems (not homework or please do my work for me type questions) and re-writing the entire program/suite/enterprise will not be an option for that OP. So if you don't like VB6, know nothing about VB6, don't want to help the OP or just want to be sarcastic, then butt out of those questions and come here and have a go at me instead. Rant over. http://msdn.microsoft.com/en-us/magazine/jj133813.aspx[^]
If you want to write a two-tier app with a pleasant GUI and backed by (say) SQL Server, VB6 could still do a useful job today but the writing is on the wall. As I enter my dotage I'll happily shuffle around any company that still has some VB6 that wants maintaining, as an old friend of mine said "If they pay me, I'll code in anything". And since I do have a lot of VB6 (and 1, 2, 3, 4, 5 and DOS) experience I'll try to use that to help people who are still supporting systems using it. I may offer some guidance that it is time to move on but I see this as being like taking my car to the garage. I know my mechanic well enough that he'll tell me when the work required makes it uneconomical to fix, he won't tell me to change the car when the wiper blades are worn out.
-
Ok - I don't actually believe the statement in the title. But it got your attention and gives you a far more appropriate venue for the puerile comments than Quick Answers or by posting fake answers to questions just to take the p**s. Yes - VB6 is outdated. Yes - VB6 is no longer supported However, Yes - There are still billions of lines of VB6 code still being using in Production systems across the world No! - We cannot just wave a magic wand and convert it all in a single stroke (and test it thoroughly by the way!) . One of the reasons being that there are fewer and fewer developers who will admit to knowing anything about VB6 and people are actively discouraged from finding anything out. Large, Medium and Small companies have kept VB6 (and even earlier tech) going for as long as they can simply because the stuff is already there, it works, it's already tested, it's already been proven, it's a major major investment in time and money to start converting it and doing all of that re-testing. Or perhaps you would like the large banking organisation I work for to just dive in and replace all of their VB6 code with "the latest technologies" ... hey - how about we do that each time a new technology comes a-knocking? Yeah, right! You don't mind some of your money going missing in the meantime I guess? So there will occasionally be questions in CP about VB6. Real questions about real problems (not homework or please do my work for me type questions) and re-writing the entire program/suite/enterprise will not be an option for that OP. So if you don't like VB6, know nothing about VB6, don't want to help the OP or just want to be sarcastic, then butt out of those questions and come here and have a go at me instead. Rant over. http://msdn.microsoft.com/en-us/magazine/jj133813.aspx[^]
CHill60 wrote:
VB6 is a god!!
To some extent, you are correct, as it will slowly fall into the annals of mythology over the coming years just like all the spaghetti monsters. On a positive note, at least one could get vb6 to do something constructive.
I wasn't, now I am, then I won't be anymore.
-
reilly96 wrote:
I don't think VB6 will run on 64 bit systems
False! VB6 apps run just fine on Win8 64 bit. Our main software applications are VB6, and I still work in it everyday. We are using .NET for new projects and will rewrite everything. The fact that VB6 runs flawlessly on Win8 buys me another 4-5 years to get it done. :)
"Go forth into the source" - Neal Morse
-
Ok - I don't actually believe the statement in the title. But it got your attention and gives you a far more appropriate venue for the puerile comments than Quick Answers or by posting fake answers to questions just to take the p**s. Yes - VB6 is outdated. Yes - VB6 is no longer supported However, Yes - There are still billions of lines of VB6 code still being using in Production systems across the world No! - We cannot just wave a magic wand and convert it all in a single stroke (and test it thoroughly by the way!) . One of the reasons being that there are fewer and fewer developers who will admit to knowing anything about VB6 and people are actively discouraged from finding anything out. Large, Medium and Small companies have kept VB6 (and even earlier tech) going for as long as they can simply because the stuff is already there, it works, it's already tested, it's already been proven, it's a major major investment in time and money to start converting it and doing all of that re-testing. Or perhaps you would like the large banking organisation I work for to just dive in and replace all of their VB6 code with "the latest technologies" ... hey - how about we do that each time a new technology comes a-knocking? Yeah, right! You don't mind some of your money going missing in the meantime I guess? So there will occasionally be questions in CP about VB6. Real questions about real problems (not homework or please do my work for me type questions) and re-writing the entire program/suite/enterprise will not be an option for that OP. So if you don't like VB6, know nothing about VB6, don't want to help the OP or just want to be sarcastic, then butt out of those questions and come here and have a go at me instead. Rant over. http://msdn.microsoft.com/en-us/magazine/jj133813.aspx[^]
It will be as dead as COBOL - I was told that COBOl was on the way out when I started in IT in 1985. Lots of people still make a living maintaining COBOL systems
It's well known that if all the cat videos and porn disappeared from the internet there would be only one site left and it would be called whereareallthecatvideosandporn.com
-
Ok - I don't actually believe the statement in the title. But it got your attention and gives you a far more appropriate venue for the puerile comments than Quick Answers or by posting fake answers to questions just to take the p**s. Yes - VB6 is outdated. Yes - VB6 is no longer supported However, Yes - There are still billions of lines of VB6 code still being using in Production systems across the world No! - We cannot just wave a magic wand and convert it all in a single stroke (and test it thoroughly by the way!) . One of the reasons being that there are fewer and fewer developers who will admit to knowing anything about VB6 and people are actively discouraged from finding anything out. Large, Medium and Small companies have kept VB6 (and even earlier tech) going for as long as they can simply because the stuff is already there, it works, it's already tested, it's already been proven, it's a major major investment in time and money to start converting it and doing all of that re-testing. Or perhaps you would like the large banking organisation I work for to just dive in and replace all of their VB6 code with "the latest technologies" ... hey - how about we do that each time a new technology comes a-knocking? Yeah, right! You don't mind some of your money going missing in the meantime I guess? So there will occasionally be questions in CP about VB6. Real questions about real problems (not homework or please do my work for me type questions) and re-writing the entire program/suite/enterprise will not be an option for that OP. So if you don't like VB6, know nothing about VB6, don't want to help the OP or just want to be sarcastic, then butt out of those questions and come here and have a go at me instead. Rant over. http://msdn.microsoft.com/en-us/magazine/jj133813.aspx[^]
CHill60 wrote:
There are still billions of lines of VB6 code still being using in Production systems across the world
How much Cobol? How much Fortran? How much Pascal?
CHill60 wrote:
Large, Medium and Small companies have kept VB6 (and even earlier tech) going for as long as they can simply because the stuff is already there, it works, it's already tested, it's already been proven, it's a major major investment in time and money to start converting it and doing all of that re-testing.
To be fair "tested" in this context means - "it works in production". Versus, for example a extensive and complete testing suite.
CHill60 wrote:
work for to just dive in and replace all of their VB6 code with "the latest technologies" ... hey - how about we do that each time a new technology comes a-knocking? Yeah, right! You don't mind some of your money going missing in the meantime I guess?
The banks absolutely do not care if my money goes missing. What they care about is if their money goes missing. This is why, for example, credit cards these days have so many 'fraud' checks. They do nothing to protect the consumer because the consumer's credit cards are already completely protected from loss (maximum of $50.) What they do is protect the bank's losses. But other than that no business should upgrade to every new technology. But businesses especially large ones should have some concept of architecture which includes evaluating new technologies for inclusion. Across the entire business. And banks don't do that. They often have divisions that not only do not coordinate their development but have absolutely no idea that the other divisions even exist. Hiring and management is often at the highest levels (perhaps always) handled by financial officers who do not have any experience with development. And there is no emphasis on looking for solutions that increase the quality of development but always an emphasis on reducing cost.
-
Ok - I don't actually believe the statement in the title. But it got your attention and gives you a far more appropriate venue for the puerile comments than Quick Answers or by posting fake answers to questions just to take the p**s. Yes - VB6 is outdated. Yes - VB6 is no longer supported However, Yes - There are still billions of lines of VB6 code still being using in Production systems across the world No! - We cannot just wave a magic wand and convert it all in a single stroke (and test it thoroughly by the way!) . One of the reasons being that there are fewer and fewer developers who will admit to knowing anything about VB6 and people are actively discouraged from finding anything out. Large, Medium and Small companies have kept VB6 (and even earlier tech) going for as long as they can simply because the stuff is already there, it works, it's already tested, it's already been proven, it's a major major investment in time and money to start converting it and doing all of that re-testing. Or perhaps you would like the large banking organisation I work for to just dive in and replace all of their VB6 code with "the latest technologies" ... hey - how about we do that each time a new technology comes a-knocking? Yeah, right! You don't mind some of your money going missing in the meantime I guess? So there will occasionally be questions in CP about VB6. Real questions about real problems (not homework or please do my work for me type questions) and re-writing the entire program/suite/enterprise will not be an option for that OP. So if you don't like VB6, know nothing about VB6, don't want to help the OP or just want to be sarcastic, then butt out of those questions and come here and have a go at me instead. Rant over. http://msdn.microsoft.com/en-us/magazine/jj133813.aspx[^]
Honestly, this shouldn't need to be in the Soapbox.
"The ones who care enough to do it right care too much to compromise." Matthew Faithfull
-
Honestly, this shouldn't need to be in the Soapbox.
"The ones who care enough to do it right care too much to compromise." Matthew Faithfull
-
Ok - I don't actually believe the statement in the title. But it got your attention and gives you a far more appropriate venue for the puerile comments than Quick Answers or by posting fake answers to questions just to take the p**s. Yes - VB6 is outdated. Yes - VB6 is no longer supported However, Yes - There are still billions of lines of VB6 code still being using in Production systems across the world No! - We cannot just wave a magic wand and convert it all in a single stroke (and test it thoroughly by the way!) . One of the reasons being that there are fewer and fewer developers who will admit to knowing anything about VB6 and people are actively discouraged from finding anything out. Large, Medium and Small companies have kept VB6 (and even earlier tech) going for as long as they can simply because the stuff is already there, it works, it's already tested, it's already been proven, it's a major major investment in time and money to start converting it and doing all of that re-testing. Or perhaps you would like the large banking organisation I work for to just dive in and replace all of their VB6 code with "the latest technologies" ... hey - how about we do that each time a new technology comes a-knocking? Yeah, right! You don't mind some of your money going missing in the meantime I guess? So there will occasionally be questions in CP about VB6. Real questions about real problems (not homework or please do my work for me type questions) and re-writing the entire program/suite/enterprise will not be an option for that OP. So if you don't like VB6, know nothing about VB6, don't want to help the OP or just want to be sarcastic, then butt out of those questions and come here and have a go at me instead. Rant over. http://msdn.microsoft.com/en-us/magazine/jj133813.aspx[^]
This post is about VB6, I better downvote it... ;p Seriously though, we still do VB6 from time to time because that's what some of our customers still use. Although management announced we will not be supporting it anymore after 2015. The reason being that we simply cannot get it to work anymore on our machines (we run some virtual machines to edit VB6 software), but also because we don't have the knowledge anymore. Some of us (not me) still know some VB6 from way back when, but if you only get to do it once a year looking for that function or structure that could help you out takes way longer than it should...
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
Ok - I don't actually believe the statement in the title. But it got your attention and gives you a far more appropriate venue for the puerile comments than Quick Answers or by posting fake answers to questions just to take the p**s. Yes - VB6 is outdated. Yes - VB6 is no longer supported However, Yes - There are still billions of lines of VB6 code still being using in Production systems across the world No! - We cannot just wave a magic wand and convert it all in a single stroke (and test it thoroughly by the way!) . One of the reasons being that there are fewer and fewer developers who will admit to knowing anything about VB6 and people are actively discouraged from finding anything out. Large, Medium and Small companies have kept VB6 (and even earlier tech) going for as long as they can simply because the stuff is already there, it works, it's already tested, it's already been proven, it's a major major investment in time and money to start converting it and doing all of that re-testing. Or perhaps you would like the large banking organisation I work for to just dive in and replace all of their VB6 code with "the latest technologies" ... hey - how about we do that each time a new technology comes a-knocking? Yeah, right! You don't mind some of your money going missing in the meantime I guess? So there will occasionally be questions in CP about VB6. Real questions about real problems (not homework or please do my work for me type questions) and re-writing the entire program/suite/enterprise will not be an option for that OP. So if you don't like VB6, know nothing about VB6, don't want to help the OP or just want to be sarcastic, then butt out of those questions and come here and have a go at me instead. Rant over. http://msdn.microsoft.com/en-us/magazine/jj133813.aspx[^]
CHill60 wrote:
Rant over.
The reasons why I keep pointing it out are valid;
- VB6 is no longer for sale, meaning there'll be just a few remaining active licenses.
- One who does not migrate while it is still an option will be COBOL'ed
- People with an emotional attachment to the language do not rationally think about the fact that they're writing in a dead language. VB.NET isn't "much more" complicated.
- Posts like yours prove that the language still has support. Whoopie - but that means that YOU will be answering these questions in the future and doing the migrations, not me.
- It's not "news" - VB6 has been killed a decade ago. A speech to keep supporting it is more than a decade too late.
As for the large banks; I know that there are some large companies who depend on their outdated and unsafe VB6 solutions. I can also guess whose balls will be on the plate if anything goes wrong.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
-
I completely agree. I just got a little fed up with some people hijacking OPs genuine questions/problems involving VB6 just to have a rant, and sometimes being rather rude. I'd rather they had a go at me here so we can get on the point of QA :sigh:
For a number of years we got question in the forums asking for VB6 support on projects that were just starting, they deserved a rant to move the project to a supported platform. I have not seen any of these for some time :) I still think any large organisation needs a strategy to move to supported platforms! Still you should not be getting flack for supporting legacy crap but if it is broke then it needs migrating - yeah I know, broken wipers != new car but some of the requests are for adding new features!
Never underestimate the power of human stupidity RAH
