none
Bring back Visual Basic 6.0 ! We all need it.

All replies

  •  I am sure if you do some google searching you can find a place to download it. However, that is like Bringing back black and white television.   :)
    Friday, January 17, 2014 12:41 PM
  • um, no
    Friday, January 17, 2014 12:48 PM
  • Can you describe what VB6 does that cannot be done with VB .NET ?

    Friday, January 17, 2014 2:51 PM
  • Hello,

    This will never happen, heck even thou Microsoft is committed to keeping VB.NET and C# features the same as much as possible VB.NET is (hopefully this is not taken the wrong way) losing audiences to C# thus this leaves no room for classic VB6 at all.

    This is not to say ignore VB.NET but it does indicate ignore VB6 unless you need to manage legacy projects which in this case you should have VB6 or search the web to purchase a copy of VB6.

    The only (seemingly) advantage for VB6 over VB.NET is that somethings seem to be easier to do yet when one needs to do more complex operations using VB6 one needs to write what I call crazy code that in many circles is known as "black-belt" coding. Jump to VB.NET and what was easy to do in VB6 when first learning VB.NET seems extremely complex. This complexity is welcome once you have spent time with VB.NET as now you have the freedom to be free of black-belt coding styles.  There are countless benefits to VB.NET over VB6 yet in the end you need to decide which is best for you. So if you want to use VB6 so be it but there is no way on this Earth will Microsoft bring back VB6, similarly this is like asking to bring back 8-track tapes :-)


    Please remember to mark the replies as answers if they help and unmark them if they provide no help, this will help others who are looking for solutions to the same or similar problem.

    Friday, January 17, 2014 3:07 PM
  • Please reconsider introducing VB6 to the market. It is needed by many.

    I know where you can get a copy of that.

    I saw a copy in the Smithsonian Natural History Museum in a display where a Neanderthal was using the CD as a fresnel lens to start a fire. It's still there IMO.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.

    Friday, January 17, 2014 3:09 PM
  • Please reconsider introducing VB6 to the market. It is needed by many.

    I know where you can get a copy of that.

    I saw a copy in the Smithsonian Natural History Museum in a display where a Neanderthal was using the CD as a fresnel lens to start a fire. It's still there IMO.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.


    What not on floppy disks :-)

    Please remember to mark the replies as answers if they help and unmark them if they provide no help, this will help others who are looking for solutions to the same or similar problem.

    Friday, January 17, 2014 3:25 PM
  • I think you are in the wrong forum. 

    However, VB6 is not even a dead horse it is a horse which has not even bones anymore.

    For instance the VB6 part made for Internet the IISClass was soon after the introduction retired because it was to complex to get it working with VB6 and in fact had to less possibilities.

    In my idea it came back as .Net but then in a much more usable way.

    In fact is asking for VB6 the same as asking: "Please close Internet and get rid of all those cell phones and other mobile devices".

    In my opinion as that has happened Microsoft can bring also VB6.


    Success
    Cor

    Friday, January 17, 2014 3:37 PM
  • I'd say it's most like saying:

    "Bring back Windows 3.11, we need it."  =P

    This thread should probably go to Off-Topic, but perhaps it also serves to remind people that VB6 should be retired and forgotten.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    Friday, January 17, 2014 4:20 PM
  • I'd say it's most like saying:

    "Bring back Windows 3.11, we need it."  =P

    This thread should probably go to Off-Topic, but perhaps it also serves to remind people that VB6 should be retired and forgotten.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"


    You should so sticky this thread reed and post a comment about why vb6 is not used anymore to show people how silly their questions sound. Especially when you look at how vb6 has not been updated in years as everyone else has pointed out. =P

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr


    • Edited by The Thinker Friday, January 17, 2014 6:06 PM
    Friday, January 17, 2014 6:05 PM
  • @TheThinker (and moderators), 

    I don't think it is a good idea to create a kind of war thread in this forum with make from this a sticky. Its serves nothing.

    We can have a lot of fun around it, but it serves nothing than frustration and that is not the purpose of this forum.

    As long as this in top that is enough, after that let it go.


    Success
    Cor

    Friday, January 17, 2014 6:57 PM
  • Bring out your dead...

    Paul ~~~~ Microsoft MVP (Visual Basic)

    Friday, January 17, 2014 7:03 PM
  • @The Thinker,

    LOL while I can certainly appreciate the sentiment, Cor is correct and that would be a step too far.

    @Paul,

    I feel happy!


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    Friday, January 17, 2014 7:34 PM
  • @The Thinker,

    LOL while I can certainly appreciate the sentiment, Cor is correct and that would be a step too far.

    @Paul,

    I feel happy!


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    Yes, I understand. Although its still funny to watch people bring these discussions up from time to time.

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr

    Friday, January 17, 2014 7:50 PM
  • Can you describe what VB6 does that cannot be done with VB .NET ?

    This CodeProject article will explain clearly why Visual Basic 6.0 is better than other programming languages:

    http://www.codeproject.com/Articles/710181/Visual-Basic-6-0-A-giant-more-powerful-than-ever

    This link will show you that VB6 has the smartest advanced opensource projects:

    https://www.facebook.com/MicrosoftVB

    ;)

    Wednesday, February 26, 2014 3:42 PM
  • I'd say it's most like saying:

    "Bring back Windows 3.11, we need it."  =P

    This thread should probably go to Off-Topic, but perhaps it also serves to remind people that VB6 should be retired and forgotten.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    You are behind with the news and you do not know what you say! MPV or not MPV, you lose credibility because you talk like that of Visual Basic 6.0! This CodeProject article will explain clearly why Visual Basic 6.0 is better and way faster than other programming languages:

    http://www.codeproject.com/Articles/710181/Visual-Basic-6-0-A-giant-more-powerful-than-ever

    This link will show you that VB6 has the smartest advanced opensource projects:

    https://www.facebook.com/MicrosoftVB

    Wednesday, February 26, 2014 3:52 PM
  • Can you describe what VB6 does that cannot be done with VB .NET ?

    This CodeProject article will explain clearly why Visual Basic 6.0 is better than other programming languages:

    http://www.codeproject.com/Articles/710181/Visual-Basic-6-0-A-giant-more-powerful-than-ever

    This link will show you that VB6 has the smartest advanced opensource projects:

    https://www.facebook.com/MicrosoftVB

    ;)


    The only problem between vb6 and vb.net is the usage of variants for specialized tasks which was removed in vb.net. Besides variants, other functionality is in vb.net that is not in vb6 you just need to know how to use it (it has a lot of math functions if you figure out the correct library to import). However, a lot of vb6 tasks and some functions from vb6 are still floating around in vb.net you only need to know how to use them. The biggest problem with vb6 is ease of learning and it was not necessarily an easy language to learn at times. One example is in vb6 you still need to dispose of objects but in most instances the dot net garbage collector takes care of this for you. Even in objective-c you have dynamic memory allocation and disposal for a project so this would be a step backwards to bring back the original vb6. I could go onto codeplex and instantly find anything I want in vb.net so why vb6? This includes data retrieval and specialized applications/libraries (their is everything from c++ to python to vb.net but hardly anything vb6 because its impractical right now). The biggest problem is that it is limited to x86 code right now and everything is going to 64-bit machines.

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr


    • Edited by The Thinker Wednesday, February 26, 2014 4:08 PM
    Wednesday, February 26, 2014 4:03 PM
  • Can you describe what VB6 does that cannot be done with VB .NET ?

    This CodeProject article will explain clearly why Visual Basic 6.0 is better than other programming languages:

    http://www.codeproject.com/Articles/710181/Visual-Basic-6-0-A-giant-more-powerful-than-ever

    This link will show you that VB6 has the smartest advanced opensource projects:

    https://www.facebook.com/MicrosoftVB

    ;)


    The only problem between vb6 and vb.net is the usage of variants for specialized tasks which was removed in vb.net. Besides variants, other functionality is in vb.net that is not in vb6 you just need to know how to use it (it has a lot of math functions if you figure out the correct library to import). However, a lot of vb6 tasks and some functions from vb6 are still floating around in vb.net you only need to know how to use them. The biggest problem with vb6 is ease of learning and it was not necessarily an easy language to learn at times. One example is in vb6 you still need to dispose of objects but in most instances the dot net garbage collector takes care of this for you. Even in objective-c you have dynamic memory allocation and disposal for a project so this would be a step backwards to bring back the original vb6. I could go onto codeplex and instantly find anything I want in vb.net so why vb6? This includes data retrieval and specialized applications/libraries (their is everything from c++ to python to vb.net but hardly anything vb6 because its impractical right now). The biggest problem is that it is limited to x86 code right now and everything is going to 64-bit machines.

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr



    I would also like to comment that the graph in that post Megan likes exactly like the vb.net graph. I hope the person that wrote that article knows that.

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr

    Wednesday, February 26, 2014 4:10 PM
  • I think you are in the wrong forum. 

    However, VB6 is not even a dead horse it is a horse which has not even bones anymore.

    For instance the VB6 part made for Internet the IISClass was soon after the introduction retired because it was to complex to get it working with VB6 and in fact had to less possibilities.

    In my idea it came back as .Net but then in a much more usable way.

    In fact is asking for VB6 the same as asking: "Please close Internet and get rid of all those cell phones and other mobile devices".

    In my opinion as that has happened Microsoft can bring also VB6.


    Success
    Cor

    The fact that you are not coherent in text, says a lot about how good you are at programming! The same six people comment with malice about Visual Basic 6.0 all over the internet without knowing anything about the VB6 subject ! Is a shame that you say that about VB6, as long as in 2014 is the most popular programming language!!

    What is the best programming language in the world ?!:

    VB6 on place 1: http://www.theranking.com/what-is-the-best-programming-language-in-the-world_r55229
    VB6 on place 2: http://www.theranking.com/what-is-the-best-programming-language-ever_r43672
    VB6 on place 2: http://www.theranking.com/best-programing-language-in-the-world_r36102

    Don't cheat yourself, VB6 is here to stay and will work on Win 9 !


    Wednesday, February 26, 2014 4:12 PM
  • I'd say it's most like saying:

    "Bring back Windows 3.11, we need it."  =P

    This thread should probably go to Off-Topic, but perhaps it also serves to remind people that VB6 should be retired and forgotten.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    You are behind with the news and you do not know what you say! MPV or not MPV, you lose credibility because you talk like that of Visual Basic 6.0! This CodeProject article will explain clearly why Visual Basic 6.0 is better and way faster than other programming languages:

    http://www.codeproject.com/Articles/710181/Visual-Basic-6-0-A-giant-more-powerful-than-ever

    This link will show you that VB6 has the smartest advanced opensource projects:

    https://www.facebook.com/MicrosoftVB

    There's almost more old people in the U.S. than young people. Maybe that's why there are so many more VB6 programmers around. You know how people get the older they get. Unable to accept change.

    I'm sure none of those programs at that codeproject link could be written using vb.net and work anywhere nearly as well as the ones written in VB6. :)

    Although a lot of the article at that link seems more of opinion necessarily than fact.

    Here's a link for you Megan.

     ArtinSoft’s Visual Basic Upgrade Companion (VBUC)

    Exciting Offer for You!

    Microsoft and ArtinSoft have partnered to offer a free VBUC license to you. The discount code below can be used to purchase a license that will allow you to migrate an application of up to 10,000 lines of VB6 code to VB.NET or C# for free. It can also be applied when purchasing a larger license.

    Download your copy today. Use the code MSDN for a free license for up to 10,000 lines of code!"


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.


    • Edited by Mr. Monkeyboy Wednesday, February 26, 2014 4:22 PM 5555
    Wednesday, February 26, 2014 4:12 PM
  • Hello,

    This will never happen, heck even thou Microsoft is committed to keeping VB.NET and C# features the same as much as possible VB.NET is (hopefully this is not taken the wrong way) losing audiences to C# thus this leaves no room for classic VB6 at all.

    This is not to say ignore VB.NET but it does indicate ignore VB6 unless you need to manage legacy projects which in this case you should have VB6 or search the web to purchase a copy of VB6.

    The only (seemingly) advantage for VB6 over VB.NET is that somethings seem to be easier to do yet when one needs to do more complex operations using VB6 one needs to write what I call crazy code that in many circles is known as "black-belt" coding. Jump to VB.NET and what was easy to do in VB6 when first learning VB.NET seems extremely complex. This complexity is welcome once you have spent time with VB.NET as now you have the freedom to be free of black-belt coding styles.  There are countless benefits to VB.NET over VB6 yet in the end you need to decide which is best for you. So if you want to use VB6 so be it but there is no way on this Earth will Microsoft bring back VB6, similarly this is like asking to bring back 8-track tapes :-)


    Please remember to mark the replies as answers if they help and unmark them if they provide no help, this will help others who are looking for solutions to the same or similar problem.

    What do you know about Microsoft and to what Microsoft is committed to ?! VB. NET has had 12 years to overthrow Visual Basic 6.0 and failed! Ignore !? There are hundreds of thousands of VB6 programmers, who are you to dictate the "room"?! The majority of VB6 programmers are black-belt coders !

    In fact chances are quite high that Visual Basic 6.0 will return in a new form (a modern version)

    Wednesday, February 26, 2014 4:32 PM
  • Please reconsider introducing VB6 to the market. It is needed by many.

    I know where you can get a copy of that.

    I saw a copy in the Smithsonian Natural History Museum in a display where a Neanderthal was using the CD as a fresnel lens to start a fire. It's still there IMO.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.

    Yes, but Neanderthal has had 30% more brain :)
    Wednesday, February 26, 2014 4:34 PM
  • um, no
    You are as smart as your short words !
    Wednesday, February 26, 2014 4:35 PM
  • If you talking about the program language itself, I agree with you. Mostly there is spoken about the product in combination with the Com part (In fact VB1998).

    Yes the language is very good, but that has since version 6 very few changes. It are much less between VB6 and VB12 then there were between VB1 and VB6. A major change between VB6 and VB7 is that in the later version passing goes in the same way for functions as for subs which was in versions before VB7 very weird. But that is for me the most important one. Others are just very minors. 

    On the other hand there are endless additions in the language since version 6 and 12, but the syntax is not broken anymore in no way since version 7. 

    However, many persons cannot see what is in a designer product and what is a program language. They look to it like to a product as MS Word and Excel. For instance the VB6 Visual Studio designer had the possibility to create arrays of special controls for Windows Forms. That is not anymore in the Visual Studio designer, Windows Forms is just a small part of the product. However, in VB we can now create endless kinds of control array, control collections, control list and what is more, not only from one type  but mixed in any way we want.

    I don't tell how good you are in programming, but I know about VB6 programming, and also know that in 2002 I've endless times seen written by persons who had very long experience (high qualified VB6 programmers) with all versions of VB that they were hoping never to have to program with the product VB6 again.

    Although there were others who could not make the step to OOP and wanted to go on in a scripting kind of programming. They had another opinion, and blamed that they could not understand it to Microsoft.

     


    Success
    Cor


    • Edited by Cor Ligthert Wednesday, February 26, 2014 4:38 PM
    Wednesday, February 26, 2014 4:36 PM
  • I'd say it's most like saying:

    "Bring back Windows 3.11, we need it."  =P

    This thread should probably go to Off-Topic, but perhaps it also serves to remind people that VB6 should be retired and forgotten.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    You are behind with the news and you do not know what you say! MPV or not MPV, you lose credibility because you talk like that of Visual Basic 6.0! This CodeProject article will explain clearly why Visual Basic 6.0 is better and way faster than other programming languages:

    http://www.codeproject.com/Articles/710181/Visual-Basic-6-0-A-giant-more-powerful-than-ever

    This link will show you that VB6 has the smartest advanced opensource projects:

    https://www.facebook.com/MicrosoftVB

    There's almost more old people in the U.S. than young people. Maybe that's why there are so many more VB6 programmers around. You know how people get the older they get. Unable to accept change.

    I'm sure none of those programs at that codeproject link could be written using vb.net and work anywhere nearly as well as the ones written in VB6. :)

    Although a lot of the article at that link seems more of opinion necessarily than fact.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.

    That's true because implementation and fact are far different from speculation from weird websites that are biased. Megan, I will refer to a vb6 teacher I had who would use vb6 over and over again (an older version) but that does not mean he was correct and that it would work on new machines. This is the reason people upgrade to vb.net because support died a long time ago otherwise people would be using it now. You could open source vb6 but that requires "support" even from a developer community and in that respect even mono has them beat. Go ask any indie game developer about what programming languages they use and mono is probably one of the top programming language environments used besides visual studio (mono has vb.net and c# of its own). This may even be more true since Microsoft stated they officially support unity which uses it: http://news.xbox.com/2013/06/xbox-one-unity-announcement and http://unity3d.com/company/public-relations/news/unity-announces-strategic-collaboration-microsoft.  You could never use vb6 on the xbox 360 or xbox one because of possible problems with developing a perfect application like C# or C++ when developed properly has major performance boosts. Which is higher then both visual basic or vb.net at all:  http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html or vb6 or vb.net are not even listed on one blog: http://blog.codeeval.com/codeevalblog/2014#.Uw4WtxOYaM8 and another uses multiple sources which state it is not even on the list at all: http://www.slideshare.net/lyndadotcom/top-10-programming-languages-to-know-in-2014. Although this maybe misleading because general C# and vb.net code can be re-used or cross-coded with C# improving functionality and one coder may use vb.net. This is a simple google query language of most popular programming language's of 2014 and in one vb6 is barely 2-3 spaces above vb.net in usage. However, the results could all be biased because it is only about a 1/3 of the way through 2014 and impossible to tell unless they are forecasting which would make the results incomplete.


    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr









    • Edited by The Thinker Wednesday, February 26, 2014 4:58 PM
    Wednesday, February 26, 2014 4:44 PM
  • Can you describe what VB6 does that cannot be done with VB .NET ?

    This CodeProject article will explain clearly why Visual Basic 6.0 is better than other programming languages:

    http://www.codeproject.com/Articles/710181/Visual-Basic-6-0-A-giant-more-powerful-than-ever

    This link will show you that VB6 has the smartest advanced opensource projects:

    https://www.facebook.com/MicrosoftVB

    ;)

    Your reply does not address what I asked. Many years ago I used 6805 assembly language, and then 68000 assembly. It is the most efficient way to create a program, but it's no longer very feasible to use.

    I do remember that in VB6 you can declare API functions using the "As Any" clause, which .NET does not allow, but that was a bad idea to start with. Again, what can be done in VB6 that .NET is unable to do ?

    Wednesday, February 26, 2014 4:56 PM
  • I'd say it's most like saying:

    "Bring back Windows 3.11, we need it."  =P

    This thread should probably go to Off-Topic, but perhaps it also serves to remind people that VB6 should be retired and forgotten.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    You are behind with the news and you do not know what you say! MPV or not MPV, you lose credibility because you talk like that of Visual Basic 6.0! This CodeProject article will explain clearly why Visual Basic 6.0 is better and way faster than other programming languages:

    http://www.codeproject.com/Articles/710181/Visual-Basic-6-0-A-giant-more-powerful-than-ever

    This link will show you that VB6 has the smartest advanced opensource projects:

    https://www.facebook.com/MicrosoftVB

    There's almost more old people in the U.S. than young people. Maybe that's why there are so many more VB6 programmers around. You know how people get the older they get. Unable to accept change.

    I'm sure none of those programs at that codeproject link could be written using vb.net and work anywhere nearly as well as the ones written in VB6. :)

    Although a lot of the article at that link seems more of opinion necessarily than fact.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.

    That's true because implementation and fact are far different from speculation from weird websites that are biased. Megan, I will refer to a vb6 teacher I had who would use vb6 over and over again (an older version) but that does not mean he was correct and that it would work on new machines. This is the reason people upgrade to vb.net because support died a long time ago otherwise people would be using it now. You could open source vb6 but that requires "support" even from a developer community and in that respect even mono has them beat. Go ask any indie game developer about what programming languages they use and mono is probably one of the top programming language environments used besides visual studio (mono has vb.net and c# of its own). This may even be more true since Microsoft stated they officially support unity which uses it: http://news.xbox.com/2013/06/xbox-one-unity-announcement and http://unity3d.com/company/public-relations/news/unity-announces-strategic-collaboration-microsoft.  You could never use vb6 on the xbox 360 or xbox one because of possible problems with developing a perfect application like C# or C++ when developed properly has major performance boosts. Which is higher then both visual basic or vb.net at all:  http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html or vb6 or vb.net are not even listed on one blog: http://blog.codeeval.com/codeevalblog/2014#.Uw4WtxOYaM8 and another uses multiple sources which state it is not even on the list at all: http://www.slideshare.net/lyndadotcom/top-10-programming-languages-to-know-in-2014. Although this maybe misleading because general C# and vb.net code can be re-used or cross-coded with C# improving functionality and one coder may use vb.net. This is a simple google query language of most popular programming language's of 2014 and in one vb6 is barely 2-3 spaces above vb.net in usage. However, the results could all be biased because it is only about a 1/3 of the way through 2014 and impossible to tell unless they are forecasting which would make the results incomplete.


    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr










    At best you could ask the developers using mono to throw in vb6 but they might laugh at you too. I dare you to do so because actual usage is far from actual implementation. Anymore it is becoming less feasible to implement vb6 on a platform because of it's actual support. I can be "fan" and "use" vb6 but that does not mean I use it for anything useful anymore or on an actual system. The author is clearly a very good vb6 fanboy but that does not mean his ideas can be implemented efficently.

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr




    • Edited by The Thinker Wednesday, February 26, 2014 5:16 PM
    Wednesday, February 26, 2014 5:04 PM
  • Can you describe what VB6 does that cannot be done with VB .NET ?

    This CodeProject article will explain clearly why Visual Basic 6.0 is better than other programming languages:

    http://www.codeproject.com/Articles/710181/Visual-Basic-6-0-A-giant-more-powerful-than-ever

    This link will show you that VB6 has the smartest advanced opensource projects:

    https://www.facebook.com/MicrosoftVB

    ;)

    Your reply does not address what I asked. Many years ago I used 6805 assembly language, and then 68000 assembly. It is the most efficient way to create a program, but it's no longer very feasible to use.

    I do remember that in VB6 you can declare API functions using the "As Any" clause, which .NET does not allow, but that was a bad idea to start with. Again, what can be done in VB6 that .NET is unable to do ?


    Devon, variant support in vb.net is poor because even C# has some support for it and the support vb.net has does not work for a project I am currently working on. Megan, most options from vb6 are available in vb.net (with a little bit of coding) and in visual studio 2012 and above working flawlessly.  I used to be grouchy coming into vb.net too from vb6. Once upon a time, I had a different username on this forum before I created a Gmail account and forgot my Hotmail account password and came in very grouchy to these forums. I stopped using my old account because I forgot my password and username.  Megan, try asking for variant support in vb.net and watch the vb.net usage increase 10 fold because that's one of the biggest pet peeve's is variant support (current support is poor) I can see.

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr


    • Edited by The Thinker Wednesday, February 26, 2014 5:13 PM
    Wednesday, February 26, 2014 5:12 PM
  • I'd say it's most like saying:

    "Bring back Windows 3.11, we need it."  =P

    This thread should probably go to Off-Topic, but perhaps it also serves to remind people that VB6 should be retired and forgotten.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    You are behind with the news and you do not know what you say! MPV or not MPV, you lose credibility because you talk like that of Visual Basic 6.0! This CodeProject article will explain clearly why Visual Basic 6.0 is better and way faster than other programming languages:

    http://www.codeproject.com/Articles/710181/Visual-Basic-6-0-A-giant-more-powerful-than-ever

    This link will show you that VB6 has the smartest advanced opensource projects:

    https://www.facebook.com/MicrosoftVB

    There's almost more old people in the U.S. than young people. Maybe that's why there are so many more VB6 programmers around. You know how people get the older they get. Unable to accept change.

    I'm sure none of those programs at that codeproject link could be written using vb.net and work anywhere nearly as well as the ones written in VB6. :)



    "old people in the U.S." realy ?! :) Do I seem old to you ?! Most VB6 programmers (that I know of) are under 30 years old and they also know and work with Java, C++, ASM and other languages. The CodeProject article is based on facts alright!

    You make me laugh with your links :))))) I bought all Visual Studio packages out of curiosity and I went back to VB6! All VB6 programmers know the links that you have posted, all of them! :)
    Wednesday, February 26, 2014 5:13 PM
  • Ninguém está pedindo para a Microsoft voltar a vender os disquettes do VB6, não sejam idiotas. Estamos pedindo que ela abra o source code do VB6, e simplesmente adicione as funções de compilar para 64 bits, para Risc e para Metro. 

    Se isso parece ridículo, então liberem o source code como patrimônio da humanidade, e os dinossauros como eu que programavam em assembler de Z80 e de 8088 quando esses meninos que gostam de nos humilhar nem óvulos, eram, fazemos nós mesmos as mudanças necessárias.

    E finalmente, não façam nada, tanto faz. Quando a gente se cansar dessa conversa tola, ou tirarem a VBrun do windows, a gente descompila tudo e faz um novinho, open code free for all system operatiionals...

    Se a Microsoft acha que o source code do VB é lixo, dêem ele para os dinossauros.
    Porque uma hora um dos dinossauros se cansa de ser ofendido por esses moleques que mal sairam da fralda e nem sabem o que é um mnemônico, faz um shell novo para linux com cara de Modern Metro e acaba de vez com tudo isso, e aí vocês vão poder dizer quem estava errado ao pedir amigavelmente que o compilador seja atualizado. 


    Eugenio P. S. Canaan - ILT tecnologia - BR

    Wednesday, February 26, 2014 5:36 PM
  •  Do I seem old to you ?! 

    You reminds me to this woman, she knows also everything everybody needs.



    Success
    Cor

    Wednesday, February 26, 2014 5:36 PM
  •  Do I seem old to you ?! 

    You reminds me to this woman, she knows also everything everybody needs.



    Success
    Cor

    Cor, from my research it appears variant support is very poor in vb.net and I posted a suggestion for it on the visual studio connect improvement website. So if Microsoft listens or makes it so device code no longer uses variants and instead objects this will improve coding in vb.net a lot. It seems a lot of vb6 coders hate upgrading because their variant object will not upgrade in some instances and so they stick with vb6. Bring back the variant object can be the best move for vb.net to make (Its strictly a compatibility issue with devices that use the full variant data type and so the object data type does not work). 

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr

    Wednesday, February 26, 2014 5:52 PM
  •  Do I seem old to you ?! 

    You reminds me to this woman, she knows also everything everybody needs.

    So far, regarding VB6, you also have shown that you know everything everybody needs. What you think VB6 programmers need, and what VB6 programmers say they need are totally separate things :)
    Wednesday, February 26, 2014 6:05 PM
  • Option Strict Off and Option Explicit off gives you in fact back the variant.

    In C# the counterpart which is created to give in this in C# parity to VB.

    http://msdn.microsoft.com/en-us/library/dd264741.aspx

    Again and Again, VB.Net is the name from the product which contained VB7.0 in 2002. In 2003 the name changed to 2003 Net and after that it is not used anymore. However those for who the time stood still after the first year of the millennium change are going on keeping those names. 

    Dim X = "The Thinker" with all Options Off gives a kind of Variant, although, what is already written in this thread, gives not the dummy way of use with the Com objects. 

    I remember another major change between VB6, the mnemonic names of value types shifted to a more common use. The 8 bit was gone and integer became the 32bit one like all processors in those days.


    Success
    Cor


    • Edited by Cor Ligthert Wednesday, February 26, 2014 6:10 PM
    Wednesday, February 26, 2014 6:07 PM
  • @The Thinker,

    LOL while I can certainly appreciate the sentiment, Cor is correct and that would be a step too far.

    @Paul,

    I feel happy!


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    Try not to pull down the reputation of all MVP's. Your "sentiment" regarding Visual Basic 6.0 is irrelevant and affects your credibility.
    Wednesday, February 26, 2014 6:11 PM
  • Please reconsider introducing VB6 to the market. It is needed by many.

    I know where you can get a copy of that.

    I saw a copy in the Smithsonian Natural History Museum in a display where a Neanderthal was using the CD as a fresnel lens to start a fire. It's still there IMO.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.

    Yes, but Neanderthal has had 30% more brain :)

    I don't know what a Neanderthal did with 30% more brain. Not much it appears compared to non-Neanderthal. I've never seen a Neanderthal perform a time to climb record in an F-4 Phantom like my old man did back in the day as a USN test pilot. He's a genius also. Although Alzheimers is destroying him nowadays.

    You don't seem old. You do seem ignorant. Black-Belt coder? I doubt it. That's an opinion not a fact. You base it on your available experience and not reality.

    Now my old Tang Soo Do Moo Duk Kwan instructor was a Black Belt (7th degree way back when) and now he's the Grand Master. His name is Song Ki Pak.

    Don't try to fool others into believing what you want to be true which isn't necessarily so.

    Also too bad you're a red head cause female red heads only come in two types IMO. Attractive and the opposite. And IMO you ain't the first.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.


    • Edited by Mr. Monkeyboy Wednesday, February 26, 2014 6:22 PM 5555
    Wednesday, February 26, 2014 6:17 PM
  •  Do

     What you think VB6 programmers need, and what VB6 programmers say they need are totally separate things :)

    You tell VB6 is perfect. Perfect means it cannot be improved, therefore what are you asking for?

    http://dictionary.cambridge.org/dictionary/essential-american-english/perfect

    Mr, Monkeyboy gave you already the links where you can get the licensed versions.


    Success
    Cor


    • Edited by Cor Ligthert Wednesday, February 26, 2014 6:19 PM
    Wednesday, February 26, 2014 6:17 PM
  • @The Thinker,

    LOL while I can certainly appreciate the sentiment, Cor is correct and that would be a step too far.

    @Paul,

    I feel happy!


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    Reed - You might want to consider locking this thread before it gets ugly.

    Wednesday, February 26, 2014 6:25 PM
  • Option Strict Off and Option Explicit off gives you in fact back the variant.

    In C# the counterpart which is created to give in this in C# parity to VB.

    http://msdn.microsoft.com/en-us/library/dd264741.aspx

    Again and Again, VB.Net is the name from the product which contained VB7.0 in 2002. In 2003 the name changed to 2003 Net and after that it is not used anymore. However those for who the time stood still after the first year of the millennium change are going on keeping those names. 

    Dim X = "The Thinker" with all Options Off gives a kind of Variant, although, what is already written in this thread, gives not the dummy way of use with the Com objects. 

    I remember another major change between VB6, the mnemonic names of value types shifted to a more common use. The 8 bit was gone and integer became the 32bit one like all processors in those days.


    Success
    Cor


    Megan, I am not an MVP and I do not support vb6 I only want to improve VB.NET. Cor, Dim X = "The Thinker" only makes an object data type at best not variant but in most cases would convert to an string. We need a full fledged variant type that converts only to variant not object (make it 64-bit variant if you wish for compatibility reasons).  VB6 was good back in the day but C# programmers will not give up their throne which is very much like concrete in its current place. 

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr

    Wednesday, February 26, 2014 6:25 PM
  • Option Strict Off and Option Explicit off gives you in fact back the variant.In C# the counterpart which is created to give in this in C# parity to VB.

    Again and Again, VB.Net is the name from the product which contained VB7.0 in 2002. In 2003 the name changed to 2003 Net and after that it is not used anymore. However those for who the time stood still after the first year of the millennium change are going on keeping those names. Dim X = "The Thinker" with all Options Off gives a kind of Variant, although, what is already written in this thread, gives not the dummy way of use with the Com objects. I remember another major change between VB6, the mnemonic names of value types shifted to a more common use. The 8 bit was gone and integer became the 32bit one like all processors in those days.

    Success

    Cor

    @Cor Ligthert

    Your point is ?! VB7 never existed ! VB .NET is NOT a true VB7, this is why it is not as successful as VB6 (and it will never be). On the other hand, a NEW VB7 running any VB6 source code project would have all the success in the world.


    Wednesday, February 26, 2014 6:28 PM
  • Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.

    @Mr. Monkeyboy

    Ok, show me your best advanced open source code app (in any language) and then I will show you what Visual Basic 6.0 can do ! Unfortunately, the ignorant one is you (and also not too inteligent it seems). Let the anthropology assumptions to those smarter than you.  Look at the Visual Basic 6.0 avanced projects, these are facts!

    PS: how did you manage to talk about your father, I don't understand ...






    Wednesday, February 26, 2014 6:44 PM
  • Ok, show me your best advanced open source code app (in any language) and then I will show you what Visual Basic 6.0 can do ! Unfortunately, the ignorant one is you (and also not too inteligent it seems). Let the anthropology assumptions to those smarter than you.  Look at the Visual Basic 6.0 avanced projects, these are a facts!

    PS: how did you manage to talk about your father, I don't understand ...




    I do not understand what you are talking about Megan. I would recommend writing a vb6 application that can communicate with a device first. That's very difficult even for an "experienced" vb6 programmer unless they developed the driver themselves. If you are talking about me I never talked about my father. What advanced vb6 projects? Most business want database applications and a lot of vb6 database actions have been upgraded or replaced.

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr

    Wednesday, February 26, 2014 6:51 PM
  • Ok, show me your best advanced open source code app (in any language) and then I will show you what Visual Basic 6.0 can do ! Unfortunately, the ignorant one is you (and also not too inteligent it seems). Let the anthropology assumptions to those smarter than you.  Look at the Visual Basic 6.0 avanced projects, these are a facts!

    PS: how did you manage to talk about your father, I don't understand ...




    I do not understand what you are talking about Megan. I would recommend writing a vb6 application that can communicate with a device first. That's very difficult even for an "experienced" vb6 programmer unless they developed the driver themselves. If you are talking about me I never talked about my father. What advanced vb6 projects? Most business want database applications and a lot of vb6 database actions have been upgraded or replaced.

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr

    @The Thinker

    No :), that message was addressed to Mr. Monkeyboy (refresh the page and you will see).

    This is a link referring to exactly what you say  http://www.vbforums.com/showthread.php?728505-VB-Classic-(A-True-VB-7-0)

    PS: incidentally, regarding your nickname here, VB6 is nicknamed the language of the thinkers :)





    Wednesday, February 26, 2014 7:00 PM
  • Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.

    @Mr. Monkeyboy

    Ok, show me your best advanced open source code app (in any language) and then I will show you what Visual Basic 6.0 can do ! Unfortunately, the ignorant one is you (and also not too inteligent it seems). Let the anthropology assumptions to those smarter than you.  Look at the Visual Basic 6.0 avanced projects, these are a facts!

    PS: how did you manage to talk about your father, I don't understand ...





    Apparently with 30% less brain than a neanderthal he's a genius while neanderthals not so much. Why was that difficult for you to understand?

    I believe you're the one who's not too quick.

    Maybe spoiled if you have the money from your parents to buy all versions and years of Visual Studio or something.

    Definitely a big mouth. I believe inteligent has two Ls. Dumby.

    I believe your life resume would maybe fill a thimble while mine would drown yours. Significantly.

    Also I've a friend who wrote code for the EA-6B prowler electronic warfare aircraft in C++ I believe. It's top secret still probably. But I doubt, even if I could show it to you which then I'd have to kill you, that you could make VB6 do what it does.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.




    • Edited by Mr. Monkeyboy Wednesday, February 26, 2014 7:13 PM 5555
    Wednesday, February 26, 2014 7:05 PM
  • Ok, show me your best advanced open source code app (in any language) and then I will show you what Visual Basic 6.0 can do ! Unfortunately, the ignorant one is you (and also not too inteligent it seems). Let the anthropology assumptions to those smarter than you.  Look at the Visual Basic 6.0 avanced projects, these are a facts!

    PS: how did you manage to talk about your father, I don't understand ...




    I do not understand what you are talking about Megan. I would recommend writing a vb6 application that can communicate with a device first. That's very difficult even for an "experienced" vb6 programmer unless they developed the driver themselves. If you are talking about me I never talked about my father. What advanced vb6 projects? Most business want database applications and a lot of vb6 database actions have been upgraded or replaced.

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr

    @The Thinker

    No :), that message was addressed to Mr. Monkeyboy (refresh the page and you will see).

    This is a link referring to exactly what you say  http://www.vbforums.com/showthread.php?728505-VB-Classic-(A-True-VB-7-0)

    PS: incidentally, regarding your nickname here, VB6 is nicknamed the language of the thinkers :)





    Just so you know Megan if you do some digging it appears Microsoft has released some of the visual studio source code on codeplex.com and I remember reading an article on it. So Yes, if you painstaking want to add vb6 functionality to vb.net you can do so by implementing add-ons or extensibility code which does so and submit it to the Microsoft codeplex open source page (http://entlib.codeplex.com/ and maybe more on their but I cannot take to time to look). It appears the ruby and python followers did that (I spent too much time in the visual studio extension's center). However, I believe the biggest complaint is device simulation in vb.net and variants.  

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr

    Wednesday, February 26, 2014 7:52 PM
  • There was a control which enabled you to do this.  I have worked on various projects which required interaction with devices in particular the COM RS232 Port and the Parallel port.  So, no not a valid point.  I think what Megan is trying to say is that Visual Basic was an environment which allowed you to create applications very quickly with the least amount of skill.  Just like how the whole Windows thing started, it was SIMPLE TO USE.


    Dave Matthews

    Wednesday, February 26, 2014 7:56 PM
  • Ironically, I would bring back Windows XP as I have had so many problems with Microsoft Vista and Microsoft 7 and don't even think about using Windows 8.  Simple things such as cut and paste fail to work in Windows 7 at random times because of one of the 138 so called updates.  What is happening with the Microsoft agenda?  They are making things more difficult for their userbase.

    Dave Matthews

    Wednesday, February 26, 2014 7:57 PM
  • " I would recommend writing a vb6 application that can communicate with a device first. That's very difficult even for an "experienced" vb6 programmer unless they developed the driver themselves"

    Really??

    OMG my 100k+ line app controls robotics all the time, with no problems and amazing performance that competes with c++ compiled apps. Kind of makes sense, vb6 apps are basically Visual c++ converted apps.

    Yes I think for database and business apps vb.net might do, but for semi- real-time robotics control I only trust vb6.

    BTW. My apps are multithreaded and run 24/7 365 days a week, perfectly!

    And I know some vb6 engineers that would put anyone to shame ( they are currently working on a open source vb6) I still wish MS would wake up and resist this hate and cater to a huge group of productive programmers!

    Wednesday, February 26, 2014 7:58 PM
  • Okay, brilliant example which really matters.  You load up a program which you created in the late 1990s which was written in Visual Basic 6 and it works.  You then try the same with .NET and guess what - errors.  That is mainly the reason I was put of with .NET - it doesnt work out of the box!

    Dave Matthews

    Wednesday, February 26, 2014 8:00 PM
  • Ironic, I just bought Visual Basic 3 Boxed Retail from ebay 30 minutes ago for a research project.  That was the version I started with, as before that I was using Quick Basic 7.  Although Visual Basic 6 is gone, there was hidden methods on how to work with programming that have been lost since - and this is the important point.

    Dave Matthews

    Wednesday, February 26, 2014 8:04 PM
  • There was a control which enabled you to do this.  I have worked on various projects which required interaction with devices in particular the COM RS232 Port and the Parallel port.  So, no not a valid point.  I think what Megan is trying to say is that Visual Basic was an environment which allowed you to create applications very quickly with the least amount of skill.  Just like how the whole Windows thing started, it was SIMPLE TO USE.


    Dave Matthews

    :))))

    Actually, you must have good skills to do VB6 app's ;). VB6 allows beginner developers to make simple applications, and allows advanced VB6 programmers to make applications which are not possible (or very complicated to do) in other languages ;)

    Here we must make the difference between "complex" and "complicated", there are two distinct notions!


    Wednesday, February 26, 2014 8:16 PM
  • Ironically, I would bring back Windows XP as I have had so many problems with Microsoft Vista and Microsoft 7 and don't even think about using Windows 8.  Simple things such as cut and paste fail to work in Windows 7 at random times because of one of the 138 so called updates.  What is happening with the Microsoft agenda?  They are making things more difficult for their userbase.

    Dave Matthews

    Fortunately, VB6 IDE works on Win 7, Win 8, and will work on Win 9 :)
    Wednesday, February 26, 2014 8:18 PM
  • " I would recommend writing a vb6 application that can communicate with a device first. That's very difficult even for an "experienced" vb6 programmer unless they developed the driver themselves"

    Really??

    OMG my 100k+ line app controls robotics all the time, with no problems and amazing performance that competes with c++ compiled apps. Kind of makes sense, vb6 apps are basically Visual c++ converted apps.

    Yes I think for database and business apps vb.net might do, but for semi- real-time robotics control I only trust vb6.

    BTW. My apps are multithreaded and run 24/7 365 days a week, perfectly!

    And I know some vb6 engineers that would put anyone to shame ( they are currently working on a open source vb6) I still wish MS would wake up and resist this hate and cater to a huge group of productive programmers!

    So TRUE ! I also know a lot of Visual Basic 6.0 engineers that would put anyone to shame ! 
    Wednesday, February 26, 2014 8:24 PM
  • Ironic, I just bought Visual Basic 3 Boxed Retail from ebay 30 minutes ago for a research project.  That was the version I started with, as before that I was using Quick Basic 7.  Although Visual Basic 6 is gone, there was hidden methods on how to work with programming that have been lost since - and this is the important point.

    Dave Matthews

    Visual Basic 6.0 is NOT gone and will NOT be gone for a very long time, where do you pull these affirmations ?! Again, it will run on Windows 9! Read this: http://www.codeproject.com/Articles/710181/Visual-Basic-6-0-A-giant-more-powerful-than-ever



    Wednesday, February 26, 2014 8:32 PM
  • " I would recommend writing a vb6 application that can communicate with a device first. That's very difficult even for an "experienced" vb6 programmer unless they developed the driver themselves"

    Really??

    OMG my 100k+ line app controls robotics all the time, with no problems and amazing performance that competes with c++ compiled apps. Kind of makes sense, vb6 apps are basically Visual c++ converted apps.

    Yes I think for database and business apps vb.net might do, but for semi- real-time robotics control I only trust vb6.

    BTW. My apps are multithreaded and run 24/7 365 days a week, perfectly!

    And I know some vb6 engineers that would put anyone to shame ( they are currently working on a open source vb6) I still wish MS would wake up and resist this hate and cater to a huge group of productive programmers!


    Not even what I was talking  about and RS232 really? Write a multi-mouse emulator or simulator in vb6 or point me to one because I cannot find one! (multi-mouse devices not the lazy coding using sendinput but pure driver input injection! Impossible you say in vb.net! No!) RS232 and Serial ports are different from USB which is faster hence why it was replaced or converters were made! USB 3.0 is way faster. Yes, I program robotics projects too (I have used the boebot, Kinect (fervently in a personal project which was originally an experiment at work), and helped someone with their arundio even. So I call bull!

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr


    • Edited by The Thinker Wednesday, February 26, 2014 8:52 PM
    Wednesday, February 26, 2014 8:41 PM
  • 1) VB6 is a true RAD - you can develop faster in VB6 than VB.Net

    2) VB6 is faster than VB.Net on the same hardware ("VB6 is still the product to beat in performance"- Paul Yuknewicz, Program Manager for Visual Studio)

    3) VB6 is the same language as VBA, the macro language in Microsoft Office, which is still supported.

    4) VB6 programs can run on Windows from Windows 98 to Windows 8.1 64 bit (without recompiling)

    5) VB6 is still a more popular language than VB.Net (Tiobe, February 2014), despite it being 15 years old (and it is more popular than JavaScript, Python, Ruby and many others).

    6) VB.Net has never been a 'successful' product - more coders use C# than VB.Net; VB.Net after 12 years is still nowhere near as popular as VB6 is now, let alone when it was at it's height.

    7) Even .Net can hardly be described as a roaring success. Java and C++ are more widely used. Microsoft's Office Team refused to re-write Office in .Net (and yet Microsoft expects us to re-write our VB6 code in .Net.

    8) Microsoft can't even be bothered to provide sample code in VB.Net - it's a dying language.

    9) Microsoft are telling us the future is C++ and JavaScript 

    10) It looks like VB6 will work on Windows 8.1.1.  And almost certainly on Windows 9 and Windows 10 too. In fact, as long as Windows continues to use the Windows API, VB6 will still work.

    Vote for an Updated VB6


    Wednesday, February 26, 2014 8:43 PM
  • I don't want to think about programming in VB6 with USB ports, come on - Visual Basic was around before USB ports existed and as we know hasn't been updated to take into account of all these new (well current) mod cons.

    I think what everybody has loved about Visual Basic 6 is its RAD and how simple it was to use.  Yes, it is definetely outdated in terms of todays placement - but the ideas in VB6 were lost in the making of .NET.

    I hope we all agree on that point as that is essentially what people are arguing/discussing about on this form.


    Dave Matthews

    Wednesday, February 26, 2014 8:46 PM
  • And yet VB6 is still more popular than VB.Net, even though Microsoft have been trying to kill off VB6 for years.

    VB6 still more popular than VB.Net


    Wednesday, February 26, 2014 8:51 PM
  •  Do

     What you think VB6 programmers need, and what VB6 programmers say they need are totally separate things :)

    You tell VB6 is perfect. Perfect means it cannot be improved, therefore what are you asking for?

    Mr, Monkeyboy gave you already the links where you can get the licensed versions.

    Success
    Cor


    That's all you got?! You send me to a dictionary?! Really ?! Visual Basic 6.0 is perfect, nevertheless, it must be reintroduced to the market with some additions (separate modules (user selectable) for cross-platform development). Mr. Monkeyboy (if you as a MCC/MPV really want to be associated with him) gives information that we all know.

    Wednesday, February 26, 2014 8:54 PM
  • I don't want to think about programming in VB6 with USB ports, come on - Visual Basic was around before USB ports existed and as we know hasn't been updated to take into account of all these new (well current) mod cons.

    I think what everybody has loved about Visual Basic 6 is its RAD and how simple it was to use.  Yes, it is definetely outdated in terms of todays placement - but the ideas in VB6 were lost in the making of .NET.

    I hope we all agree on that point as that is essentially what people are arguing/discussing about on this form.


    Dave Matthews


    Just for arguments sake did you read my post above for extending visual studio? Microsoft has made a lot of the enterprise visual studio library open source for people to change as they please. You might have missed that. A lot of people have made visual studio add-ons to address the issue. I was just pushing somewhat. But I listed a pro of vb6 earlier: "Variants are not supported". Are you familiar with DSF(Device simulation framework)? I have some c++ code in a dll file working from vb.net except when I call the QueueInputReport function which does not pass my data as intended. It seems most device drivers are written in c because that's what windows is written in. That is part of a project I am using in vb.net and it calls c++ code which in-turn calls low-level code that was not even available to vb programmers back then as far as I know. I had to modify Microsoft's original code which was very poorly documented.

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr


    • Edited by The Thinker Wednesday, February 26, 2014 9:02 PM
    Wednesday, February 26, 2014 9:00 PM
  • In response to Megan saying VB6 is still alive...

    It is technically gone, although I wish it hadn't.  Where can I buy a brand new Visual Basic 6.0 retail box from Microsoft?  I can't!  Therefore whether we like it or not, its gone.  Have a look at wikipedia - its 'retired'.  This doesn't mean I want it to be gone, as it was one of the best programming languages that I have used and I do wish it was still around AND supported.


    Dave Matthews


    • Edited by Dave Matthews Wednesday, February 26, 2014 9:05 PM Response direction
    Wednesday, February 26, 2014 9:01 PM
  • Ladies and gentlemen of this thread, I mean no ill-will to anyone, but the reality is that this is a Microsoft forum and they consider VB6 to be a deprecated language.

    No matter your stand on it – whether an advocate for or against – it’s all a moot point.

    I encourage everyone here to resolve that this is the reality of things, thus rendering continued discussion about it completely senseless.


    Please call me Frank :)

    Wednesday, February 26, 2014 9:12 PM
  • Reply tothe Thinker...

    I don't work with direct I/O any longer as I moved away from Visual Basic 6 to running a company that specialises in writing Web applications.  I did chek out .NET, but I felt it was so messed up that I gave up.  Having had to convert applications from Quick Basic to Visual Basic 3 and then again from Visual Basic 3 to Visual Basic 6 - I had enough.  Not only this, the source code of dot net didn't work wither later versions.  I just wonder how many programmers did the same line of thought....

    What I liked about VB6 was that it was simple and something that Microsoft could of expanded on, which obviously they didn't.

    As for robotics, I just *played* with remote controlled cars linking them up via RS232 communication channel then to a Parallel Relay box.  I created the applications using visual basic 3 and also quick basic 4.5.

    This forum I feel isn't about slagging off VB6 in favor of .NET, it is about recognising that there was a potential future for VB6 which never happened and it was a lost oppourtunity for M$.


    Dave Matthews

    Wednesday, February 26, 2014 9:15 PM
  • It is technically gone, although I wish it hadn't.  Where can I buy a brand new Visual Basic 6.0 retail box from Microsoft?  I can't!  Therefore whether we like it or not, its gone.  Have a look at wikipedia - its 'retired'.  This doesn't mean I want it to be gone, as it was one of the best programming languages that I have used and I do wish it was still around AND supported.


    Dave Matthews

    Dave you wouldn't happen to know usage of U SBHID devices would you? I have some code that works in  vbscript but not vb.net or c++ for that matter (Their are 32-bit tlb files for usage in  vb6 if you want to try your luck). If I were to finish my program I could for fun's sake remake a tlb for usage in vb6. If you can call native dlls you could try and call HID.dll if you are experienced with it. http://kinectmultipoint.codeplex.com. The softhidreceiver.dll project source code is in c++ so you should be able to call it using vb6 with some changes (QueueInputReport is the culprit). USB emulation is hard as hell and Microsoft's DSF library works but translation into vb.net,vb6, or any language for that matter is hard. 

    Check out Microsoft's All in one framework on codeplex: http://1code.codeplex.com/

    Its my heaven for everything Microsoft! :D

    Plus, if you make a github or codeplex project (very popular by Microsoft developers so you will get the equivalent of media attention if you start one) where everyone can join your project to improve vb6, I'll join because I know all most of the calls to Microsoft dll's but the cool thing about visual studio is dll to tlb conversion. Cosmos is a C# open source OS (http://cosmos.codeplex.com) which is the coolest and most complex project I've seen so far on codeplex with the dotnet framework. If you want to take a surf in the MS ope source community go ahead and make a codeplex page because their are no shortage of crazy ideas on codeplex (plus you can get funded by ads for people that visit the project page  or Pay Per view with no clicks required to make money).

    My thoughts: We need a VB.NET extreme that adds more functionality. Right now if I finish my project anyone can easily use visual studio to make a tlb file and use from vb6 if they choose to. I have to say device management and device communication are easily the most complicated part of VB.NET though.


    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr






    • Edited by The Thinker Wednesday, February 26, 2014 9:34 PM
    Wednesday, February 26, 2014 9:16 PM
  • I'd say it's most like saying:

    "Bring back Windows 3.11, we need it."  =P

    This thread should probably go to Off-Topic, but perhaps it also serves to remind people that VB6 should be retired and forgotten.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    You are behind with the news and you do not know what you say! MPV or not MPV, you lose credibility because you talk like that of Visual Basic 6.0! This CodeProject article will explain clearly why Visual Basic 6.0 is better and way faster than other programming languages:

    http://www.codeproject.com/Articles/710181/Visual-Basic-6-0-A-giant-more-powerful-than-ever

    This link will show you that VB6 has the smartest advanced opensource projects:

    https://www.facebook.com/MicrosoftVB

    There's almost more old people in the U.S. than young people. Maybe that's why there are so many more VB6 programmers around. You know how people get the older they get. Unable to accept change.

    I'm sure none of those programs at that codeproject link could be written using vb.net and work anywhere nearly as well as the ones written in VB6. :)

    Although a lot of the article at that link seems more of opinion necessarily than fact.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.

    That's true because implementation and fact are far different from speculation from weird websites that are biased. Megan, I will refer to a vb6 teacher I had who would use vb6 over and over again (an older version) but that does not mean he was correct and that it would work on new machines. This is the reason people upgrade to vb.net because support died a long time ago otherwise people would be using it now. You could open source vb6 but that requires "support" even from a developer community and in that respect even mono has them beat. Go ask any indie game developer about what programming languages they use and mono is probably one of the top programming language environments used besides visual studio (mono has vb.net and c# of its own). This may even be more true since Microsoft stated they officially support unity which uses it: http://news.xbox.com/2013/06/xbox-one-unity-announcement and http://unity3d.com/company/public-relations/news/unity-announces-strategic-collaboration-microsoft.  You could never use vb6 on the xbox 360 or xbox one because of possible problems with developing a perfect application like C# or C++ when developed properly has major performance boosts. Which is higher then both visual basic or vb.net at all:  http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html or vb6 or vb.net are not even listed on one blog: http://blog.codeeval.com/codeevalblog/2014#.Uw4WtxOYaM8 and another uses multiple sources which state it is not even on the list at all: http://www.slideshare.net/lyndadotcom/top-10-programming-languages-to-know-in-2014. Although this maybe misleading because general C# and vb.net code can be re-used or cross-coded with C# improving functionality and one coder may use vb.net. This is a simple google query language of most popular programming language's of 2014 and in one vb6 is barely 2-3 spaces above vb.net in usage. However, the results could all be biased because it is only about a 1/3 of the way through 2014 and impossible to tell unless they are forecasting which would make the results incomplete.


    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr


    People use VB6 aaa lot, in 2014 is the most popular. You are not aware of this issue, but VB6 is supported even on Win 9 and on all OS's that MS will make until 2020.

    Sorry to say but people do not migrate to VB .NET! What you hear is just "migration" propaganda, precisely for this reason: people do not migrate to VB .NET.


    I think even TIOBE is wondering how they managed to put VB6 on place 7 when VB6 should be in top 3 (mimimum top 3).

    ARE YOU SERIOUS WITH http://blog.codeeval.com ?! REALY ?! This is baiest and a NO NAME site !

    You know, on slideshare.com I can upload a slide myself ...


    Wednesday, February 26, 2014 9:25 PM
  • Megan, in 12 years a lot has changed.  The market has changed, the majority of people are now developing Smart phone applications, and web applications.  When VB6 was around, phones were like dumb terminals (if you could call them that).

    Dave Matthews

    Wednesday, February 26, 2014 9:29 PM
  • 1) VB6 is a true RAD - you can develop faster in VB6 than VB.Net

    2) VB6 is faster than VB.Net on the same hardware ("VB6 is still the product to beat in performance"- Paul Yuknewicz, Program Manager for Visual Studio)

    3) VB6 is the same language as VBA, the macro language in Microsoft Office, which is still supported.

    4) VB6 programs can run on Windows from Windows 98 to Windows 8.1 64 bit (without recompiling)

    5) VB6 is still a more popular language than VB.Net (Tiobe, February 2014), despite it being 15 years old (and it is more popular than JavaScript, Python, Ruby and many others).

    6) VB.Net has never been a 'successful' product - more coders use C# than VB.Net; VB.Net after 12 years is still nowhere near as popular as VB6 is now, let alone when it was at it's height.

    7) Even .Net can hardly be described as a roaring success. Java and C++ are more widely used. Microsoft's Office Team refused to re-write Office in .Net (and yet Microsoft expects us to re-write our VB6 code in .Net.

    8) Microsoft can't even be bothered to provide sample code in VB.Net - it's a dying language.

    9) Microsoft are telling us the future is C++ and JavaScript 

    10) It looks like VB6 will work on Windows 8.1.1.  And almost certainly on Windows 9 and Windows 10 too. In fact, as long as Windows continues to use the Windows API, VB6 will still work.

    Even l can't explain things better you did :)
    Wednesday, February 26, 2014 9:39 PM
  • Ladies and gentlemen of this thread, I mean no ill-will to anyone, but the reality is that this is a Microsoft forum and they consider VB6 to be a deprecated language.

    No matter your stand on it – whether an advocate for or against – it’s all a moot point.

    I encourage everyone here to resolve that this is the reality of things, thus rendering continued discussion about it completely senseless.


    Please call me Frank :)

    For me this thread is deja-vu all over again and the topic of this discussion officially ended a number of years ago. No point debating it here.

    Time to move this thread to the off-topic forum.


    Paul ~~~~ Microsoft MVP (Visual Basic)

    Wednesday, February 26, 2014 10:00 PM
  • I'd say it's most like saying:

    "Bring back Windows 3.11, we need it."  =P

    This thread should probably go to Off-Topic, but perhaps it also serves to remind people that VB6 should be retired and forgotten.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    You are behind with the news and you do not know what you say! MPV or not MPV, you lose credibility because you talk like that of Visual Basic 6.0! This CodeProject article will explain clearly why Visual Basic 6.0 is better and way faster than other programming languages:

    http://www.codeproject.com/Articles/710181/Visual-Basic-6-0-A-giant-more-powerful-than-ever

    This link will show you that VB6 has the smartest advanced opensource projects:

    https://www.facebook.com/MicrosoftVB

    There's almost more old people in the U.S. than young people. Maybe that's why there are so many more VB6 programmers around. You know how people get the older they get. Unable to accept change.

    I'm sure none of those programs at that codeproject link could be written using vb.net and work anywhere nearly as well as the ones written in VB6. :)

    Although a lot of the article at that link seems more of opinion necessarily than fact.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.

    That's true because implementation and fact are far different from speculation from weird websites that are biased. Megan, I will refer to a vb6 teacher I had who would use vb6 over and over again (an older version) but that does not mean he was correct and that it would work on new machines. This is the reason people upgrade to vb.net because support died a long time ago otherwise people would be using it now. You could open source vb6 but that requires "support" even from a developer community and in that respect even mono has them beat. Go ask any indie game developer about what programming languages they use and mono is probably one of the top programming language environments used besides visual studio (mono has vb.net and c# of its own). This may even be more true since Microsoft stated they officially support unity which uses it: http://news.xbox.com/2013/06/xbox-one-unity-announcement and http://unity3d.com/company/public-relations/news/unity-announces-strategic-collaboration-microsoft.  You could never use vb6 on the xbox 360 or xbox one because of possible problems with developing a perfect application like C# or C++ when developed properly has major performance boosts. Which is higher then both visual basic or vb.net at all:  http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html or vb6 or vb.net are not even listed on one blog: http://blog.codeeval.com/codeevalblog/2014#.Uw4WtxOYaM8 and another uses multiple sources which state it is not even on the list at all: http://www.slideshare.net/lyndadotcom/top-10-programming-languages-to-know-in-2014. Although this maybe misleading because general C# and vb.net code can be re-used or cross-coded with C# improving functionality and one coder may use vb.net. This is a simple google query language of most popular programming language's of 2014 and in one vb6 is barely 2-3 spaces above vb.net in usage. However, the results could all be biased because it is only about a 1/3 of the way through 2014 and impossible to tell unless they are forecasting which would make the results incomplete.


    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr


    People use VB6 aaa lot, in 2014 is the most popular. You are not aware of this issue, but VB6 is supported even on Win 9 and on all OS's that MS will make until 2020.

    Sorry to say but people do not migrate to VB .NET! What you hear is just "migration" propaganda, precisely for this reason: people do not migrate to VB .NET.


    I think even TIOBE is wondering how they managed to put VB6 on place 7 when VB6 should be in top 3 (mimimum top 3).

    ARE YOU SERIOUS WITH http://blog.codeeval.com ?! REALY ?! This is baiest and a NO NAME site !

    You know, on slideshare.com I can upload a slide myself ...



    No better then the site you posted and Devon is correct we need to end this discussion before Reed shuts us down. However, as I stated above if you want vb6 badly then create an add-on that lets you use it or make VB.NET better. I have been going backwards in that respect for VB.NET starting with device drivers and making my way up (Hardest to easiest).

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr


    • Edited by The Thinker Wednesday, February 26, 2014 10:02 PM
    Wednesday, February 26, 2014 10:02 PM
  • Ladies and gentlemen of this thread, I mean no ill-will to anyone, but the reality is that this is a Microsoft forum and they consider VB6 to be a deprecated language.

    No matter your stand on it – whether an advocate for or against – it’s all a moot point.

    I encourage everyone here to resolve that this is the reality of things, thus rendering continued discussion about it completely senseless.


    Please call me Frank :)

    For me this thread is deja-vu all over again and the topic of this discussion officially ended a number of years ago. No point debating it here.

    Time to move this thread to the off-topic forum.


    Paul ~~~~ Microsoft MVP (Visual Basic)


    Agreed...

    Please call me Frank :)

    Wednesday, February 26, 2014 10:06 PM
  • Ladies and gentlemen of this thread, I mean no ill-will to anyone, but the reality is that this is a Microsoft forum and they consider VB6 to be a deprecated language.

    No matter your stand on it – whether an advocate for or against – it’s all a moot point.

    I encourage everyone here to resolve that this is the reality of things, thus rendering continued discussion about it completely senseless.


    Please call me Frank :)

    For me this thread is deja-vu all over again and the topic of this discussion officially ended a number of years ago. No point debating it here.

    Time to move this thread to the off-topic forum.


    Paul ~~~~ Microsoft MVP (Visual Basic)


    Agreed...

    Please call me Frank :)

    Flag off-topic and move on or lock the thread. If anyone wants to improve vb.net please tell me or are looking for help upgrading a project (I mostly deal with robotics, the Kinect, and devices but do a fair bit with content in vb.net too). As I said if anyone was serious create a codeplex page. No cares about your programming language as long as you upload source code and show what you can do (make a visual studio dotnet project and upload it initially if you have troubles). 

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr


    • Edited by The Thinker Wednesday, February 26, 2014 10:15 PM
    Wednesday, February 26, 2014 10:14 PM
  • Ladies and gentlemen of this thread, I mean no ill-will to anyone, but the reality is that this is a Microsoft forum and they consider VB6 to be a deprecated language.

    No matter your stand on it – whether an advocate for or against – it’s all a moot point.

    I encourage everyone here to resolve that this is the reality of things, thus rendering continued discussion about it completely senseless.


    Please call me Frank :)

    No the language isn't deprecated. It is identical to the VBA language in Microsoft Office (and in AutoCad). And VBA is current and supported.

    Where is the logic in supplying and supporting the language when packaged inside Office but then refusing to supply the same language in the standalone VB6 package?

    For me this thread is deja-vu all over again and the topic of this discussion officially ended a number of years ago. No point debating it here.

    Time to move this thread to the off-topic forum.


    Paul ~~~~ Microsoft MVP (Visual Basic)

    Just because you are a Microsoft MVF (Most Valuable Fanboi) doesn't make you the censor of this thread. If people want to discuss VB6 they will.

    Vote for VB6

    Wednesday, February 26, 2014 10:15 PM
  • Megan, in 12 years a lot has changed.  The market has changed, the majority of people are now developing Smart phone applications, and web applications.  When VB6 was around, phones were like dumb terminals (if you could call them that).

    Dave Matthews

    Yes, much has changed since then! Believe it or not, VB6 has changed too, a lot actually! This is why you should read the CodeProject article, it will illuminate many answers, and most importantly, why we need a new version of VB6! Due to a very good brotherhood that VB6 has established with ASM, the VB6 language is now all powerful and I do not believe it has any real competitors, not even the all adored C++! 

    The problem is that programmers from other communities do not know these details and when they talk, they talk unaware of the real facts !


    Wednesday, February 26, 2014 10:17 PM
  • Ladies and gentlemen of this thread, I mean no ill-will to anyone, but the reality is that this is a Microsoft forum and they consider VB6 to  ....   nseless.


    Please call me Frank :)

    Frank, stay in your box and put down the pipe ! VB6 will come back ! :)






    Wednesday, February 26, 2014 10:27 PM
  • Megan and others,

    I am not here to be adversarial; what you choose to use is up to you.

    That said though, THIS FORUM IS ABOUT VB NET ... not VB6.

    *****

    If I've offended anyone then I proffer my apology.


    Please call me Frank :)

    Wednesday, February 26, 2014 10:29 PM
  • Megan and others,

    I am not here to be adversarial; what you choose to use is up to you.

    That said though, THIS FORUM IS ABOUT VB NET ... not VB6.

    *****

    If I've offended anyone then I proffer my apology.


    Please call me Frank :)

    Ultimately I must admit that I can not hate VB .NET programmers because they are our brothers. VB6 is a necessity, and must re-appear in parallel with VB .NET!

    We all must be careful when we speak ill of the "Visual Basic" word, because we risk to depreciate the entire VB family line!


    Wednesday, February 26, 2014 10:37 PM
  • Ultimately I must admit that I can not hate VB .NET programmers because they are our brothers.

    I have no answers, but I do hope that you and others do well in your ventures, no matter the program language of choice.

    I mean that sincerely. :)


    Please call me Frank :)

    Wednesday, February 26, 2014 10:43 PM
  • I'm still awaiting some examples of actual useful solutions that VB6 can do that VB NET cannot.

    Wednesday, February 26, 2014 10:45 PM
  • Ultimately I must admit that I can not hate VB .NET programmers because they are our brothers.

    I have no answers, but I do hope that you and others do well in your ventures, no matter the program language of choice.

    I mean that sincerely. :)


    Please call me Frank :)

    Thank you Frank :)
    Wednesday, February 26, 2014 10:49 PM
  • I'm still awaiting some examples of actual useful solutions that VB6 can do that VB NET cannot.

    Sten2005 answered your question, look above!
    Wednesday, February 26, 2014 10:57 PM
  • I can't understand why when so many people want VB6 back that nobody never sat down and wrote the dam compiler.

    Why is it nessessary to wait on Microsoft to do it ... when it is almost sure that they wont do it.

    Wednesday, February 26, 2014 11:21 PM
  • For me this thread is deja-vu all over again and the topic of this discussion officially ended a number of years ago. No point debating it here.

    Time to move this thread to the off-topic forum.


    Paul ~~~~ Microsoft MVP (Visual Basic)

    Just because you are a Microsoft MVF (Most Valuable Fanboi) doesn't make you the censor of this thread. If people want to discuss VB6 they will.

    Vote for VB6

    LOL! Mike is that you? Or, perhaps it's Karl? ;-)

    It would appear that we're are being invaded by a few of the old Classic VB guys, some of them possibly former MVPs, hiding behind names that are most likely not theirs. (Megan? Come on!)

    I wouldn't bother debating them since they're simply here to cause trouble.


    Paul ~~~~ Microsoft MVP (Visual Basic)

    Wednesday, February 26, 2014 11:27 PM
  • For me this thread is deja-vu all over again and the topic of this discussion officially ended a number of years ago. No point debating it here.

    Time to move this thread to the off-topic forum.


    Paul ~~~~ Microsoft MVP (Visual Basic)

    Just because you are a Microsoft MVF (Most Valuable Fanboi) doesn't make you the censor of this thread. If people want to discuss VB6 they will.

    Vote for VB6

    LOL! Mike is that you? Or, perhaps it's Karl? ;-)

    It would appear that we're are being invaded by a few of the old Classic VB guys, some of them possibly former MVPs, hiding behind names that are most likely not theirs. (Megan? Come on!)

    I wouldn't bother debating them since they're simply here to cause trouble.


    Paul ~~~~ Microsoft MVP (Visual Basic)

    You are trying to censor again. It isn't for you to decide who is worth debating. It isn't for you to decide what threads are allowed.
    It isn't even for you to decide whether names are real or not.

    Wednesday, February 26, 2014 11:39 PM
  • I can't understand why when so many people want VB6 back that nobody never sat down and wrote the dam compiler.

    Why is it nessessary to wait on Microsoft to do it ... when it is almost sure that they wont do it.

    I though I would end this conversion with that but no-one is paying attention to my posts. :( That's probably the best conclusion and idea and developing a new programming language is fun so I see no reason why not! Its like a nice cake because you can open source it for the community and put what you want in it. I once thought about one for AI needs I had a while back. I still might be tempted because supposedly I read an article awhile back that allowed you to call your exe file in vb.net from vbscript that peeked my interest.  Megan, if you or any vb6 folks happen to start a compiler for an enhanced version of vb6 or plan on extending VB.NET to include some more vb6 support functions count me in! (I could probably making a killing the further along I go ;) ).  Professionally, I have been using VB.NET for 2 1/2 years. However, personally I have been using it since I was 13-14 (2003-2004) along with HTML. So I have seen how it has changed (for awhile I just gave up and then came back after while to and it made sense after about visual studio 2008. As far as Com in office maybe it may not be useful).  So I am not a vb6 hater, I just use VB.NET now and wish to expand it and provide useful functions to people (not that its tempting to play around with vbscript and my old vb6 programs from time to time especially the drawing one).

     

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr

    Wednesday, February 26, 2014 11:48 PM
  • If you are referring to the list of ten things, that is not an answer at all, I am asking for a specific VB6 project that performs a useful task that cannot be converted to or rewritten in VB NET.

    I also have to take exception to a remark you made to Cor Ligthert - "The fact that you are not coherent in text, says a lot about how good you are at programming!" - Have you ever considered that some people here do not natively speak english ?

    Lastly, since you must be an experienced programmer, I'd like you to take 5 or 10 minutes to do this simple task:

    Create a program with a button and a large textbox. When the button is clicked, create a random number of approximately 30,000 to 60,000 bits. Display it as both base 10 and base 16. Then calculate and display the following hashes for the base 10 string:

    MD5, SHA1, SHA256, and SHA512


    Wednesday, February 26, 2014 11:52 PM
  • Please reconsider introducing VB6 to the market. It is needed by many.


    For sale: backups of my old vb6 - $    100.00

                  backups of my old vb1 - $ 1,000.00

                  backups of my old qb4 - $10,000.00

    keypunch cards computing the value of pi from my first programming class - priceless.

    Wednesday, February 26, 2014 11:59 PM
  • Please reconsider introducing VB6 to the market. It is needed by many.


    For sale: backups of my old vb6 - $    100.00

                  backups of my old vb1 - $ 1,000.00

                  backups of my old qb4 - $10,000.00

    keypunch cards computing the value of pi from my first programming class - priceless.

    You are underpricing your VB6.

    VB6 on Ebay New VB6.0 Professional $429.75

    Thursday, February 27, 2014 12:12 AM
  • Please reconsider introducing VB6 to the market. It is needed by many.


    For sale: backups of my old vb6 - $    100.00

                  backups of my old vb1 - $ 1,000.00

                  backups of my old qb4 - $10,000.00

    keypunch cards computing the value of pi from my first programming class - priceless.

    You are underpricing your VB6.

    VB6 on Ebay New VB6.0 Professional $429.75


    I have a photo of a caveman's poop in binary, whats that worth?

    Sorry. Seemed funny when I thought of it. I have nothing against vb6. Just so you know.

    Thursday, February 27, 2014 12:17 AM
  • I can't understand why when so many people want VB6 back that nobody never sat down and wrote the dam compiler.

    Why is it nessessary to wait on Microsoft to do it ... when it is almost sure that they wont do it.

    We actually are in making of it, see the above comments. But the idea is to keep in touch with Microsoft.

    Nothing is for sure ! But I'm sure Microsoft will make us a cool surprise regarding a new verion of Visual Basic 6.0! :) just a feeling ...

    Thursday, February 27, 2014 12:19 AM
  • Megan and others,

    I am not here to be adversarial; what you choose to use is up to you.

    That said though, THIS FORUM IS ABOUT VB NET ... not VB6.

    *****

    If I've offended anyone then I proffer my apology.


    Please call me Frank :)

    Ultimately I must admit that I can not hate VB .NET programmers because they are our brothers. VB6 is a necessity, and must re-appear in parallel with VB .NET!

    We all must be careful when we speak ill of the "Visual Basic" word, because we risk to depreciate the entire VB family line!


    Hey Megan,

    Paul knows that Megan isn't your real name !  (Did you know that ?)
    He thinks you are someone called Mike or Karl !

    And he has loads more points than you have so he must be right !

    Thursday, February 27, 2014 12:20 AM
  • For me this thread is deja-vu all over again and the topic of this discussion officially ended a number of years ago. No point debating it here.

    Time to move this thread to the off-topic forum.


    Paul ~~~~ Microsoft MVP (Visual Basic)

    Just because you are a Microsoft MVF (Most Valuable Fanboi) doesn't make you the censor of this thread. If people want to discuss VB6 they will.

    LOL! Mike is that you? Or, perhaps it's Karl? ;-)

    It would appear that we're are being invaded by a few of the old Classic VB guys, some of them possibly former MVPs, hiding behind names that are most likely not theirs. (Megan? Come on!)

    I wouldn't bother debating them since they're simply here to cause trouble.


    Paul ~~~~ Microsoft MVP (Visual Basic)

    :))))))))))))))

    nop, unfortunately I am just Megan and I want the Visual Basic 6.0 return, as many do :)

    Thursday, February 27, 2014 12:23 AM
  • If you are referring to the list of ten things, that is not an answer at all, I am asking for a specific VB6 project that performs a useful task that cannot be converted to or rewritten in VB NET.

    I also have to take exception to a remark you made to Cor Ligthert - "The fact that you are not coherent in text, says a lot about how good you are at programming!" - Have you ever considered that some people here do not natively speak english ?

    Lastly, since you must be an experienced programmer, I'd like you to take 5 or 10 minutes to do this simple task:

    Create a program with a button and a large textbox. When the button is clicked, create a random number of approximately 30,000 to 60,000 bits. Display it as both base 10 and base 16. Then calculate and display the following hashes for the base 10 string:

    MD5, SHA1, SHA256, and SHA512



    base 16 (hexadecimal) is not very hard for me since I ate and breather hexadecimal for my cisco class and was required to do it by hand. As far as hashes, I forget the libraries in VB.NET to do so. In fact, I might update my binary application to include instant hexadecimal too. I figured out how to do partial binary. Oh, I should write an article on my blog about Linux file permissions and partial binary since I learned about how chmod involves 4-bits. Linux has changed so much since its birth. For reference, this conversation reminds me of how SQL server changed from its UNIX/OS-2 days (I had to help write an article on it which is sad to say a crazy history).

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr


    • Edited by The Thinker Thursday, February 27, 2014 12:25 AM
    Thursday, February 27, 2014 12:24 AM
  • I can't understand why when so many people want VB6 back that nobody never sat down and wrote the dam compiler.

    Why is it nessessary to wait on Microsoft to do it ... when it is almost sure that they wont do it.

    I though I would end this conversion with that but no-one is paying attention to my posts. :( That's probably the best conclusion and idea and developing a new programming language is fun so I see no reason why not! Its like a nice cake because you can open source it for the community and put what you want in it. I once thought about one for AI needs I had a while back. I still might be tempted because supposedly I read an article awhile back that allowed you to call your exe file in vb.net from vbscript that peeked my interest.  Megan, if you or any vb6 folks happen to start a compiler for an enhanced version of vb6 or plan on extending VB.NET to include some more vb6 support functions count me in! (I could probably making a killing the further along I go ;) ).  Professionally, I have been using VB.NET for 2 1/2 years. However, personally I have been using it since I was 13-14 (2003-2004) along with HTML. So I have seen how it has changed (for awhile I just gave up and then came back after while to and it made sense after about visual studio 2008. As far as Com in office maybe it may not be useful).  So I am not a vb6 hater, I just use VB.NET now and wish to expand it and provide useful functions to people (not that its tempting to play around with vbscript and my old vb6 programs from time to time especially the drawing one).

     

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr

    I pay attention to your posts. I hope that the whole VB family of programmers will be more united. Do not forget that we have enough worries from Java up to C++. :)

    Thursday, February 27, 2014 12:29 AM
  • If you are referring to the list of ten things, that is not an answer at all, I am asking for a specific VB6 project that performs a useful task that cannot be converted to or rewritten in VB NET.

    I also have to take exception to a remark you made to Cor Ligthert - "The fact that you are not coherent in text, says a lot about how good you are at programming!" - Have you ever considered that some people here do not natively speak english ?

    Lastly, since you must be an experienced programmer, I'd like you to take 5 or 10 minutes to do this simple task:

    Create a program with a button and a large textbox. When the button is clicked, create a random number of approximately 30,000 to 60,000 bits. Display it as both base 10 and base 16. Then calculate and display the following hashes for the base 10 string:

    MD5, SHA1, SHA256, and SHA512


    Realy?! Who do you think you are ?! swallow this if you want to meet quality and intelligence in Visual Basic 6.0:

    http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=73513&lngWId=1

    http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=73481&lngWId=1

    http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=73500&lngWId=1

    http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=73502&lngWId=1

    http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=73499&lngWId=1

    Do not try to lecture me again, are you a man in the middle-aged crisis!? I'm really surprised that I even bother to respond !


    Thursday, February 27, 2014 12:43 AM
  • I can't understand why when so many people want VB6 back that nobody never sat down and wrote the dam compiler.

    Why is it nessessary to wait on Microsoft to do it ... when it is almost sure that they wont do it.

    I though I would end this conversion with that but no-one is paying attention to my posts. :( That's probably the best conclusion and idea and developing a new programming language is fun so I see no reason why not! Its like a nice cake because you can open source it for the community and put what you want in it. I once thought about one for AI needs I had a while back. I still might be tempted because supposedly I read an article awhile back that allowed you to call your exe file in vb.net from vbscript that peeked my interest.  Megan, if you or any vb6 folks happen to start a compiler for an enhanced version of vb6 or plan on extending VB.NET to include some more vb6 support functions count me in! (I could probably making a killing the further along I go ;) ).  Professionally, I have been using VB.NET for 2 1/2 years. However, personally I have been using it since I was 13-14 (2003-2004) along with HTML. So I have seen how it has changed (for awhile I just gave up and then came back after while to and it made sense after about visual studio 2008. As far as Com in office maybe it may not be useful).  So I am not a vb6 hater, I just use VB.NET now and wish to expand it and provide useful functions to people (not that its tempting to play around with vbscript and my old vb6 programs from time to time especially the drawing one).

     

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr

    I pay attention to your posts. I hope that the whole VB family of programmers will be more united. Do not forget that we have enough worries from Java up to C++. :)


    Same in VB.NET, in our minds we do not like JAVA because its means competition despite what we say (respect or toleration is different). Minimum we could make VB.NET closer to c++ or interop better. Did I once see an article floating around asking for visual basic.net to be open source?  Maybe it was for visual studio but I thought it was for visual basic. Megan, you would be surprised how much dynamic code could be loaded in a VB.NET project at runtime especially with reflection. But in the end I am only here to make code that works as opposed to throwing around something that does not work in VB.NET. I think you can inherit from a VB.NET base class and add items or libraries but can someone confirm this? Maybe if this was correct you could do it. P.S. go to my blog and tell me what you think. I am still in progress on my Kinect Multipoint project with driver code because most of the lower level code requires c/c++ which is so hard at times to get working (Not to mention you bluescreen your computer if illegal actions take place). Message me your project or join me on one of my projects on codeplex so I can help you with yours.

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr





    • Edited by The Thinker Thursday, February 27, 2014 12:55 AM
    Thursday, February 27, 2014 12:44 AM
  • I do not use rs232, i use direct communication to a high speed usb micro ...
    Thursday, February 27, 2014 12:52 AM
  • Megan you actually gave Cor Ligthert a difficult time because he's from Germany and probably his primary language is not English? I think he uses English more effectively than many posters here. And I find his terminology and use of the english language rather refreshing. And hilarious a lot of the time. I've worked all over the world with engineers whos primary language was other than english that spoke english. They were just as capable as anybody else. Man you really are a Charlie Foxtrot.

    When you look at this why would Microsoft bother spending the money to bring back VB6? VB is certainly not a huge market requirement. And what portion of the VB in each image is for VB6 or less?

    Programming Language Popularity

    And this article says all I need to know.

    The Silent Majority: Why Visual Basic 6 Still Thrives

    "Microsoft recently extended “It Just Works” compatibility for Visual Basic 6 applications through the full lifetime of Windows 8 (see this month’s Editor’s Note, “Old Soldiers Never Die”). Visual Basic 6 first shipped in 1998, so its apps will have at least 24 years of supported lifetime. Contrast that with the Microsoft .NET Framework 1.0 (2002), which is incompatible with Windows 7 (2009).

    A student of mine named Eric once joked that Visual Basic 6 was “the un-killable cockroach” in the Windows ecosystem. That analogy goes deeper than you might think. Cockroaches are successful because they’re simple. They do what they need to do for their ecological niche and no more. Visual Basic 6 did what its creators intended for its market niche: enable very rapid development of limited programs by programmers of lesser experience. It was never meant for heavy-duty coders developing complex applications.

    Visual Basic 6 accomplished its goals by abstracting away the complexity of the underlying Windows OS. Simple things were very simple to accomplish. On the other hand, complex things, such as dealing with threads, were impossible. My rule of thumb for Visual Basic 6 was: if I couldn’t do it within 10 minutes, I couldn’t do it at all.

    Another key to the success of Visual Basic 6 was the much shorter learning curve demanded by its limited feature set. Learning to drive a bus takes much less time than learning to fly a fighter jet. Becoming a good Visual Basic 6 programmer took much less time than becoming a good C++ programmer, the primary alternative at the time.

    When Microsoft made Visual Basic .NET “a full-fledged language,” the company loaded it up with all the power and concomitant complexity that C# has—threads, background operations and inheritance, to name just a few. It therefore required the same skill set as C# programming, the same learning curve and the same experience.

    The people at Microsoft did that because that’s what they thought they heard the Visual Basic 6 community demanding. But Visual Basic 6 programmers epitomize the “silent majority,” a term popularized by U.S. President Richard Nixon in 1969 to describe his non-protesting, non-counterculture supporters in those turbulent years. Almost all Visual Basic 6 programmers were content with what Visual Basic 6 did. They were happy to be bus drivers: to leave the office at 5 p.m. (or 4:30 p.m. on a really nice day) instead of working until midnight; to play with their families on weekends instead of trudging back to the office; to sleep with their spouses instead of pulling another coding all-nighter and eating cold pizza for breakfast. They didn’t lament the lack of operator overloading or polymorphism in Visual Basic 6, so they didn’t say much.

    The voices that Microsoft heard, however, came from the 3 percent of Visual Basic 6 bus drivers who actively wished to become fighter pilots. These guys took the time to attend conferences, to post questions on CompuServe forums, to respond to articles. Not content to merely fantasize about shooting a Sidewinder missile up the tailpipe of the car that had just cut them off in traffic, they demanded that Microsoft install afterburners on their busses, along with missiles, countermeasures and a head-up display. And Microsoft did.

    But giving Visual Basic .NET to the Visual Basic 6 community was like raising a coyote as a domestic dog, then releasing him into the woods, shouting, “Hunt for your dinner as God intended, you magnificent, wild creature!” Most of them said, “Heck with that. I’m staying on my nice warm cushion by the fire while you open me a can of Alpo.” And Visual Basic 6 kept right on going.

    Visual Basic 6 was not without faults, of course. OnError Resume Next? If one thing croaks, just keep right on going and see what happens? Probably not the best idea. But the rapid (and therefore cheaper) development of limited (and therefore cheaper) applications by lower-skilled (and therefore cheaper) personnel is an important solution to a very large class of problems.

    LightSwitch is now trying to fill this niche, with mixed reviews (see bit.ly/n9crJj). It is, at best, a decade late.

    The things that Visual Basic 6 did still need doing. Until and unless Microsoft brings out another tool that does these things, Visual Basic 6 will keep scuttling around. I’ll bet you a beer that Microsoft has to extend Visual Basic 6 support through Windows 9 and 10."


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.


    • Edited by Mr. Monkeyboy Thursday, February 27, 2014 1:15 AM 5555
    Thursday, February 27, 2014 12:55 AM
  • Megan you actually gave Cor Ligthert a difficult time because he's from Germany and probably his primary language is not English? I think he uses English more effectively than many posters here. And I find his terminology and use of the english language rather refreshing. And hilarious a lot of the time. I've worked all over the world with engineers whos primary language was other than english that spoke english. They were just as capable as anybody else. Man you really are a Charlie Foxtrot.


    When you look at this why would Microsoft bother spending the money to bring back VB6? VB is certainly not a huge market requirement. And what portion of the VB in each image is for VB6 or less?

    Programming Language Popularity

    And this article says all I need to know.

    The Silent Majority: Why Visual Basic 6 Still Thrives

    @Mr. Monkeyboy 

    The market is huge for VB6, really huge ! Your "Programming Language Popularity" link is bias (I know of it), please look at how the data is interpreted. To see the reality, look at these links (and many others):

    http://www.theranking.com/what-is-the-best-programming-language-in-the-world_r55229
    http://www.theranking.com/what-is-the-best-programming-language-ever_r43672
    http://www.theranking.com/best-programing-language-in-the-world_r36102


    VB6 programmers are the best in the world! if you look at the VB6 open source projects you will realize this things. Preconceived ideas about VB6 should be avoided. It would be a shame for these open source projects not to see other platforms. A new VB6 will bring progress !



    Thursday, February 27, 2014 2:06 AM
  • You still haven't answered my question and I am sure you won't, because you can't.

    This is mildly amusing though, thanks for that.

    Thursday, February 27, 2014 2:16 AM
  • @Mr. Monkeyboy 

    The market is huge for VB6, really huge ! Your "Programming Language Popularity" link is bias (I know of it), please look at how the data is interpreted. To see the reality, look at these links (and many others):

    http://www.theranking.com/what-is-the-best-programming-language-in-the-world_r55229
    http://www.theranking.com/what-is-the-best-programming-language-ever_r43672
    http://www.theranking.com/best-programing-language-in-the-world_r36102


    VB6 programmers are the best in the world! if you look at the VB6 open source projects you will realize this things. Preconceived ideas about VB6 should be avoided. It would be a shame for these open source projects not to see other platforms. A new VB6 will bring progress !



    Yeah right. Those links are for people to vote what they think. Which in no way coincides with reality.

    It's like voting for singers on American Idol. Which from what I've read you can do as many times as you want.

    I imagine I could write a vb.net bot that could access your links and vote up VB.Net till it exceeds VB6.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.


    • Edited by Mr. Monkeyboy Thursday, February 27, 2014 3:03 AM 5555
    Thursday, February 27, 2014 3:02 AM
  • You still haven't answered my question and I am sure you won't, because you can't.

    This is mildly amusing though, thanks for that.

    Yes it does answer your question (not that your question really matters), only that you think you are smarter than you really are (or worse, you do not understand what I just gave you). 

    I just realized you do not know to do this! These projects can calculate a number (much bigger than your 7500 digits) with as many digits you wish (if you think this is a problem in VB6, it is NOT):

    http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=75226&lngWId=1

    http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=75227&lngWId=1

    What can I say, a pathetic request! I am convinced that you amuse yourself daily!






    Thursday, February 27, 2014 3:06 AM
  • @Mr. Monkeyboy 

    The market is huge for VB6, really huge ! Your "Programming Language Popularity" link is bias (I know of it), please look at how the data is interpreted. To see the reality, look at these links (and many others):

    http://www.theranking.com/what-is-the-best-programming-language-in-the-world_r55229
    http://www.theranking.com/what-is-the-best-programming-language-ever_r43672
    http://www.theranking.com/best-programing-language-in-the-world_r36102


    VB6 programmers are the best in the world! if you look at the VB6 open source projects you will realize this things. Preconceived ideas about VB6 should be avoided. It would be a shame for these open source projects not to see other platforms. A new VB6 will bring progress !



    Yeah right. Those links are for people to vote what they think. Which in no way coincides with reality.

    It's like voting for singers on American Idol. Which from what I've read you can do as many times as you want.

    I imagine I could write a vb.net bot that could access your links and vote up VB.Net till it exceeds VB6.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.


    I want to see that you do that! Please, change the ranking, I challenge you! ;)

    Nice animation :)


    Thursday, February 27, 2014 3:17 AM
  • Resposta à Devon Nullman:

    O que eu posso fazer em VB6 que você não poderá nunca fazer em dot net:

    Eu crio um executável e instalo o programa em uma HD sem sistema operacional.

    Eu então plugo a minha HD em qualquer máquina rodando windows.

    E eu simplesmente chamo o executável que eu criei em VB6 sem
    precisar fazer qualquer instalação de nada nada nada.

    Se eu desligar o micro e colocar a minha HD em outra máquina, com outra versão do windows,
    eu continuo executando meu aplicativo sem ter que novamente
    fazer qualquer instalação de nada, nada, nada.

    E você não vai conseguir decompilar meu executável.

    Faça isso em dot net.

    Além da RAD fantástica e inigualável, que me permite criar objetos
    enquanto eles são executados e funcionando ao mesmo tempo em que eu os crio.

    Sinto muito por você não saber que tudo isso não existe em dot net...

    Abraços


    Eugenio P. S. Canaan - ILT tecnologia - BR


    Thursday, February 27, 2014 3:18 AM
  • To Eugênio P. S. Canaan

    Finalmente, alguém pelo menos fala com bom senso. Isso não é exatamente o que eu queria dizer, mas sim que é verdade. O que eu ainda estou procurando é um código que pode ser criado em VB6 que é impossível duplicar em VB NET. Esta pessoa "Inverno" parece ser um especialista, por isso estou pedindo a ela, principalmente para explicar sua posição.

    Perdoe a tradução, estou em dívida com o Google Tradutor para Português

    Thursday, February 27, 2014 3:41 AM
  • Thursday, February 27, 2014 3:44 AM

  • Soon will not be so out of date! Therefore we require a new VB6 ! :)
    Thursday, February 27, 2014 3:50 AM
  • To Eugênio P. S. Canaan

    Finalmente, alguém pelo menos fala com bom senso. Isso não é exatamente o que eu queria dizer, mas sim que é verdade. O que eu ainda estou procurando é um código que pode ser criado em VB6 que é impossível duplicar em VB NET. Esta pessoa "Inverno" parece ser um especialista, por isso estou pedindo a ela, principalmente para explicar sua posição.

    Perdoe a tradução, estou em dívida com o Google Tradutor para Português

    I gave you a vote because you tried to answer Eugênio :) nice

    Thursday, February 27, 2014 3:54 AM
  • To Eugênio P. S. Canaan

    Finalmente, alguém pelo menos fala com bom senso. Isso não é exatamente o que eu queria dizer, mas sim que é verdade. O que eu ainda estou procurando é um código que pode ser criado em VB6 que é impossível duplicar em VB NET. Esta pessoa "Inverno" parece ser um especialista, por isso estou pedindo a ela, principalmente para explicar sua posição.

    Perdoe a tradução, estou em dívida com o Google Tradutor para Português


    Thank's for reply, i have little dificult to write social dialogs in english,
    but i understand the language.

    Eugenio P. S. Canaan - ILT tecnologia - BR

    Thursday, February 27, 2014 10:03 AM
  • Can you describe what VB6 does that cannot be done with VB .NET ?

    Devon,

    You are missing the point.

    If I say to you "show me something VB.NET does that C# can't", is that a reason for Microsoft to drop VB.NET ?

    (Actually Microsoft seem to be thinking it is, everyone can see that VB.NET takes a backseat to C# - there aren't even samples any more).



    • Edited by Sten2005 Thursday, February 27, 2014 11:03 AM
    Thursday, February 27, 2014 11:01 AM
  • Can you describe what VB6 does that cannot be done with VB .NET ?

    Devon,

    You are missing the point.

    If I say to you "show me something VB.NET does that C# can't", is that a reason for Microsoft to drop VB.NET ?

    (Actually Microsoft seem to be thinking it is, everyone can see that VB.NET takes a backseat to C# - there aren't even samples any more).



    No he was not, this thread has nothing to do with C#.

    So please leave that alone. 

    Karl or Mike, whoever it was started spamming old VB6 threads with all kind of links, therefore the account of him is removed from this forum.

     


    Success
    Cor

    Thursday, February 27, 2014 1:21 PM
  • Can you describe what VB6 does that cannot be done with VB .NET ?

    Devon,

    You are missing the point.

    If I say to you "show me something VB.NET does that C# can't", is that a reason for Microsoft to drop VB.NET ?

    (Actually Microsoft seem to be thinking it is, everyone can see that VB.NET takes a backseat to C# - there aren't even samples any more).



    No he was not, this thread has nothing to do with C#.

    So please leave that alone. 

    Karl or Mike, whoever it was started spamming old VB6 threads with all kind of links, therefore the account of him is removed from this forum.

     


    Success
    Cor

    Yes, Devon was missing the point. This thread is about VB6.  It was Devon who started asking what VB6 could do that a different language (VB.NET) couldn't.
    It is perfectly valid to extend that to asking why if some other language (C# in my example) could do everything that VB.NET can, would that be reason enough to can VB.NET ?
    (The answer, by the way, is "no it wouldn't").

    I also suspect Devon is capable of replying for himself.

    This forum does seem to have become very censorious.

    Thursday, February 27, 2014 2:01 PM
  • Karl or Mike, whoever it was started spamming old VB6 threads with all kind of links, therefore the account of him is removed from this forum.

     


    Success
    Cor

    I have never met Megan Winter, but I have no reason to suppose she is anything other than what she appears to be.

    Is your 'evidence' just Paul's comment:

    LOL! Mike is that you? Or, perhaps it's Karl? ;-)

    It would appear that we're are being invaded by a few of the old Classic VB guys, some of them possibly former MVPs, hiding behind names that are most likely not theirs. (Megan? Come on!)

    I wouldn't bother debating them since they're simply here to cause trouble.

    or do you actually have some proof ?

    If that is your reason for removing Megan Winter's account, that is shameful.

    What next ? Are you going to start burning VB6 books ?

    Thursday, February 27, 2014 2:27 PM
  • What do you guys think? I thought of a name: VBX.NET. Basically, this is an open source and/or extended version of VB.NET by the open source community. Much like torquecv or torque community edition is really an extension of torque that is so much better and improved (research it and you will see that torque died but it meant the community version died too. Very sad :(. This is not what I want of VB.NET). I would be more willing to do something like this. In addition, every month the TechNet guru competition has had some interesting articles from time to time written in VB.NET. I would like a VB.NET extension but no-one has made one. I say we decide on sections that groups of people would be willing to work on (i.e. mathematical functions, gaming (second hardest next to hardware programming), hardware programming, etc.). Then, we could standardize the language much like how computer networking standards are fixed in place and have changes from time to time once we know how it works. Heck, even the SQL language has been standardized how about time VB.NET did or let VB6 come back? That's why the SQL language is close to the same it was around 1999-2000 and works. I bet no-one knew that SQL server was open source and that's why it flourished at first.

    What we need to do is extend VB.NET to do what VB6 did plus more. Personally, I participate in a lot of beta tests ranging from Microsoft to very exclusive and private EA game betas. Making software for gaming and hardware is where you get the most people interested.


    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr






    • Edited by The Thinker Thursday, February 27, 2014 2:52 PM
    Thursday, February 27, 2014 2:42 PM
  • Can you describe what VB6 does that cannot be done with VB .NET ?

    Devon,

    You are missing the point.

    If I say to you "show me something VB.NET does that C# can't", is that a reason for Microsoft to drop VB.NET ?

    (Actually Microsoft seem to be thinking it is, everyone can see that VB.NET takes a backseat to C# - there aren't even samples any more).



    No he was not, this thread has nothing to do with C#.

    So please leave that alone. 

    Karl or Mike, whoever it was started spamming old VB6 threads with all kind of links, therefore the account of him is removed from this forum.

     


    Success
    Cor

    Yes, Devon was missing the point. This thread is about VB6.  It was Devon who started asking what VB6 could do that a different language (VB.NET) couldn't.
    It is perfectly valid to extend that to asking why if some other language (C# in my example) could do everything that VB.NET can, would that be reason enough to can VB.NET ?
    (The answer, by the way, is "no it wouldn't").

    I also suspect Devon is capable of replying for himself.

    This forum does seem to have become very censorious.

    Sten - this thread started with "Please reconsider introducing VB6 to the market. It is needed by many." To start with, this forum is supposed to be for people that have run into problems with their VB NET code and seek help. There is nobody here that could have any influence over Microsoft as far as bringing back VB6. One of the Sticky threads on the forum page in fact is titled "Where to post your VB 6 questions". I asked what can VB6 do that cannot be done in VB NET because to me, that might be one of the first things discussed at Microsoft if they were to consider bringing it back (which they won't IMO). So there were a few humorous replies, Cor pointed out that this is the wrong forum, then some folks started in with the "VB6 is better than VB NET", meanwhile I keep asking for an example of what can VB6 do that cannot be done in VB NET, and I get no useful answers until finally someone points out that VB6 programs can run almost anywhere, which is pretty accurate (there are msvbvmxx dll files if I remember correctly), but not exactly what I meant. In the meantime some posts started to get a bit personal, and all the time the original topic is ignored. The fact of it is this (In my opinion)

    Microsoft will NOT bring VB6 back in any form at all, no VB7, VB8, etc.

    .NET is going to be around a while, get used to it, get over it.

    .NET will eventually be replaced with something else and the cycle will repeat itself.

    If that is unacceptable, quit programming for Windows, or learn assembler which will never grow obsolete (j/k)

    Nobody is censoring anyone. As far as myself, I know that my question will never be answered and I no longer care. VB6 vs VB NET is not the same comparison as VB NET vs C# NET.

    Lastly - and this is truly a question - why does VB6 need to be brought back ? Does it not work with Windows 98, or XP, or Vista, or Win 7, or 8 ? I'm sure that somewhere it can be downloaded and I doubt that MS would go after someone for not buying it. One could certainly set up a development machine if it is that important, no ?

    Thursday, February 27, 2014 2:51 PM
  • What do you guys think? I thought of a name: VBX.NET. Basically, this is an open source and/or extended version of VB.NET by the open source community.


    Kind of funny that you chose VBX. This was the file extension of the old 16-bit control libraries that were developed for Visual Basic versions 1.0-3.0.

    Paul ~~~~ Microsoft MVP (Visual Basic)

    Thursday, February 27, 2014 2:55 PM
  • Can you describe what VB6 does that cannot be done with VB .NET ?

    Devon,

    You are missing the point.

    If I say to you "show me something VB.NET does that C# can't", is that a reason for Microsoft to drop VB.NET ?

    (Actually Microsoft seem to be thinking it is, everyone can see that VB.NET takes a backseat to C# - there aren't even samples any more).



    No he was not, this thread has nothing to do with C#.

    So please leave that alone. 

    Karl or Mike, whoever it was started spamming old VB6 threads with all kind of links, therefore the account of him is removed from this forum.

     


    Success
    Cor

    Yes, Devon was missing the point. This thread is about VB6.  It was Devon who started asking what VB6 could do that a different language (VB.NET) couldn't.
    It is perfectly valid to extend that to asking why if some other language (C# in my example) could do everything that VB.NET can, would that be reason enough to can VB.NET ?
    (The answer, by the way, is "no it wouldn't").

    I also suspect Devon is capable of replying for himself.

    This forum does seem to have become very censorious.

    Sten - this thread started with "Please reconsider introducing VB6 to the market. It is needed by many." To start with, this forum is supposed to be for people that have run into problems with their VB NET code and seek help. There is nobody here that could have any influence over Microsoft as far as bringing back VB6. One of the Sticky threads on the forum page in fact is titled "Where to post your VB 6 questions". I asked what can VB6 do that cannot be done in VB NET because to me, that might be one of the first things discussed at Microsoft if they were to consider bringing it back (which they won't IMO). So there were a few humorous replies, Cor pointed out that this is the wrong forum, then some folks started in with the "VB6 is better than VB NET", meanwhile I keep asking for an example of what can VB6 do that cannot be done in VB NET, and I get no useful answers until finally someone points out that VB6 programs can run almost anywhere, which is pretty accurate (there are msvbvmxx dll files if I remember correctly), but not exactly what I meant. In the meantime some posts started to get a bit personal, and all the time the original topic is ignored. The fact of it is this (In my opinion)

    Microsoft will NOT bring VB6 back in any form at all, no VB7, VB8, etc.

    .NET is going to be around a while, get used to it, get over it.

    .NET will eventually be replaced with something else and the cycle will repeat itself.

    If that is unacceptable, quit programming for Windows, or learn assembler which will never grow obsolete (j/k)

    Nobody is censoring anyone. As far as myself, I know that my question will never be answered and I no longer care. VB6 vs VB NET is not the same comparison as VB NET vs C# NET.

    Lastly - and this is truly a question - why does VB6 need to be brought back ? Does it not work with Windows 98, or XP, or Vista, or Win 7, or 8 ? I'm sure that somewhere it can be downloaded and I doubt that MS would go after someone for not buying it. One could certainly set up a development machine if it is that important, no ?

    Yes, we can extend VB.NET though and technically call it VBX.NET (might have some updated versions of VB6 functions hence VBX.NET) like torquex had a torquexcv version which was a community extended version of torquex. Standardization assures us that that certain pieces or sections of the programming language function the same on all computers and devices and that the useful functions are not removed (does not mean everything will survive but only the functions that help everyone and cause it to function properly on a new computer). Its a big leap but that's what serious programming languages do is get Standardized.


    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr



    • Edited by The Thinker Thursday, February 27, 2014 3:01 PM
    Thursday, February 27, 2014 2:59 PM
  • Megan account was removed because she started spamming many other threads about VB6 in the forum, ...

    It was certainly not about the identity of the User. Or because she like VB6

    Thursday, February 27, 2014 3:00 PM
  • What do you guys think? I thought of a name: VBX.NET. Basically, this is an open source and/or extended version of VB.NET by the open source community.


    Kind of funny that you chose VBX. This was the file extension of the old 16-bit control libraries that were developed for Visual Basic versions 1.0-3.0.

    Paul ~~~~ Microsoft MVP (Visual Basic)


    I thought VBX had some significance to the early versions of VB. :D Well, if anyone wants to build it I will create a new thread here so we can move discussion away from this thread. if we build it, people will come.

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr


    • Edited by The Thinker Thursday, February 27, 2014 3:32 PM
    Thursday, February 27, 2014 3:32 PM
  • The fact of it is this (In my opinion)

    Microsoft will NOT bring VB6 back in any form at all, no VB7, VB8, etc.

    .NET is going to be around a while, get used to it, get over it.

    .NET will eventually be replaced with something else and the cycle will repeat itself.

    If that is unacceptable, quit programming for Windows, or learn assembler which will never grow obsolete (j/k)

    Thanks for replying, Devon.

    Maybe Microsoft won't bring back VB6.
    But that is rather strange. VBA is the identical language to VB6. It is just in a different container (Word or Excel, instead of in the VB6 IDE). And Microsoft updated VBA6 to VBA7.
    There doesn't seem much sense in supporting the language in one format but not the other.

    And do you (or Microsoft) really think that VB6 coders who haven't migrated to VB.NET over the last 12 years (since .NET was launched) will do so now ?
    I prefer to take Microsoft's advice that the future is JavaScript and HTML.

    Nobody is censoring anyone. As far as myself, I know that my question will never be answered and I no longer care. VB6 vs VB NET is not the same comparison as VB NET vs C# NET.

    VB.NET is closer to C# than VB6 so I consider it a valid comparison. But my point wasn't to criticize VB.NET (or C#) it was to point out that comparing languages is largely meaningless (especially after you have written your code). The real answer to your question is that if you have legacy VB6 code, the thing VB.Net won't do is open it. So you face the choice of continuing with an 'old' language or converting it at considerable cost.

    As the Microsoft Program Manager for Visual Studio said "It isn't cost effective to keep rewriting code to get back to functional equivalence.".

    Lastly - and this is truly a question - why does VB6 need to be brought back ? Does it not work with Windows 98, or XP, or Vista, or Win 7, or 8 ? I'm sure that somewhere it can be downloaded and I doubt that MS would go after someone for not buying it. One could certainly set up a development machine if it is that important, no ?

    Why does VB6 need to be brought back?
    Well yes you are right we can manage perfectly well as things are. VB6 works on Windows 7, 8 and 8.1 and has 'it just works' support from Microsoft until 2023. It is likely to work on Windows 8.1.1 and Windows 9 and beyond too.
    But that doesn't mean that there aren't some improvements we'd like - such as the 64 bit features already added to VBA7.  Both VB6 and VBA use the Visual Basic Runtime Library so it should be relatively easy to add this.
    There is a vibrant developer community for VB6 (I checked another forum a few minutes ago, there were just over 600 viewers of the VB.NET forum online and 550 viewers of the VB6 forum).  According to the Tiobe index VB6 is #7 in the list of most popular languages, VB.NET has reached its highest ever position - #10.  Many corporates have systems written in VB6 (to Microsoft's credit they have recognized this with the extension of "it just works" support).
      The community has already added many features, but you can't do everything without having access to the VB6 source code (open sourcing would be a solution, but I think that is even less likely than a return of VB6).

    I don't believe you can legally download VB6 and it is getting harder to buy old copies (Ebay's prices have increased now (I quoted VB6 professional at over $400 earlier, others cost even more). It would be good if either Microsoft sold it again or announced it could be freely downloaded - I'd like to take your assurance that Microsoft "wouldn't go after someone" but really it needs them to say that. 

    Thursday, February 27, 2014 4:15 PM
  • Somehow difficult to tell to you guys. But let me try it in an analogy.

    VB Net is used in the same way like persons who talk about the USA as America and about Europe about the EU. 

    However, unlike America and Europe does VB Net not exist as product anymore. The current product is VB12 included in Visual Studio 2013 but often also called for simplisity Visual Basic 2013.

    VB Net was the same as language version VB7.0 and had the product name VB.Net. Version 7.1 got the name 2003 Net and with version 2005 it Net was not anymore in the name.

    Some older ones among you should remember that VB6 was available in Visual studio '98, the way 1998 was then written.

    There were however who did not want to change anything and wanted to go on for instance with Win '95.

    The only possibility where VB6 could be used is by the way Windows Forms, Windows Services and Console. The web part failed in a tremendous way and was quick drawn back.

    Com was at its end in those days Internet and Mobile started and had to be replaced, and Microsoft did and was able to go on.

     


    Success
    Cor



    • Edited by Cor Ligthert Thursday, February 27, 2014 4:19 PM
    Thursday, February 27, 2014 4:16 PM
  • Megan account was removed because she started spamming many other threads about VB6 in the forum, ...

    It was certainly not about the identity of the User. Or because she like VB6

    I'm happy to accept that, Crazypennie.

    But do remember people can get quite emotional. I didn't see much wrong with what Megan posted other than her obvious passion about VB6 (and passion is hardly a fault).

    Wasn't there anything else you could have done, short of removing her account and all her posts ?


    Thursday, February 27, 2014 4:42 PM
  • I figure Megan was an Imposter made up by someone to stir a pot since nothing posted by Megan was factual in any way, shape or form.

    But I still wanted to show Megan this.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.

    Thursday, February 27, 2014 4:48 PM
  • I'm happy to accept that, Crazypennie.

    But do remember people can get quite emotional. I didn't see much wrong with what Megan posted other than her obvious passion about VB6 (and passion is hardly a fault).

    Wasn't there anything else you could have done, short of removing her account and all her posts ?


    Nothing she posted or linked had any factual basis. Or did you bother reading any of it and actually understanding that?

    I say the Ford Pinto is faster than an Indy car. You can believe that too!


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.

    Thursday, February 27, 2014 4:58 PM
  • I figure Megan was an Imposter made up by someone to stir a pot since nothing posted by Megan was factual in any way, shape or form.

    But I still wanted to show Megan this.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.

    Well done, Monkeyboy. It looks like you have mastered 'cut and paste'

    Tomorrow we'll teach you basic keyboard skills.

    Thursday, February 27, 2014 5:00 PM
  • "Well done, Monkeyboy. It looks like you have mastered 'cut and paste'

    Tomorrow we'll teach you basic keyboard skills."

    Who's we? You and your army of black belt coders? LOL.

    Who's the Master of keyboard skills?

    So when your done writing the below app in VB6 let me know OBI WAN, signed YODA.


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.



    • Edited by Mr. Monkeyboy Thursday, February 27, 2014 5:50 PM 5555
    Thursday, February 27, 2014 5:48 PM
  • Sten - you wrote "The real answer to your question is that if you have legacy VB6 code, the thing VB.Net won't do is open it." - That is why I keep Visual Basic 2008 Express Edition on hand. It saves a lot of typing and form design. Of course sometimes things must be fixed, and sometimes it is best to just start over.

    Perhaps you should petition MS to open source the entire VB6 suite, worst they could say is "No". I don't see how it could hurt them but they might not want to share anything about the IDE at all, no matter how old it is.

    Thursday, February 27, 2014 6:03 PM
  • Hmmm.. Why all the hate for VB6? Are you afraid if it would be supported again that VB.NET would be dead?

    VB6 and VB.NET are completely different tools..

    I myself like the simplicity of VB6, having developed in many different languages I still like VB6.. Everytime when I do stuff in .NET I wonder what some of the designers of the framework were thinking, but at other times I would love to have some of the features in VB6 (those are few though).. You can't tell me for instance that the ribbonbar is a well designed component (it's the most utter crap I have ever had the displeasure to had to work with, whoever designed that should have been fired at the spot)..

    MS did keep unmanaged C++, so why didn't they keep unmanaged VB? Why would I need to rewrite my VB6 application which is working perfectly on all current Windows (from 95 to 8) and is also using a lot of the latest technology..

    Biggest problem I have is the fact the VB6 IDE isn't working that well with the latest versions of windows, once you've got it running it'll run good enough.. Also the other problem I have is the limited ammount of different variable/function names one can have in one project (I just hate/despise OCX and a lot of different DLL's if all I have is one application), that would be the first thing I would change about VB6, remove the limitation, and the next thing would be support for unsigned integers (never understood why it wasn't present), also 64bit support would be nice..

    MS already had a real VB7 which was appearantly also pretty feature ready but was scrapped at the last minute in favor of VB.NET.. So why not just fix VB7 up and release it, or even better, open source it (that'll never happen ofcourse, but one never knows, MS supports open source better these days)..

    Saying VB6 should just die, only shows how narrowminded you as a developer are, remember, you don't have to use it if you don't want to... I don't want to spend millions of dollars and months/years of development just to port my already perfectly working application to VB.NET with no real extra advantages.. especially with the mindset of Microsoft, you never know if the framework you are using isn't dumped by MS a year later (just look at Silverlight for instance)..

    Thursday, February 27, 2014 6:55 PM
  • Hi Devon,

    I'd be happy if Microsoft open sourced VB6.  But as I pointed out VB6 uses VBA. And VBA is still a current and supported Microsoft language (in Microsoft Office).  I can't really see them open sourcing it.

    And, as you say, they may not want to release the IDE.

    Converting is manageable for small programs (I usually use VS2005), but it is almost as easy to re-write.

    But if you have a large VB6 application (say 100,000 lines or more) Microsoft's official advice is "Do nothing if your application is working great, it has not required any changes for many years, there are no plans to extend the functionality, nor a need to integrate it with newer applications."  That's fine, but real life software needs the occasional modification or enhancement. Microsoft don't really have a suggestion for that.
    If it is a major change, such as providing a web version of the application, I choose to re-write in a non-Microsoft language - such as JavaScript.

    Thursday, February 27, 2014 7:10 PM
  • Who is saying that VB6 should die? - many of the comments here are stating a fact, namely that in the eyes of Microsoft, it is long since dead. I really doubt that any discussions have taken place in Redmond in a long time regarding reviving/continuing VB6 as a Development Tool.

    You say that you have applications that would cost millions of dollars and months/years to port, those must be some huge projects. I'd love to see specific references to some of them. If the VB6 IDE is not working well in Vista/7/8, why not have a development machine with 98 or XP ? That seems like nothing more than an annoyance to me, especially if the alternative is porting over at a huge cost.

    As I replied to another person here, get as many VB6 developers as you can to sign a petition to Microsoft to open source VB6, worst they can do is say "Nope, not happening"

    Thursday, February 27, 2014 7:22 PM
  • Thats a shame, I enjoyed the chitchating with a Visual Basic 6 fundamentalist.  I actually logged into this page to check out what she was raving about and found it interesting.  Could we not give her access just to a VB Fundamentalist blog to see where she ends up?

    Dave Matthews

    Thursday, February 27, 2014 8:10 PM
  • What do you guys think? I thought of a name: VBX.NET. Basically, this is an open source and/or extended version of VB.NET by the open source community.


    Kind of funny that you chose VBX. This was the file extension of the old 16-bit control libraries that were developed for Visual Basic versions 1.0-3.0.

    Paul ~~~~ Microsoft MVP (Visual Basic)


    I thought VBX had some significance to the early versions of VB. :D Well, if anyone wants to build it I will create a new thread here so we can move discussion away from this thread. if we build it, people will come.

    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr


    I sure hope you know I meant VBX.NET which would be an extension of VB.NET. I have seen people extending built-in libraries in VB.NET and C#. Anyone want to extend? Its sad that so many people have developed nice libraries in VB.NET too that no-one knew about. I found this wifi library that was so cool which worked with VB.NET: http://managedwifi.codeplex.com/  (looks like people found his or her page and downloaded programs and source code). I was amazed at how simple, easy to use, and that it was functional without hours of coding. The real problem is no-one knows about the many items available to the outside world. Anyone in favor of a codeplex page? If I knew people would join I would create one myself, extend VB.NET, make articles with different code, and invite people to do the same.



    Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog - http://www.computerprofessions.co.nr




    • Edited by The Thinker Thursday, February 27, 2014 10:27 PM
    Thursday, February 27, 2014 10:03 PM
  • I myself like the simplicity of VB6, having developed in many different languages I still like VB6.. Everytime when I do stuff in .NET I wonder what some of the designers of the framework were thinking, but at other times I would love to have some of the features in VB6 (those are few though).. You can't tell me for instance that the ribbonbar is a well designed component (it's the most utter crap I have ever had the displeasure to had to work with, whoever designed that should have been fired at the spot)..

    VB6 may be simple in some ways, but in others it's not.  For example, it requires 2 lines of code to declare and assign a string:

    Dim s As String
    s = "Hello World"

    It would be nice to be able to type just this:

    Dim s As String = "Hello World"

    Some of the things VB6 requires to you do are silly.  For example, if you call a Sub, you call it without using parentheses for the argument list

    SomeSub arg1, arg2, arg3

    But for a Function, you have to use parens!  You can call a Function without using parens if you use the Call keyword.  

    Having to use Set when assigning an object versus not when assigning a primitive type...


    VB.Net, as a language, is far superior to VB6 in my opinion.  It has object oriented development, support for generics, lambdas, namespaces, static methods, extension methods, structured exception handling (seh), collection initializers, query expressions (LINQ), Xml literals, implicit line continuation, etc.   VB6 as a language is frustrating to use to say the least!  (IMO).  


    I don't want to spend millions of dollars and months/years of development just to port my already perfectly working application to VB.NET with no real extra advantages.. especially with the mindset of Microsoft, you never know if the framework you are using isn't dumped by MS a year later (just look at Silverlight for instance)..

    You realize that VB.Net has been around for 12 years?  VB Classic was only around for 11 when the first versions of VB.Net were released.  The argument that MS might suddenly pull the plug on VB.Net, in my opinion, is no longer valid.

    I don't advocate for the death of VB6, it surely is appropriate for maintaining existing applications, but for new applications, choosing VB6 is not a wise decision in my opinion.

    Thursday, February 27, 2014 11:47 PM
  • But if you have a large VB6 application (say 100,000 lines or more) Microsoft's official advice is "Do nothing if your application is working great, it has not required any changes for many years, there are no plans to extend the functionality, nor a need to integrate it with newer applications."  That's fine, but real life software needs the occasional modification or enhancement. Microsoft don't really have a suggestion for that.

    Frankly, that's the fault of the organization who owns the app, not Microsoft's.  If, as an organization, you wish to be able to maintain and possibly enhance a large and important application, then you should definitely keep the appropriate tools and hardware around to do so if you don't want to port to newer tools.  If you have that large of a VB6 app, then what happened to the software that was used to create it?  Did it evaporate?  Surely there must be a CD stored somewhere.  When you buy software for your organization, it should be treated as an asset and stored and backed up appropriately.  And if moderns versions of the OS render the tool useless, then you should keep an older version of the OS around for development.  

    As you may be aware, VB6 Enterprise Edition is still available from Microsoft via almost all of their MSDN subscriptions, many of which are inexpensive. A BizSpark subscription (which includes VB6) is free for startups that meet certain requirements.  

    Friday, February 28, 2014 12:00 AM
  • VB6 may be simple in some ways, but in others it's not.  For example, it requires 2 lines of code to declare and assign a string: 

    Dim s As String
    s = "Hello World"

    It would be nice to be able to type just this:

    Dim s As String = "Hello World"

    Some of the things VB6 requires to you do are silly.  For example, if you call a Sub, you call it without using parentheses for the argument list

    SomeSub arg1, arg2, arg3

    But for a Function, you have to use parens!  You can call a Function without using parens if you use the Call keyword.  

    Having to use Set when assigning an object versus not when assigning a primitive type...

    Well, I think those aren't weird things, you can just as much use parens on subs if you want to.. Also yes it's nice if you can assign a new value immediatly, but is it necessary and always better? And having to use set vs not is not a bad thing IMHO, it just makes sure you know what you are doing.. (and let's not forget using set or not on an object are 2 different things).

    VB.Net, as a language, is far superior to VB6 in my opinion.  It has object oriented development, support for generics, lambdas, namespaces, static methods, extension methods, structured exception handling (seh), collection initializers, query expressions (LINQ), Xml literals, implicit line continuation, etc.   VB6 as a language is frustrating to use to say the least!  (IMO).  

    Yes you might call is superior, I call it bloated.. Yes it's nice to have some of those functions, but do you reall need them? we didn't need them for 40 years so why should you really need them now.. Those functions like lambda's (which are just functions without a name, nothing more, nothing less) are just for lazy developers IMHO (and certainly don't make your code more readable/better). also implicit line continuation was only introduced in 2010, and also IMHO not something that you really need.. Also let's not forget a lot of stuff you mention is framework and if you really want to you can do/build them also with VB6.. All I can really give you with the above is the Structured exception handling, it's more clean, and the better OO, but even the better OO isn't making sure you get a better application..

    VB.Net, as a language, is far superior to VB6 in my opinion.  It has object oriented development, support for generics, lambdas, namespaces, static methods, extension methods, structured exception handling (seh), collection initializers, query expressions (LINQ), Xml literals, implicit line continuation, etc.   VB6 as a language is frustrating to use to say the least!  (IMO).  

     

    You realize that VB.Net has been around for 12 years?  VB Classic was only around for 11 when the first versions of VB.Net were released.  The argument that MS might suddenly pull the plug on VB.Net, in my opinion, is no longer valid.

    I don't advocate for the death of VB6, it surely is appropriate for maintaining existing applications, but for new applications, choosing VB6 is not a wise decision in my opinion.

    You forget that if you want to keep up with VB.NET and the latest framework you HAVE to buy the newest visual studio (which seems to increase in price lately).. and MS already showed it does dump .NET stuff (framework 1 doesn't install on newer systems anymore) or just look at Silverlight and WPF (both are dumped)..

    And yet, my VB6 application is still running after 16 years and is still using a lot of the latest technologies..

    Ofcourse when I start a new project I won't start it in VB6, but I'll certainly look for something that has better multiplatform support and is already longer on the market.. Seems like the only tool that actually still works for all those years is delphi (or C++)..

    Friday, February 28, 2014 9:28 AM
  • In the way you write it, I advice you to look at this tool, not bad at all.

    And it exist much longer than VB6 and is still used.


    Success
    Cor

    Friday, February 28, 2014 10:00 AM
  • I still liked my analog computer from American Science projects Kit of the Month Club. It didn't require any language and was easy to program! No VB6, No .Net! Bring back the old days damnit all man! And it still works (well it would if I still had it).


    Please BEWARE that I have NO EXPERIENCE and NO EXPERTISE and probably onset of DEMENTIA which may affect my answers! Also, I've been told by an expert, that when you post an image it clutters up the thread and mysteriously, over time, the link to the image will somehow become "unstable" or something to that effect. :) I can only surmise that is due to Global Warming of the threads.

    Friday, February 28, 2014 12:20 PM
  • The very first programmable computer was designed by Charles Babbage. 

    And it was Ada Lovelance (world's first programmer) who encoded it to tabulate polynomial function

    It is at the London Science Museum ... and still works !

    Friday, February 28, 2014 2:14 PM
  • But if you have a large VB6 application (say 100,000 lines or more) Microsoft's official advice is "Do nothing if your application is working great, it has not required any changes for many years, there are no plans to extend the functionality, nor a need to integrate it with newer applications."  That's fine, but real life software needs the occasional modification or enhancement. Microsoft don't really have a suggestion for that.

    Frankly, that's the fault of the organization who owns the app, not Microsoft's.  If, as an organization, you wish to be able to maintain and possibly enhance a large and important application, then you should definitely keep the appropriate tools and hardware around to do so if you don't want to port to newer tools.  If you have that large of a VB6 app, then what happened to the software that was used to create it?  Did it evaporate?  Surely there must be a CD stored somewhere.  When you buy software for your organization, it should be treated as an asset and stored and backed up appropriately.  And if moderns versions of the OS render the tool useless, then you should keep an older version of the OS around for development.  

    As you may be aware, VB6 Enterprise Edition is still available from Microsoft via almost all of their MSDN subscriptions, many of which are inexpensive. A BizSpark subscription (which includes VB6) is free for startups that meet certain requirements.  

    No one is suggesting that backup copies and tools haven't been kept. Of course they have. And VB6 is still in regular use.

    The point was that Microsoft effectively offer 2 options - (1) If you don't need any modifications leave your code in VB6; (2) If you need modifications migrate to VB.NET.

    But the most likely scenario is that you need slight modifications - where is the sense in migrating a 100,000 line VB6 app if all you need to do (for example) is increase the size of a text field. Yet this scenario isn't addressed by Microsoft.  The obvious answer is that you use VB6. Yet MS tell you the IDE doesn't run on Windows 7 or 8 (actually it is fine).

    VB6 and VBA are (virtually) identical languages. VB6 actually uses VBA to define the language.
    Microsoft continue to support the language when it is hosted in Office (such as in Word or Excel) but refuse to support it when it is hosted in the VB6 IDE.

    Microsoft say VBA will be supported for the foreseeable future stating "This means that if you have an existing VBA project that you are satisfied with, you can be confident your investment is safe". Where is the sense in having this for VBA but not VB6 ? They assure you your VBA investment is safe but won't give the same assurance for your VB6 investment.

    By the way, thanks for the BizSpark info but I'm not sure there are many organisations with large scale VB6 applications that are also 'startups' and would qualify for a BizSpark subscription.

    Friday, February 28, 2014 2:26 PM
  • This thread is off topic for this forum, contains little valuable information on either language, and is full of flaming and childish replies.

    Moving to off-topic; you can continue the discussion in that forum if you wish.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    Friday, February 28, 2014 2:37 PM
  • The very first programmable computer was designed by Charles Babbage. 

    And it was Ada Lovelance (world's first programmer) who encoded it to tabulate polynomial function

    It is at the London Science Museum ... and still works !

    Ada Lovelace did indeed work on Babbage's analytical engine, though she died young and never got to see a completed engine. The engine had punched card input and a printer !

    Ada, of course, was the daughter of the poet Lord Byron.  The programming language 'Ada' was named for her.

    Ada's achievements are even more exceptional given the attitudes of Victorian Britain towards 'intellectual' women.

    Friday, February 28, 2014 2:58 PM
  • This thread is off topic for this forum, contains little valuable information on either language, and is full of flaming and childish replies.

    Moving to off-topic; you can continue the discussion in that forum if you wish.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    Looks like you are back to censoring again.

    The thread is only about one language, VB6, though some posters may insist on mentioning others.

    This is actually an interesting and informative topic. If you have issues with some posters then don't act against the rest of us.

    And the forum it is (was) in is the most relevant.

    Friday, February 28, 2014 3:06 PM

  • No one is suggesting that backup copies and tools haven't been kept. Of course they have. And VB6 is still in regular use.

    The point was that Microsoft effectively offer 2 options - (1) If you don't need any modifications leave your code in VB6; (2) If you need modifications migrate to VB.NET.

    But the most likely scenario is that you need slight modifications - where is the sense in migrating a 100,000 line VB6 app if all you need to do (for example) is increase the size of a text field. Yet this scenario isn't addressed by Microsoft.  The obvious answer is that you use VB6. Yet MS tell you the IDE doesn't run on Windows 7 or 8 (actually it is fine).

    VB6 and VBA are (virtually) identical languages. VB6 actually uses VBA to define the language.
    Microsoft continue to support the language when it is hosted in Office (such as in Word or Excel) but refuse to support it when it is hosted in the VB6 IDE.

    Microsoft say VBA will be supported for the foreseeable future stating "This means that if you have an existing VBA project that you are satisfied with, you can be confident your investment is safe". Where is the sense in having this for VBA but not VB6 ? They assure you your VBA investment is safe but won't give the same assurance for your VB6 investment.

    By the way, thanks for the BizSpark info but I'm not sure there are many organisations with large scale VB6 applications that are also 'startups' and would qualify for a BizSpark subscription.

    All this makes no sens to me

    It is easy today to find someone to service a VB6 application ... Everybody I know has a copy of it.

    And I am sure that it will be possible to have a VB6 application serviced for at least 10 more years.

    In 10 years from now, it will be a 20 years old application, ... Well how long can someone expect it's application to last. 

    ----

    Sure, some people has created new software with VB6 in the last few years, and still does, but those who did and still do that just don't care about the client investment because they know that it will be a problem and just tell to themself "It is not gonna be my problem".   

    Friday, February 28, 2014 3:09 PM
  • All this makes no sens to me


    Which bit didn't you understand, Crazypennie? I'll be happy to explain further.

    Is it the bit about Microsoft supporting the language when it is named VBA but not when it is named VB6 ?

    I must admit that has never made sense to me either.

    Friday, February 28, 2014 3:34 PM
  • All this makes no sens to me


    Which bit didn't you understand, Crazypennie? I'll be happy to explain further.

    Is it the bit about Microsoft supporting the language when it is named VBA but not when it is named VB6 ?

    I must admit that has never made sense to me either.

    I bought Office 2013 one month ago and the programming language in it is VBA .... I hope they do support the language more than a month !!

    It may not be the same thing VB6 that I bought something like 12 years ago

    Friday, February 28, 2014 3:53 PM
  • Saying VB6 should just die, only shows how narrowminded you as a developer are, remember, you don't have to use it if you don't want to... I don't want to spend millions of dollars and months/years of development just to port my already perfectly working application to VB.NET with no real extra advantages.. especially with the mindset of Microsoft, you never know if the framework you are using isn't dumped by MS a year later (just look at Silverlight for instance)..

    My boat exactly. When forced to port I will never use Microshaft based languages or frameworks.

    Reading many of the posts here miss part of the point. VB.NET I am sure is a fine language. VB6 implemented real work flows for people with real solutions. Converting from VB6 to VB.NET is akin to changing a C to some new version of C that removed the &&, multiplier operators, switch statements and calling it C.NET.

    Friday, February 28, 2014 3:59 PM
  • I bought Office 2013 one month ago and the programming language in it is VBA .... I hope they do support the language more than a month !!

    It may not be the same thing VB6 that I bought something like 12 years ago

    Have a look at the VBA language, you'll find it is exactly the same as VB6 !

    (OK, if you install Office as 64 bit you'll see you have a 'longlong' variable and a 'safeptr' now).

    In fact you can cut and paste code between VB6 and VBA (and vice-versa). It is the same !

    I've even heard people say they like VBA but that VB6 is cr*p/obsolete/useless. It always makes me laugh, they are identical.

    Don't worry about your Office 2013, Microsoft are committed to supporting VBA for the foreseeable future.

    Friday, February 28, 2014 4:03 PM
  • At our company all our end-user setup programs (3 of them) would need recoding. A lot of them depend on near real-time requirements. We would also have to recode all our production systems (uses the common libraries and objects developed for user apps). This would amount to more than 10 applications. Some are on legacy products we still sell for existing customers with long term projects. Recoding these is clearly a dead end for us.

    We are smart and could do it. They were all pretty well written. Our ROI on these projects would be very negative.

    I am sure there are a lot of MS customers in our camp, waiting for someone sane at MS to give us a viable next generation for our code.

    Friday, February 28, 2014 4:05 PM
  • At our company all our end-user setup programs (3 of them) would need recoding. A lot of them depend on near real-time requirements. We would also have to recode all our production systems (uses the common libraries and objects developed for user apps). This would amount to more than 10 applications. Some are on legacy products we still sell for existing customers with long term projects. Recoding these is clearly a dead end for us.

    We are smart and could do it. They were all pretty well written. Our ROI on these projects would be very negative.

    I am sure there are a lot of MS customers in our camp, waiting for someone sane at MS to give us a viable next generation for our code.

    Exactly that Dave.

    Many people on this forum and others will tell you that VB.NET (or whatever their favorite is) is newer/more advanced/bigger/smaller or whatever. They  have probably never read the comment of Microsoft's Program Manager for  Visual Studio "It isn't cost effective to keep rewriting code to get back to functional equivalence. "

    Vote for an Updated VB6

    Friday, February 28, 2014 4:54 PM
  • compile a exe that cannot be decompiled !
    Friday, February 28, 2014 6:32 PM
  • Yes it's nice to have some of those functions, but do you reall need them? we didn't need them for 40 years so why should you really need them now..

    It's not about need, it's about making things easier. Why use a socket wrench when a regular wrench has worked for many years. You don't really need a socket wrench. Why use power tools when regular manual tools have been around for a long time. You don't really need power tools. Why use an IDE for writing programs when a simple text editor would work? An IDE is not really needed.
    Those functions like lambda's (which are just functions without a name, nothing more, nothing less) are just for lazy developers IMHO (and certainly don't make your code more readable/better). also implicit line continuation was only introduced in 2010, and also IMHO not something that you really need..

    Is it lazy to want to make things easier? I agree that lambdas can be difficult to read, but like any tool when used properly can save a lot of time and effor.
    Also let's not forget a lot of stuff you mention is framework and if you really want to you can do/build them also with VB6

    All of those features that I listed are part of the VB.Net language and are defined in the language spec. Obviously, they need the appropriate framework support. I don't see how you can do any of those things with VB6 in its current state.
    All I can really give you with the above is the Structured exception handling, it's more clean, and the better OO, but even the better OO isn't making sure you get a better application..


    It is not the tool that makes good programs, but the developer. That's why I read arguments that VB6 is faster than VB.Net with skepticism because they usually don't give any details about how the programs were written and just make a blanket assumption which most of the time is greatly exaggerated. Can VB6 programs run faster than a VB.Net program? Yes, but if programmed properly, I maintain that any VB.Net program can be just as fast as any VB6 program or faster. There, of course, might be exceptions.

    You forget that if you want to keep up with VB.NET and the latest framework you HAVE to buy the newest visual studio (which seems to increase in price lately)..


    Since the very first version of .Net up to the present version, all of the compilers and files needed to create any application are free. You can develop any application possible with .Net without purchasing any version of Visual Studio. The Express versions of VS are free and can be used to develop any application as well. The versions of VS that you must pay for have some features that are nice and make some things easier, but there is no application that the paid version can create that cannot also be created with VS Express or using the compilers provided with the framework.
    Friday, February 28, 2014 6:53 PM
  • "Can you describe what VB6 does that cannot be done with VB .NET ?"

    On the computer that I am using, VB. NET Express seems to behave rather slowly compared to VB6.
    Also, I am presently having difficulty adjusting to the VB.NET language syntax which seems rather illogical from a beginner's perspective.

    How many lines of code would you need to execute the following code in VB.NET?

    Private Sub Command1_Click()
       Picture1.Pset(9,8), vbBlue
    End Sub

    I like the VB6 syntax for its simplicity but could use VB.NET Express later if I'll be able to purchase a faster computer later on.

    Saturday, March 1, 2014 6:55 AM
  • >"Can you describe what VB6 does that cannot be done with VB .NET ?"

    Yes, VB6 can compile my 150,000 lines of code, vb.net can not.

    Regards W. Wolf

    Saturday, March 1, 2014 8:42 AM
  • >"Can you describe what VB6 does that cannot be done with VB .NET ?"

    Yes, VB6 can compile my 150,000 lines of code, vb.net can not.

    Regards W. Wolf

    FANTASTIC !!!

    EXACTLY !!!

    PERFECT !!!

    Rindo alto aqui. É tudo o que precisava ser dito !!!


    Eugenio P. S. Canaan - ILT tecnologia - BR

    Saturday, March 1, 2014 11:39 AM
  • >"Can you describe what VB6 does that cannot be done with VB .NET ?"

    Yes, VB6 can compile my 150,000 lines of code, vb.net can not.

    Regards W. Wolf

    I'm sure a .Netter will be along shortly to explain that being able to type

    Dim s As String = "Hello World"

    Is far more important than being able compile 150,000 lines.


    Saturday, March 1, 2014 3:45 PM
  • "Can you describe what VB6 does that cannot be done with VB .NET ?"

    On the computer that I am using, VB. NET Express seems to behave rather slowly compared to VB6.
    Also, I am presently having difficulty adjusting to the VB.NET language syntax which seems rather illogical from a beginner's perspective.

    How many lines of code would you need to execute the following code in VB.NET?

    Private Sub Command1_Click()
       Picture1.Pset(9,8), vbBlue
    End Sub

    I like the VB6 syntax for its simplicity but could use VB.NET Express later if I'll be able to purchase a faster computer later on.

    As Paul Yuknewicz, Microsoft's Program Manager for Visual Studio said "VB6 is still the product to beat in performance".

    Saturday, March 1, 2014 4:02 PM
  • Welcome back Megan

    Visual Studio team (Product Team, Microsoft) commented · March 06, 2014 18:59 ·

    @MeganWinter, we looked into why you were banned on Forums and you should not have been. We have unbanned you and will further investigate internally as to why this ban took place. We are tremendously sorry and apologize for any inconvenience in which this has caused.

    Nice to have you back.

    Thursday, March 6, 2014 8:02 PM
  • >

    I'm sure a .Netter will be along shortly to explain that being able to type

    Dim s As String = "Hello World"

    I write:

    Dim s As String: s = "Hello World"

    this is 2 characters more. With this i have no problem.

    Regards W. Wolf

    Friday, March 7, 2014 5:55 PM
  • >"Can you describe what VB6 does that cannot be done with VB .NET ?"

    Yes, VB6 can compile my 150,000 lines of code, vb.net can not.

    Regards W. Wolf

    I'm sure a .Netter will be along shortly to explain that being able to type

    Dim s As String = "Hello World"

    Is far more important than being able compile 150,000 lines.


    In current VB12 you can write (that is already a long while)

    Dim s = "Hello World" it infers "Hello World" and finds that it can be only a string.

    In the VB6 version (also in VB7) it was compiled too a variant (or object) because there was no inferring done.

    This kind of removing all not necessary things and the addition of OOP and therefore making reusing more easy, did result that in current versions of VB the programs are not anymore 150,000 lines but can often easily be done in 15,000 lines.

    However, be aware that in current versions of VB you can do things, in VB6 you must do things. The way it was done in VB6 is still possible.


    Success
    Cor





    Saturday, March 8, 2014 8:36 AM
  • Você acha mesmo, sr. Cor Ligthert, que se eu lhe der 50 aplicativos com 80 mil linhas cada,
    aplicativos de todo tipo, programas para estacionamento, lanchonetes, livrarias, postos de gasolina,
    controle de acesso, imobiliárias, condomínios, clínicas médicas, todos compilando no excelente compilador
    que o VB6 tem, que o senhor conseguirá reduzir meu código enxuto e muito bem elaborado,
    para 8 mil linhas em cada um ????

    Seja um homem sério: além de viver com medo da descompilação, a falta de performance,
    a troca de versão de framework antes mesmo de o tempo de maturação do aplicativo ser realizada...
    a necessidade de instalação da framework no sistema, as incompatibilidades, os erros de todo tipo
    que a gente cruza ao longo de toda a vida útil do programa...

    Você está mesmo acreditando que um programa com 15 mil linha feito em dot net VALE O MESMO valor
    que um programa feito em VB6 de 150 mil linhas ???

    Desculpe-me, você não sabe o que está dizendo...
    inclusive porque em VB6 eu definia S="Texto" sem ter que escrever DIM nenhum.
    Você foi enganado e não percebeu em 15 anos, vai perceber agora ???




    You think so, sir Cor Ligthert that if I give you 50 applications with 80 000 lines each ,
    all kinds of applications , programs, parking , coffee shops , bookstores , gas stations ,
    access control , real estate , condominiums , medical clinics , all in excellent compiling compiler
    that has VB6 , that you will be able to reduce my lean and well designed code,
    8 thousand lines in each ? ?

    Is a serious man : in addition to living in fear of decompilation , lack of performance ,
    exchange versioning framework even before the maturity time of the application to be performed ...
    the need for installation of the system framework , incompatibilities , errors of all kinds
    we cross over the lifetime of the program ...

    Are you really believing that a program with 15,000 line made ​​in dot net worth the same value
    a program done in VB6 150 thousand lines ? ?

    Excuse me , you do not know what you're saying ...
    Largely because in VB6 I defined S = " text " without having to write any DIM .
    You were fooled and did not realize in 15 years , will realize now? ?


    Eugenio P. S. Canaan - ILT tecnologia - BR

    Saturday, March 8, 2014 12:03 PM
  • Hello Eugenio,

    What do you think if you have bought a machine in 1998. At a certain moment its at its technical end. 

    Maybe it is still functioning, but your competitors do the same for a 10th of the price. 

    Do you think it is clever from Microsoft still selling those machines or/and their parts, and even do marketing and give a bad experience about Microsoft products? (Before you tell it, yes I know about Windows 8, but in the case of VB6 it was easier to foreseen.)

    If there was still a market for a program language like VB6, somebody would make it. 


    Success
    Cor

    Saturday, March 8, 2014 1:23 PM
  • Hello Cor Ligthert

    Eu não acho que tenho que continuar usando um produto velho, você entendeu isso corretamente.
    Mas eu não acho que dot net é suficientemente bom ATÉ HOJE para substituir VB6.
    E também não acho correto perder dezenas de criações muito bem feitas por caprichos estruturais dos criadores das novas IDEs.
    O que eu não consigo em VB6 sempre fiz em assembler, mas não posso me permitir perder performance e rodar sem compilação real,
    como realmente é no dot net. E faço biometria, controle mecânico, entrada e saída de sinais, e muito mais que você não imagina.
    Em VB6 por escolha, por ser melhor compilado, por ser compilado de verdade, por ter a dll mãe dentro do windows.

    O que se postula aqui é justamente um verdadeiro grande compilador atualizado, capaz de fazer hoje, para o que existe hoje,
    o que o VB6 fez em seu tempo. Mas principalmente... Impreterivelmente...
    Que permita que eu importe meus fontes, milhões de linhas MUITO BEM ELABORADAS e que não merecem a lata de lixo.

    Porque existe gente muito boa programando ainda em VB6, calada, aceitando o fato que a dll está lá dentro do windows,
    e isso basta. Para outros contextos, outros compiladores. Não o dot net. 
    Faça aplicativos de verdade, gigantescos, que precisam de muita edição, lapidação, estabilidade, continuidade, segurança.
    Seu nível de insatisfação em alguns detalhes, será a resposta que eu não tenho como lhe explicar em poucas palavras, ao usar o framework.

    Não pense que eu idolatro o VB6, eu quero justamente que algo como ele já foi um dia, surja, 15 anos avançado !!!

    Abraços

    ***

    Hello Color Ligthert

    I do not think I have to keep using an old product , you understood it correctly .
    But I do not think dot net is good enough to replace VB6, UNTIL TODAY .
    And also do not think proper to lose dozens of creations made ​​by fine structural whims of the creators of the new IDEs .
    What I can not in VB6 always done in assembler , but I can not allow myself to run without losing performance and actual build ,
    as it really is in dot net . And do biometrics , mechanical control , input and output signals , and much more that you can not imagine .
    In VB6 by choice, by being better built , being built of fact, by having the dll-mother under Windows .

    What is postulated here is just a great real compiler updated, able to do today, to what exists today ,
    what VB6 did in his time . But mostly ... without fail ...
    That allow me to import my sources , millions of lines VERY WELL PREPARED and does not deserve the trash .

    Because there is still good people programming in VB6 , silent, accepting the fact that the dll is inside the windows ,
    and that is enough . In other contexts , other compilers . No dot net .
    Write real , gigantic , applications that need a lot of editing , cutting , stability , continuity , security.
    Your level of dissatisfaction in some detail , the response that I have no way to explain it in a nutshell , to use the framework .

    Do not think that I worship the VB6 , I just want something like it once was , emerge , advanced 15 years !

    hugs


    Eugenio P. S. Canaan - ILT tecnologia - BR


    Saturday, March 8, 2014 2:55 PM

  • What I can not in VB6 always done in assembler , but I can not allow myself to run without losing performance and actual build ,
    as it really is in dot net . And do biometrics , mechanical control , input and output signals , and much more that you can not imagine .
    In VB6 by choice, by being better built , being built of fact, by having the dll-mother under Windows .

    What is postulated here is just a great real compiler updated, able to do today, to what exists today ,
    what VB6 did in his time . But mostly ... without fail ...
    That allow me to import my sources , millions of lines VERY WELL PREPARED and does not deserve the trash .

    Because there is still good people programming in VB6 , silent, accepting the fact that the dll is inside the windows ,
    and that is enough . In other contexts , other compilers . No dot net .
    Write real , gigantic , applications that need a lot of editing , cutting , stability , continuity , security.
    Your level of dissatisfaction in some detail , the response that I have no way to explain it in a nutshell , to use the framework .

    Do not think that I worship the VB6 , I just want something like it once was , emerge , advanced 15 years !

    hugs


    Eugenio P. S. Canaan - ILT tecnologia - BR

    You should not only think, in the way you tell it, it sounds as a believe. It seems you really 've only listen to those who have written bad about the .Net framework but never tried it?

    .Net has much more ports to what you describe then VB6 ever had.

    Just try and get the experience that it goes faster in a much more reliable way. And the best thing is, you can constantly maintain parts and improve them, include newer hardware. With .Net you are at the end not stucked with an old machine, with all kind of strange parts which are loosing there support. For instance VB7 code can still be used without any change in VB12. That was never in the time of VB1 to VB6.

    With VB6 you was forced only to use a desktop, with newer VB you can use Phone, Xbox, Web, Services, Clouds, or whatever which is new on the marked. 

    What you describe is this.


    Success
    Cor


    Saturday, March 8, 2014 3:08 PM
  • E me permitindo uma piada, lhe adianto:

    Tirem a dll do Vb6 do windows, em uma versão futura, sem nos dar antes um compilador de verdade,
    e eu mesmo faço um linux com desktop similar ao UI, loja UI grátis, compilador com RAD como o Vb6 em linux,
    que importe Vb6 diretamente, e distribuo gratuitamente mundo afora, e me aposento,
    deixando meus fontes todos de 30 anos de programador, gratuitamente em um site de código fonte,
    livres para pesquisa e desenvolvimento, mas não quero morrer, se Deus assim o permitir,
    jogando no lixo uma vida inteira de desenvolvedor de software e hardware
    porque alguns poucos decidiram que as milhares de linhas que criei são lixo.

    PORQUE NÃO SÃO !!!

    O tempo vai dizer o que vai acontecer, caro Cor Ligthert...

    Abraços


    ***

    And allowing me a joke, you go forward: 

    Exclude the dll Vb6 windows, in a future version, without giving us the truth before a compiler, 
    and I even do a linux desktop with a similar UI, shop free UI 
    compiler with RAD as VB6 in linux, which Vb6 import directly 
    and distribute free world, and retire, 
    letting my sources all 30 years of programmer, for free on a website source code, 
    free for research and development, but do not want to die, if God allows, 
    throwing garbage one lifetime of a software developer and hardware 
    because few have decided that the thousands of lines that are created garbage. 

    WHY ARE NOT! 

    Time will tell what will happen, dear Cor Ligthert. .. 

    hugs

    Eugenio P. S. Canaan - ILT tecnologia - BR

    Saturday, March 8, 2014 3:22 PM
  • Você me convenceu, com a foto daquele carro, a jogar fora mais de 20 aplicativos de 80 mil linhas em média cada um.

    Me convenceu a usar um gerador de executável que não compila.

    Me convenceu a instalar framework onde eu poderia rodar meu executável sem pré instalação nenhuma.

    Me convenceu a reescrever linhas de código em uma linguagem nova por causa de OOPs e outras coisas
    importantíssimas que sem elas eu não seria um grande programador, nunca, nunca, sem elas.


    Me convenceu a desistir de argumentar uma coisa muito simples:

    Porque os idólatras do dot net tem mesmo que ficar se metendo, se o pedido não os afeta em nada ?

    Não posso mesmo de forma alguma ter o meu compilador atualizado ???

    Essa é posição final de quem ??? De quem gosta de dot net e não quer ver isso acontecer ???

    Porque não tem nada que impede um cidadão qualquer, abrir o source code do VB6, e em uma semana atualizar tanto ele,
    que você se espantaria a nave espacial que sairia dali, não um calhambeque para me ridicularizar.

    Parei, porque sou velho, e não quero perder meu tempo.

    Abraço 

    ***

    You convinced me , with a picture of that car , playing out over 20 applications on average 80 000 lines each.

    Convinced me to use a generator executable that does not compile .

    Convinced me to install framework where I could run my executable without any pre installation.

    Convinced me to write lines of code in a new language because of OOPs and other things
    extremely important that without them I would not be a great programmer , never, never without them.



    Convinced me to give up arguing something very simple :

    Because the idolaters dot net has become even getting into, if the application does not affect anything ?

    I can not even possibly have upgraded my compiler ? ?

    This is the final position of who ? ? Who likes to dot net and do not want to see this happen ? ?

    Because there's nothing that prevents any citizen , open the source code of VB6 , and in a week to update both he
    you be amazed that the spacecraft would go away, not a clunker to ridicule me .

    I stopped , because I'm old and do not want to waste my time .

    hug


    Eugenio P. S. Canaan - ILT tecnologia - BR

    Saturday, March 8, 2014 4:42 PM

  • You should not only think, in the way you tell it, it sounds as a believe. It seems you really 've only listen to those who have written bad about the .Net framework but never tried it?

    ...


    Success
    Cor


    That seems to be the case with all of these VB6 zealots.  They know nothing about what .Net really is or what it can do.  They do not understand that the VB6 runtime is like a limited, clunky, prehistoric version of the CLR.  They are so caught up in perceived design time differences that they understand nothing of the vast improvements at compile time and run time.

    We both know how laughable the idea of multithreading is in VB6.  These people believe that simply because their program does not crash that their use of threading is correct.  They have no idea of the mess that Windows is constantly trying to clean up in their wake, and/or the amount of resources that they are wasting (given that modern Windows is very robust and modern hardware provides vast system resources).

    These folks also have no concept of how a 10,000 line VB6 CRUD app could be rewritten in .Net with about 20 lines of code (utilizing all available designer data access features).  The fact that they even think in terms of "lines of code" shows how far out of date they are.  The number of lines of high-level source code are virtually irrelevant to anything.

    They also have no concept of code generation frameworks such as EF, where you can write a well-defined object model and then literally generate complete applications based off of the model (coding becomes almost optional, based on desired functionality).

    There's also all of the unfounded fear of decompiling.  These people do not realize that in most cases their software is not as fantastic as they believe it to be.  In most cases no one will care to decompile their programs because they can easily be rebuilt by anyone who knows what they are doing.  And if a program does include some super-fancy-secret algorithm, then they can always obfuscate the assembly.  We all know there are ways to protect your .Net assembly if you really need to (but that in most cases it is completely pointless).

    At the end of the day it is a fool's errand to argue with fools, so there's little sense to continuing the "discussion" (if you could all it that - a discussion implies that both sides reasonably consider each others arguments, and that those arguments are sound and valid).


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    Saturday, March 8, 2014 6:15 PM
  • At the end of the day it is a fool's errand to argue with fools, so there's little sense to continuing the "discussion" (if you could all it that - a discussion implies that both sides reasonably consider each others arguments, and that those arguments are sound and valid).


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    And yet it is you who moved this thread from the Visual Basic forum to 'Off-topic posts'. Scared of losing the argument ?

    And you still haven't named those who banned Megan ? Is that because they were VB.NET zealots ?

    And I don't think it was 'VB6 zealots' who posted photos of an abacus, an analog computer or a car. Clearly these were the best arguments these individuals could put forward.

    The opening post was a genuine call to bring back an (improved) VB6. There was no suggestion that this was to replace VB.NET or any other language. And yet no one has put forward a reason this shouldn't be done. Instead there have been arguments saying VB.NET is better than VB6 (or vice versa) which are totally irrelevant to the subject of this thread.

    Saturday, March 8, 2014 8:08 PM
  • Exatamente, Shen2005:

    Ninguém é VB6 zealot aqui, mas há muitos dot net zealots confundindo as coisas.

    Dot net é bom ? É perfeito ? Precisa melhorar ? 
    Façam tópicos pedindo melhorias para ele.
    Ninguém irá lá confundir as coisas, provavelmente alguns de nós que usam a IDE irão confirmar a necessidade das melhorias, 
    como todo programador sensato que quer ver melhorias em suas ferramentas.

    Tenho vergonha de falar em VB6 e alguém vir me tachar de incapaz ou tolo apenas porque respeito o compilador e
    gostaria sim de vê-lo atualizado e continuado.

    Se soubessem tudo o que sei e já fiz em tantos outros contextos não chegariam chutando seres humanos
    com essa idolatria descabida. Tenho vergonha de ver "colegas" se comportarem assim

    Isso sim, é idolatria. Uma idolatria completamente fora do contexto do requerimentoo desse tópico.


    Como se usar dot net fosse a única obrigatória forma de continuar sendo inteligente e capaz...

    ENVERGONHADO por alguns aqui. 

    ****

    Exactly , Shen2005 :

    Nobody is VB6 zealot here , but there are many zealots dot net confusing things .

    Dot net is good ? Is it perfect? Need to improve?
    Make topics asking improvements to it.
    No one will , there confuse things , probably some of us who use the IDE , will confirm the need for improvements ,
    like any sensible programmer who wants to see improvements in their tools.

    I am ashamed to speak in VB6 , and mislabeling someone sees me incapable or foolish , just because I respect the compiler and
    I would rather see it updated and continued .

    If they knew everything I know , and I have done in so many other contexts ,
    using many other tools not arrive kicking humans
    with this misplaced idolatry. I am ashamed to see " colleagues " behave well

    That yes , it is idolatry. Idolatry completely outside the context of requeriment this topic.


    Insist that using dot net is the only way to continue being mandatory smart , capable and productive ...

    ASHAMED by some here .



    Eugenio P. S. Canaan - ILT tecnologia - BR



    Saturday, March 8, 2014 8:34 PM
  • @Eugenio and @Sten

    Many have asked here, give us some objective facts. 

    Not words like "respect the compiler", "kicking people", "capable and productive", "Scared of Loosing arguments".

    I've told for instance:

    1. The compatibility part of VB version VB7 to VB12 is upwards complete. That while VB5 to VB6 was not yet the right language. There were needed some improvements in the language in VB6 to VB7, but now it is consistent, tell us how good it was with VB1 to VB6.
    2. Going on with the MS Dos traject could have given problems to go on with newer hardware, therefore the Win32 traject was left to choose for a less hardware and OS depending platform, which became .Net framework. Be aware in fact are Win32 and .Net not really VB parts, it is the used API to the OS, tell us for instance how nice it is to program for phone with VB6.
    3. VB7 and newer are counterparts of newer languages like C# and Java. Both the latter do not the same as C++, but are very good to use in huge projects. C# DLL's and F# Dll's can be used like it is in the same program language in current VB. Tell us how you do that with VB6?

    There is much more, but let us start with those simple 3. This is not about words like "Easy", "Understandable", "Everybody can use it". That are words which we cannot proof but completely subjective.

    Every native kid in Mexico speaks Spanish, but that does not make Spanish a simple for everybody understandable language. 


    Success
    Cor



    Sunday, March 9, 2014 8:52 AM
  • Cor Ligthert :

    Bom dia, amigo...

    Você pode explicar por horas tudo o que tem de maravilhoso no word e porque eu devo usa-lo.
    Eu quero apenas que o notepad funcione em 64 bits.

    Não estamos falando das mesmas coisas.

    Eu quero a velocidade de carga do notepad, a simplicidade do notepad, eu tenho 80 mil linhas em notepad
    e quero continuar usando notepad, e o word que estão nos empurrando não lê TXT, eu tenho que digitar tudo de novo,
    porque agora tem unicode, etc etc

    Eu só quero o notepad nos 64 bits, tablets e UI, entendeu ?

    Continue com seu office, completo, fantástico.

    Eu quero o notepad atualizado, OK ???

    Notepad = VB6
    Office e Word = dot net

    Entendeu agora ??? O word não lê meu texto, eu tenho que ir parágrafo por parágrafo, reformatar tudo.

    Eu quero apenas continuar a escrever txt, mas em 64 bits, risc e Ui.

    Entenda e pare de dizer o quando o word é maravilhoso.

    Eu sei o quanto ele é maravilhoso.

    Mas eu também gosto da simplicidade fantástica do editor de txt quando preciso apenas editar txt.

    Porque o word de que estamos falando não lê txt nem salva txt

    SE ESSA COMPARAÇÃO NÃO FOR SUFICIENTE, EU DESISTO, AMIGO.

    MAS SE FOR, PETICIONE CONOSCO, REQUEIRA CONOSCO.

    Abraços

    ***

    Cor Ligthert: 

    Good morning, friend ... 

    Can you explain for hours, everything that has the wonderful word, and why would I use it. 
    I just want that the notepad function on 64-bit. 

    We're not talking about the same things. 

    I want the speed of loading of the notepad, the simplicity of notepad, I have 80 000 lines in notepad 
    and want to continue using notepad, and the word that are pushing us, do not read TXT, I have to type it all again, 
    because it now has unicode format, paper size, etc. etc. 
    I do not want to retype, ANALYZING, my 20 books in txt 
    but you INSISTS that I should do this. 

    At the moment I need the notepad in 64 bits, tablets and UI, understand? 

    Continue with your office, complete fantastic. 

    I want the updated notepad, OK?? 

    Notepad = VB6 
    Office and Word = dot net 

    Understand now?? The word does not read my text, I have to go paragraph by paragraph, reformat everything. 


    I just want to continue editing txt, but in 64-bit, RISC and Ui. 

    Understand and stop to say when the word is wonderful. 

    I know how wonderful he is. 

    All I do after the word appeared and worth, 
    I do in word, OK? 

    But I also like the simplicity of fantastic txt editor when you need only edit txt. 

    Because the word that we are talking not read txt or save txt 

    TXT !!!

    IF THAT IS NOT ENOUGH COMPARISON, I give up, FRIEND. 

    BUT IF, Petition U.S., REQUIRES U.S.. 

    Hugs


    Eugenio P. S. Canaan - ILT tecnologia - BR

    Sunday, March 9, 2014 4:14 PM
  • And yet it is you who moved this thread from the Visual Basic forum to 'Off-topic posts'. Scared of losing the argument ?

    And you still haven't named those who banned Megan ? Is that because they were VB.NET zealots ?

    And I don't think it was 'VB6 zealots' who posted photos of an abacus, an analog computer or a car. Clearly these were the best arguments these individuals could put forward.

    The opening post was a genuine call to bring back an (improved) VB6. There was no suggestion that this was to replace VB.NET or any other language. And yet no one has put forward a reason this shouldn't be done. Instead there have been arguments saying VB.NET is better than VB6 (or vice versa) which are totally irrelevant to the subject of this thread.

    These forums are for questions and discussions, not for arguments.  Though an argument seems to be what you are after... that's typically referred to as trolling.

    Yes I moved this to off topic.  At first I posted that the thread should probably go to off-topic, but that it could be left as a reminder as to why VB6 is in the past.  But then the thread became excessively long, riddled with flames, and guarded by trolls.  At that point it was no longer providing value to the VB.Net General Forum.

    As I stated previously, I had nothing to do with the ban and have no idea who did it; most likely it was someone on the contingent staff as they do most of that kind of work.  Viewing that user's entire activity report, it is obvious that all of their posts were meaningless VB6 comments, some of which included links to warez sites.  By the book, the ban appears to have been warranted.

    As for the pictures that were posted, they were funny to many a sense of humor and since this thread is a joke to begin with, funny pictures seemed apt.  If this thread were meant to take itself seriously, it would have a title which was not so obviously false, and it would contain some content with a reasonable argument.  As it is, it is the kind of post likely to end up in "off topic" regardless of it's subject matter.

    The reason this is not a valid topic (anywhere, ever) is because VB.Net is the updated version of VB6.  This entire conversation was had years ago, and the result was the continuation of .Net and the retirement of pre-.Net versions.  But MS did hear the complaints about learning curve, and so you have LightSwitch and SmallBasic to use as well.

    As Cor has clearly demonstrated, there are no valid arguments anymore for keeping VB6 around.  People just remember how much work it was to create their 800,000 line monstrosity in VB6 and don't want to have to go through that pain again.  What they refuse to believe is that they can rebuild that application in .Net with less than 80,000 lines of code and with a far greater ease of development.  The end result will likely be more stable, and have better performance.  The VB6 application whose .Net equivalent does not perform well should probably have been written in C to begin with.

    The .Net family is a massive suite of applications and technologies and there's just no place for VB6.1 to fit into any of it.  Everything you could want already exists, if you'd just start using it.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    Sunday, March 9, 2014 10:12 PM
  • I'm on a rant now...

    Because some of you developers feel like you should be allowed to sit in your cushy chair and collect income on work you performed some ten or twenty years ago, and you think that's right, while the rest of the development world works it's butt off to stay current with all of the latest technologies (a chore which is technically impossible for any one working person to accomplish, unless that in itself is their job... and perhaps even then!).

    And on top of that, you want these hard working people to DO MORE WORK so that you can continue to generate income from your ancient endeavors.

    Well guess what?  That ain't how it works.

    Eight years ago, I had a state-of-the-art ASP.Net website with features and functionality to put any other industrial online catalog to shame.  Today that website is crap, and nothing about it has changed!  Heck, it even got a bit of polish when AJAX came out, but by today's standards it is junk.

    Do I cry that my website should still be considered fantastic when the expectations of the world around me have changed?  Not at all.  I accept that my solution has run its course and I begin preparation of its replacement.  That may be one heck of a process, with all of the web technologies to choose from and more appearing every day, but that's part of what I'm paid to do.

    What are you going to do in another five years when your VB6 app will still run on a Windows PC, but nobody is using a PC anymore?  I can tell you our office is headed toward full virtualization of the client experience and that will mean moving to ever lighter and more compact versions of what the "desktop operating system" means.  When you do still need a physical device, it will likely be some form of tablet, which may or may not be hosting a full Windows OS.  What do you do when your solution must be provided as a remote application, possibly even OS-independent?  I can tell you that the days of telling people to run your exe from a network share or mapped drive are over.  In five years time, IT leaders everywhere will be expecting their solutions in a form compliant with a fully virtualized environment and your VB6 application won't even be considered.

    The past is in the past people.  If you want to survive as a developer, then you need to live the modern day.  I'll leave you with these words of wisdom from Passenger:

    "So don't cry for the lost, smile for the living.  Take what you need, and give what your given.  Life's for the living so live it, or you're better off dead".


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    Sunday, March 9, 2014 10:39 PM
  • Hi Reed,
    Thanks for your two posts. Let me try to reply.

    Discussion or Argument ?

    You say "these forums are for discussions not arguments", and suggest that I want an "argument" or I am "trolling".
    Yes they are for discussions and no it isn't the case that I want an argument (or that I am trolling). I am trying to have a reasoned discussion following the opening poster's genuine request to "Please reconsider introducing VB6 to the market. It is needed by many."
    I don't consider you treated him fairly. You have some sort of administrative status on this forum, implicit in that is that you should treat all posters equally and fairly. Yet your first post was "Bring back Windows 3.11, we need it. ......VB6 should be retired and forgotten."  That post alone was unfair to the OP and it set the tone for other posts that followed.

    In other posts you refer to "VB6 zealots" but never criticize those who oppose the return of VB6 even when they accuse posters of being someone else. (I'm not making a plea for more banning and more censorship, I'm asking that everyone be treated equally).

    You also say "At the end of the day it is a fool's errand to argue with fools, so there's little sense to continuing the 'discussion'". Hardly fair and equal treatment, and certainly not an encouragement of discussion rather than argument.

    You also state "If this thread were meant to take itself seriously, it would have a title which was not so obviously false, and it would contain some content with a reasonable argument."  Again, the opening post was clearly a genuine call. You may not agree with it but that is no reason to call it 'obviously false'.

    Also the opening post doesn't even refer to VB.NET, it certainly doesn't suggest that VB6 should replace VB.NET - it is others who bring VB.NET into the argument. (And yet you move it to 'Off-topic posts' on the grounds it is not VB.Net related).

    Let me state I am putting this forward as my genuine opinion of your actions, I am not attempting to 'troll', 'flame' or to attack you personally.

    Valid arguments for VB6

    You say Cor has clearly demonstrated there are no valid arguments for keeping VB6 around. Not so.
    First of all the OP says "it is needed by many". Why should your and Cor's opinion be any more important than the OP's ?
    Here are some reasons it is needed (I limit myself to just 5 otherwise this post will be huge):

    1) VB6 is still widely used.  According to the TIOBE index it is the #7 most popular programming language - an amazing feat for a language last updated 16 years ago.  Particularly as Microsoft (& others) have spent 12 years trying to kill it off. You may not like it, but there it is.

    2) There are still a huge number of legacy VB6 applications in use, especially in corporates and government. Microsoft have (to their credit) recognized this and offer "it just works" support for the VB6 runtime until at least 2023 (soon to be extended).
    But this support is for the runtime, not the IDE.

     Microsoft effectively offer 2 options for these VB6 applications
       a) If no modifications are required, continue running the VB6 application (presumably Cor disagrees with Microsoft).
       b) If modifications are needed, migrate to VB.NET. 

    But in real life the most likely scenario is that the VB6 application will require a minor modification.
    So what do you do ? According to Microsoft you migrate. But if the modification is just to change (for example) some text on a form that would be nonsense.  I saw a suggestion a while ago that it cost $1 for every 3 lines of code migrated.  So a medium sized VB6 application could cost say $20,000 to migrate.  Clearly that is not an acceptable cost for the minor modification I suggested. (Don't get hung up on actual cost figures, I am just pointing out there are potentially significant costs involved).

    The obvious answer for this scenario is to use VB6 (at a cost of say $20 not $20,000). Yet Microsoft don't offer this, stating that the VB6 IDE is not supported on Windows 7 or 8. 
    Does anyone disagree that doing minor modifications in VB6 is the only acceptable solution in this scenario? Or are some going to suggest it is better to spend $20,000 than $20 ?

    Microsoft have painted themselves into a bit of a corner here, stating that they support unmodified VB6 applications until 2023, but you can't (theoretically) modify them.

    For completeness on this point I'll cover some other typical scenarios too:-
    One is that the VB6 program needs to become a web application - effectively this is then a re-write not a migrate, so you can decide what language is best to use. It may be, for example, that JavaScript/HTML5 is the way to go. (I've followed this route myself for some old VB6 apps).
    Another is that the VB6 application needs a mobile version. A few years ago that may have been VB.NET for Windows Mobile. (I've done that myself too, great for Windows CE/Windows Mobile 6.x). But doing this today you are really looking at iPhone,iPad and Android - again you can choose the best approach (native or web app ?) and language.
    The final scenario I'll mention is the one Microsoft do cover - migrate your desktop VB6 app to desktop VB.NET.  I can't think of any occasion in the last few years where I have found a genuine need to do this.  I have certainly seen cases where IT (or whoever) have decided that VB6 apps must be migrated because VB6 is 'obsolete' (I guess a view not too dissimilar from many in this forum). I've even done a few of these myself (though I had the sense to only do smaller migrations, not wanting to tie myself up with large scale migrations). I don't think of any of  these new applications (done by myself or others) were any better than the ones they replaced, but at least the customers were happy (and paid well).


    3) VB6 is the same language as VBA. VBA is a current, Microsoft supported language. It is in Microsoft's flagship product Office 2013. And it is the same language as VB6. You can cut and paste code between VB6 and VBA (and vice-versa). It is the same language.
    Both VB6 and VBA use the Visual Basic Runtime Library. In fact it is more than that, VB6 actually uses VBA to define it's language. In effect the VB6 IDE is a host for VBA in the same way that Word or Excel are hosts.
    It is strange that Microsoft support (and sell and extend) the language when it is named VBA but not when it is named VB6.
    Microsoft say VBA will be supported for the foreseeable future stating "This means that if you have an existing VBA project that you are satisfied with, you can be confident your investment is safe". Where is the logic in having this for VBA but not VB6 ? 
    They assure you your VBA investment is safe but won't give the same assurance for your VB6 investment.

    (OK, for the more pedantic posters VB6 is the same as VBA6.  VBA7 is the latest release and includes a handful of modifications to support 64 bit Windows. Prior to VBA7 the languages were kept identical, it is these same modifications that many of us now would like to have incorporated into an updated VB6).

    4) A suggestion to bring back an improved version of VB6 is the fifth most popular (out of almost 8,000) on the Visual Studio UserVoice site. Vote for VB6

    5) Microsoft's program manager for Visual Studio stated (Channel 9) "It isn't cost effective to keep rewriting code to get back to functional equivalence".  Quite so. So why re-write existing VB6 applications ?  (Again, Cor presumably disagrees).

    General Points

    You mention LightSwitch and SmallBasic. A good point.  But I'm sure you know neither support VB6 code so it doesn't address the concerns of the OP.  But it is nice to see that you aren't opposed to all languages that aren't called 'VB.NET'.
    So why the opposition to an updated VB6 ?  If you prefer, it could be named LightSwitch 6.1 rather than VB6.1 ? Or maybe SmallBasic 7.0 ? Or if you see VB6 as a threat to VB.NET you could name it VB Junior. As long as it can open and compile VB6 code that's fine by me. Incidentally, there is certainly no call for VB6.1 to be part of "the .Net family".

    You say "you want these hard working people to DO MORE WORK so that you can continue to generate income from your ancient endeavors."   I'm not sure I see your point here.  How is asking for Microsoft to bring back VB6 (together with the modifications they have already done for VBA7) doing that? I suspect Microsoft could do this for a fraction of the money they have wasted on LightSwitch or SmallBasic. And if it is going to be more work than Microsoft can handle (as if) they should open source VB6.

    You mention that your 8 year old website is 'crap'. Well, that's what happens with websites. But the analogy doesn't really hold for a typical VB6 desktop program. A desktop CRUD program written in VB.NET doesn't really look (or behave) any different to the same program in VB6.

    You ask what I will be doing in 5 years when nobody uses PCs anymore ?  Well who knows what the future will bring, but it is likely to be VB6 for those (mainly corporate) users still using desktops and laptops or Windows tablets, JavaScript for Web apps - including iOS and Android - (I note Microsoft are recommending JavaScript/HTML5), and something (maybe Basic4Android ?)  for native Android apps if Android phones and tablets become more acceptable for corporate users. I'll probably also be migrating my VB.NET apps to JavaScript too.


    As things stand, Microsoft have sent a clear message: 'If you are planning to make a substantial investment in developing your software, if your application is mission-critical, if you expect to use it for years to come - don't use Microsoft languages.'
    Have Microsoft learnt from this ? The killing of Silverlight would suggest not.

    Monday, March 10, 2014 9:01 PM
  • LOL Ok, I'll play the fool a moment -

    First, you apparently refuse (as it has been explained several times) to accept the fact that the post was created in a .Net forum where VB6 is off topic with the exception of questions regarding upgrades/conversion.  It is not relevant to create a discussion about VB6, let alone attempt to revive an ancient discussion that was finished long ago.

    The post also did not meet the forum guidelines for writing a post.  I already explained what it would have taken to validate the post.  And the title was most certainly "obviously false" because "we all need it" is a false statement.

    No one was treated unfairly.  Opinions were given on a thread which was pure opinion to begin with.  Nothing occurred outside of the forum guidelines, with the exception of the flaming/trolling content that the thread eventually accumulated.

    As for other languages, I'm a proponent of any technology that has a place in modern development.  Java PHP and Ruby for example are all viable technologies that have their niche to fill.  VB6 has no niche left, except for people who flat-out refuse to learn anything else.  Let's look at your list of points:

    1) Meaningless statistical garbage.  For every link you find saying one thing, someone else can find one saying the opposite.  Other results were already posted in this thread.  From what I've seen, and heard through other MVPs, the Tiobe index is a questionable source at best.

    2) The real world situation is that if you are in a corporate environment you are currently migrating away from (or have finished migrating away from) "Legacy" applications because they are too expensive to support and maintain.  Your VB6 application will always be a Legacy app.  Just because you saw some arbitrary cost estimate for conversion, it doesn't mean that a real developer would spend anywhere near that amount of company resources rewriting their application, once they had a solid understanding of how to do things in .Net.  Sure, doing a line by line conversion of VB6 would be painful and expensive, but in the vast majority of cases you can just redesign the application in .Net and have it rewritten in no time, using the VB6 code as a functional model.

    Your other scenarios are describing new applications.  And guess what?  If you re-wrote the core of your application in .Net following certain patterns, you could practically generate your desktop app and web app and mobile app based on the domain model that you wrote.  There are a bizzilion-and-one time saving features available throughout the .Net suite and VB6 doesn't have access to any of them, and can't, because it uses its own outdated runtime and not the CLR.

    3) No it isn't.  VBA is a lite implementation of VB6.  And even it is maintained for compatibility purposes and is not the choice for new development of any Office functionality.  You use .Net to write automation or plugins for Office applications.  It is SO much easier than using VBA, and offers so many more possibilities.

    4) Yes, 480 of you have spent all 10 of your votes on that one thread.  I'd be willing to bet that if we could see the list of voters, there would be no user card of someone who is already recognized in the modern development community.

    5) Let's see that quote in context.  Besides, in this case, you are being asked to rewrite once; after that, your code will mostly flow upward with little to no changes.

    Of course you missed my point about people sitting on their laurels... since that's the only valid argument for keeping VB6 and you seem intent on repeating the same nonsense that has been soundly refuted for years.

    Finally, I find your conclusion to be absurd.  If anything, they have demonstrated exactly the opposite of that.  Of course technologies fall out of favor as new things arise.  This doesn't end.  Wait until Roslyn is ready and then see what grows out of that!  The point is that once you've entered the .Net era, the only thing that changes is the way you use it.  Your old stuff still works just fine and you can continue to maintain it as long as you want.  Upgrading is generally optional.  Rewriting is generally desirable after some new technology comes out that allows you to do what you currently do better and faster (or more securely) and with less resource consumption.  But these are all choices left to you, the developer.

    When you are ready to leave 1998, 2014 has some great things to offer you when you get here.


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"


    Monday, March 10, 2014 10:04 PM

  • 3) VB6 is the same language as VBA. VBA is a current, Microsoft supported language. It is in Microsoft's flagship product Office 2013. And it is the same language as VB6. You can cut and paste code between VB6 and VBA (and vice-versa). It is the same language.


    Any changes to VBA are strictly driven by a flagship product, Microsoft Office. Other than supporting the 64-bit environment, there is no new development with respect to the language.

    As has been previously stated VB 6.0 is simply a past generation of the language that has evolved, and there would be no benefit for Microsoft to continue work on what would be a competing development product based upon a different version of the language.


    Paul ~~~~ Microsoft MVP (Visual Basic)

    Monday, March 10, 2014 10:33 PM
  • Any changes to VBA are strictly driven by a flagship product, Microsoft Office. Other than supporting the 64-bit environment, there is no new development with respect to the language.

    Paul ~~~~ Microsoft MVP (Visual Basic)

    Indeed so.  And it is those same 64 bit modifications we are requesting be added to VB6.

    Monday, March 10, 2014 11:06 PM
  • Caros amigos...

    Vocês em 1998 faziam o quê ? Andavam de bicicleta ? ( Humor negro, sorry... )
    Porque eu programava as mesmas 18 horas por dia que eu programo hoje.
    VB6 era massacrado por idólatras de um tal de Delphy, um pascal com IDE, mas que não editava durante a execução.
    O criador do Pascal, esse que não editava durante a execução, e que para ser instalado precisava de N procedimentos,
    foi o chefe de todo o dot net, e descontinuou VB6, vb.net NÃO É continuação de VB6.
    É um outro BASIC e todos sabem disso, apenas teve a embalagem Microsoft como o VB6.
    Esse é o fato.
    Se houvessem conversores funcionais, na época, essa discussão hoje não existiria.
    A petição seria que dot net, compilasse de verdade.
    A petição seria que dot net, tivesse performance.
    A petição seria que dot net, editasse durante a execução.

    VB bastava enviar um executável, e acredite os modems eram de 33K e 56K, e 
    nós atualizávamos software a 33K. VB era compilado, e isso nos dava segurança,
    já ouviu falar o quanto vale a fórmula da coca cola ?
    Pois eu dou valor sim às linhas de código que criei.

    Eu faço em dot net o que é de dot net.
    O que eu faço em VB não faço em dot net.

    O que eu aceitei como  fato real é que VB6 não foi continuado,
    e que merece ter sua compilação para 64 bits, risc e RT, WPhone, o que vier.

    Qual a dificuldade de terem respeito por isso ?
    Por esse pedido de atualização de um compilador que não morreu ?
    Que tem adeptos, valor de mercado, e parque instalado em alta escala ?

    Se eu tiver que converter um aplicativo meu de 80 mil linhas, 
    eu prefiro escrever um conversor do que ficar olhando sua execução,
    e escrever do zero 80 mil linhas novamente em outra linguagem,
    por mais parecida que ela seja para ser chamada de continuação,
    continuação, amigos, ela NÃO É !!!

    Se a petição requerendo vb6 já foi para off topic,
    qual é o nível de repulsa ao VB6 para até aqui no off topic,
    virem aqui trepudiar de um pedido de atualização de um simples compilador velho ?

    Impressionante como o VB6 é poderoso e faz inimigos em 2014.
    Vocês verão o quanto estão errados em dizer que estamos parados no tempo.

    Preservar o que é de valor não é ser um imbecil como ando sendo chamado.

    ****

    Dear Friends ... 

    You did what in 1998? Rode bicycles? (Black humor, sorry ...) 
    Because I programmed the same 18 hours a day that I schedule today. 
    VB6 was slaughtered by idolaters of such a Delphy a Pascal with IDE, but not edited during execution. The creator of this Pascal, this not edited during execution, and that needed to be installed N procedures, was the head of all the dot net, and discontinued VB6, vb.net NOT continued VB6. 
    It is another BASIC and everyone knows it, just had a package like Microsoft VB6. 
    That is the fact. 
    If there were functional converters, at the time, this discussion would not exist today. 
    The petition would be dot net, compile true. 
    The petition would be dot net, had performance. 
    The petition would be dot net, enactment during execution. 

    VB enough to send an executable, and believe the modems were 33K and 56K, and 
    we atualizávamos software to 33K. VB was compiled, and that gave us security, 
    heard how important it is the formula of coca cola? 
    Because I value yes to the lines of code that I created. 

    I do in dot net what is dot net. 
    What I do in VB, do not do in dot net. 

    What I accepted as fact is that VB6 was not continued, 
    and it deserves to have a compilation for 64bit risc and RT, WPhone, what may. 

    How difficult is it to have respect for that? 
    For this application, update, a compiler that did not die? 
    That has fans, market value, and installed equipment on a large scale? 

    If I have to convert my application 80 thousand lines, 
    I prefer to write a converter than stare at his execution, 
    scratch and write 80,000 lines again in another language, 
    for more like it to be continued to be called, 
    continuation, friends, it IS NOT! 

    If the petition requesting vb6 been to off topic 
    what is the level of hatred for VB6 to far off the topic, 
    come here to troll an update request from a plain old compiler? 

    Impressive as VB6 is powerful and makes enemies in 2014. 
    You will see how they are wrong to say that we are stuck in time. 

    Preserve what is of value is not an asshole like being called Walk.


    Eugenio P. S. Canaan - ILT tecnologia - BR

    Monday, March 10, 2014 11:25 PM
  • ""obviously false" because "we all need it" is a false statement." - That's nitpicking. Clearly the OP doesn't mean everyone in the world needs it. He is referring to VB6 coders. If your argument (sorry 'discussion') has sunk to this level clearly you have little to offer.

    1) "Meaningless statistical garbage" - well if it doesn't agree with your pre-conceived ideas it must be. I presume you also consider the placing of C# at position 5 and VB.Net at position 10 to be garbage too. The reality is, though, that this gives a reasonable guide to the popularity of programming languages and has done so for 25 years.
    Back in 2000 Microsoft claimed 6.1 million VB6 coders.  It is noticeable that they don't quote figures for VB.Net coders now.

    2)"The real world situation...". If you really believe corporate and government users are moving or have moved away from legacy applications, then you aren't living in the real world. Do you realise how much Cobol, VB6 and other legacy code is still out there ?
    And you don't think conversion costs would be anything like the figures I quoted ? I can point you to a conversion (done by VB.Net fanbois) that has taken 3.5 years and still isn't finished. But of course that would hardly have cost anything , would it ?
    About the scenarios I suggested. You seem to be making the assumption that one VB6 application would need to be re-written as a desktop app, a web app and a mobile app. This isn't the real world. A typical VB6 application would be re-written as one of those. A different application would be re-written as another. You don't typically generate 3 versions of the same app.

    3) "VBA is a lite implementation of VB6" - try again.

    4) Votes - you can't vote 10 times for 1 suggestion.

    5) You need 'context' for the quote  "It isn't cost effective to keep rewriting code to get back to functional equivalence" ?  Seriously ?  Clearly you are a coder. If you had any business knowledge you wouldn't need a 'context'.


    "
    sitting on their laurels..."  Don't forget someone has to pay for any migration from VB6. Clearly from your above comments it isn't something you consider.  But, in the real world, if a customer won't pay it won't get migrated. That's why banks still use Cobol apps and corporates and government still use VB6 apps. If they can't justify the business case it doesn't happen. And often there isn't a business case to re-write software that works just fine.

    "Finally, I find your conclusion to be absurd. " - I assume you are referring to the message Microsoft has sent out: For VBA code "This means that if you have an existing VBA project that you are satisfied with, you can be confident your investment is safe"; but for VB6 code no such guarantee.


    Monday, March 10, 2014 11:46 PM
  • @Sten,

    I asked 3 simple questions to you. I bring it even down to less text.

    1. How easy was it to go upwards from VB1 to VB6. Currently with VB7 to VB12 there is not any conversion in the code. The problems you mentions from past doesn't exist anymore. It seems Microsoft has listen good, but was not able to do it with that product which is thrash in current programmers eyes.
    2. How easy is it to create VB6 programs for current going devices like phones, tablets, web, game devices and so on;
    3. How easy is it to mix VB6 with program languages like F#, C#, and C++; 

    Seems to me easier to answer then all the nothing saying subjective words you use which go not further then what some believe. In the way you tell it is like persons who still want to proof the world is flat.


    Success
    Cor

    Tuesday, March 11, 2014 9:13 AM
  • Hi Cor,

    1) Yes, it was easy to go from VB1 to VB6; and it is easy to go from VB7 to VB12.
    The issue is with going from VB6 to VB7

    As Eugenio says (a couple of posts above) "If there were functional converters, at the time, this discussion would not exist today."  If Microsoft had handled the VB6 to VB.NET issue (such that you could take VB6 code and compile in VB.NET, whether directly or using a wizard) at the time we would all be using VB.NET and we wouldn't be having this discussion.

    There are huge amounts of VB6 applications still out there that haven't been migrated. Many of them probably never will be. (Microsoft have recognized this and keep extending "It just works" support for VB6, currently until 2023).

    The issue, which many coders seem not to recognize, is that there is always a cost. If no one is willing to pay for a migrate then it doesn't get done. Whether or not an application would be 'better' re-written in VB.NET is irrelevant. If no one pays it doesn't get done.

    2) No one is suggesting writing writing VB6 apps for phone, tablets or web.  There are other tools for those.  Microsoft are suggesting JavaScript and HTML5. 

    3) Again, not really relevant - no one is suggesting you do this . But yes, if you must, you can with C++ and C# (I don't know F#).

    Tuesday, March 11, 2014 10:05 AM