I suggest you ...

11,161 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    Dr. Mihai Bush, PhD (MPV)Dr. Mihai Bush, PhD (MPV) shared a merged idea: Make Visual Basic 6 as a part of Windows (by default)  ·   · 
    Anonymous shared a merged idea: Please bring back Visual Basic 6.0 !  ·   · 
    Anonymous shared a merged idea: The silent majority of VB6 users did not ask VB.NET  ·   · 
    MaryMary shared a merged idea: Merge the core of VB6 into Office or the Windows OS.  ·   · 
    BravoBravo shared a merged idea: Bring back Classic Visual Basic, an improved version of VB6  ·   · 
    HMan2828HMan2828 shared a merged idea: Make a new Classic Visual Basic, an improved version of VB6  ·   · 
    Ana-Maria (VB6 software programmer)Ana-Maria (VB6 software programmer) shared a merged idea: Bring back Classic Visual Basic 6.X, an improved version of Visual Basic 6.0  ·   · 
    Anonymous shared a merged idea: Bring back Classic Visual Basic 6.X, an improved version of Visual Basic 6.0  ·   · 
    Marius OrionMarius Orion shared a merged idea: Bring back Classic Visual Basic, an improved version of Visual Basic 6.0  ·   · 
    PacManiPacMani shared a merged idea: Close the suggestion to "bring back VB6"  ·   · 
    VB6 FireVB6 Fire shared a merged idea: Bring back Classic Visual Basic, an improved version of Visual Basic 6.0 (the old idea has been stoped at 7400 votes for no good reason)  ·   · 
    MeredithMeredith shared a merged idea: Make VB6 Free  ·   · 
    Mike PaulickMike Paulick shared a merged idea: Bring back VB6. I have no interest in .net. VB6 is better for me.  ·   · 
    David KayeDavid Kaye shared a merged idea: Bring back VB 6.0! It's an extremely handy language used on tons of business apps.  ·   · 
    Adam SpeightAdam Speight shared a merged idea: Don't do a Classic VB (VB6). Open Source the VB6 compiler source code.  ·   · 
    VB6 FireVB6 Fire shared a merged idea: Bring back our un-killable cockroach, is ours !  ·   · 
    Nitesh PatelNitesh Patel shared a merged idea: The Old classic visual basic 6.0 bring it back  ·   · 
    I_A_WI_A_W shared a merged idea: Visual Basic 6.0: A giant more powerful than ever  ·   · 
    Anonymous shared a merged idea: Full vb6 Compatiablity, dammit  ·   · 
    your nameyour name shared a merged idea: shove .net up your boss's butt. bring me VB6-A already.  ·   · 
    Anonymous shared a merged idea: Open Source VB 6  ·   · 
    leoleo shared a merged idea: make it easier. In VB6 i don't have to know what classes are. It has been to complicated for simple programms.  ·   · 
    declined  ·  Visual Studio TeamAdminVisual Studio Team (Product Team, Microsoft) responded  · 

    We have read all of the comments on this thread and I’d like to thank you for providing your constructive feedback on this issue. Instead of merely repeating our support and migration guidance that has been laid out on http://msdn.com/vbrun, I’d like to address some of your specific comments here.

    To play back the feedback themes we’re hearing:
    - VB6 is awesome
    - VB6 needs to be brought forward and maintained: in a new release or OSS

    VB6 was and still is without a doubt awesome. VB6 made developers incredibly productive building a breadth of applications and as a result we have a wealth of applications and passionate developers to this day in 2014. One way I see our mission in developer tools is to empower developers to solve problems. This includes both today’s problems AND the problems of tomorrow. VB6, as you all have stated repeatedly in this thread, is an excellent tool for solving the problems of its day. We also stand behind our decision starting in 2002 to meet the current demands of our developers and the industry with .NET. For the scenarios VB6 set out to do, we see VB6 being “complete”. We feel good about VB6 being able to continue maintaining their applications for the past 15 years. Current needs ranging from distributed applications and services, to web applications and services, to devices, to new architectures and languages, required fundamental changes to the whole stack. We looked at how we could accommodate these needs through incremental changes to VB6 while maintaining its essence, and that was not possible.

    To address the modern needs we would need to go far beyond updating the language. We have to remember that VB6 is not just a language. VB6 is a language, a runtime, a platform library, a tool/IDE, and an ecosystem tightly packaged together in a way that made all of them work well together. We’ve worked with many customers on migration from VB6 to .NET and found that while yes, there are language changes, the dominating factor in migration difficulties isn’t the language differences. Even open sourcing the language/runtime wouldn’t solve the fact that VB6 was thought for a different set of problems, and the fact that its strength came from the end-to-end solution provided by all these five pieces working together. Take a change like 64bit, the complete runtime, tools and ecosystem chain would need to be retooled.

    So, moving forward what can we do? Where we have been able to help move forward is in our stance around support and interoperability. The VB6 runtime it is still a component of the Windows operating system and is a component shipped in Windows 8.1. It will be supported at least through 2024. This ensures your apps and components continue to run as you incrementally move forward to .NET. The support policy is here: http://msdn.microsoft.com/en-us/vstudio/ms788708. There are numerous interop strategies that we developed and evolved to enable incremental migration as you upgrade your skills, described here: http://msdn.com/vbrun.

    In summary, VB6 was awesome. We agree. We don’t expect or demand anyone to throw away their code or rewrite from any of our technologies unless it makes business sense for them to do so. We have to innovate to enable our customers to innovate. It is not a viable option to create a next version of VB6. We stand by our decision to make VB.NET and the .NET Framework. We think they are awesome too. It is not feasible to open source VB6 tools chain and ecosystem. The VB6 runtime was last shipped in Windows 8.1 and will be supported for the lifetime of Windows 8.1. Support and interop are great tools to move forward incrementally.

    I hope you feel we’ve listened to your feedback and that I’ve explained things well enough that you understand our decision.

    Paul Yuknewicz
    Group Program Manager
    Microsoft Visual Studio Cloud Tools

    4427 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • VB6 TO VB.NET IS EASYVB6 TO VB.NET IS EASY commented  ·   ·  Flag as inappropriate

        Feedback from Apogeo, Italy
        clock January 22, 2013 17:30

        One more customer who used VB Migration Partner and Code Architects' migration services...

        VB Migration Partner has been a winning choice for migrating our VB6 application, that serves over 700 customers. In a few months they delivered an error-free version of our 500K lines of code application and we appreciated the VB Migration Partner efficient and skilled technical support. Code Architects is a crucial partner to quickly adapt the product to the new technologies.

        Gianluca Zanella
        Technical Team Apogeo - Gruppo Zucchetti – Italy

      • VB6 TO VB.NET IS EASYVB6 TO VB.NET IS EASY commented  ·   ·  Flag as inappropriate

        SnelStart, Netherlands choosed VB Migration Partner and happily migrated 450K LOCs
        clock August 10, 2011 09:20

        We just received this great feedback:

        We have investigated the possibilities for a migration after a presentation of Code Architects at the Microsoft TechEd 2010 in Berlin. Before the presentation we assumed that migration would be too complicated en too expensive. After analyzing four different tools, we chose VB Migration Partner for the migration of our accounting and billing software (450K lines of code).

        The big advantage of VB Migration Partner is that it solves the problems directly in the VB6-code by using “pragmas”. Therefore we don’t have to freeze our code and interrupt the new development in our software. With VB Migration Partner it’s also possible to migrate 1:1. This enables us to offer our customers the same user experience, but this time on a new platform. The final reason for us to choose VB Migration Partner is the (online) service and documentation. The tool and the website contain lots of background information and tips that will help you with the migration.

        Ivo Huizinga
        IT Manager, SnelStart

        Netherland-based SnelStart is just another company who has appreciated the beauty and usefulness of VB Migration Partner's innovative approach based on pragma and its advantages over previous-generation, traditional conversion tools. You can find more example in our User Feedback page.

      • VB6 TO VB.NET IS EASYVB6 TO VB.NET IS EASY commented  ·   ·  Flag as inappropriate

        One more customer praising the convert-test-fix approach
        clock January 24, 2011 16:28

        We received from a German customer these notes, which we gladly (and proudly) publish. As usual, boldface is mine:

        On today’s market you have to be able to deliver new application versions at any time. Customers don’t accept statements like: “Sorry, we are in a migration process. We can’t add the feature you need. We can’t even fix a bug within the next year.” VB Migration Partner is the only tool which enables us to enhance the application during the migration process.

        It was soon clear to us that the library approach is the way to go. VB6 and VB.NET are too different. It’s not possible for a machine to close this gap. Without VB Migration Partner we would have ended up implementing our own library. The "pragma" concept enables us to run the migration and as a result get .NET code we can compile. With pragmas migration is an ongoing process. We migrate, make changes on the generated code, express these changes in terms of "pragmas" and migrate again. During these migration cycles we are still able to change, enhance and deliver the old VB6 application. VB Migration Partner is a software which gives you the feeling the developers work with it themselves. They know the problems in migration processes and they offer solutions that work.

        Conclusion: If you have unlimited time, money and manpower it might be worth having a closer look on the VS built in migration tool. If one of these resources is limited you choose VB Migration Partner.

        Martin Gerhold
        Dietrich’s AG / Germany

        Some customers ask us whether it is feasible to migrate to .NET without a support library. This customer found the answer by himself: the support library is the only reasonable mean to automatically deliver code that runs correctly. In fact, he says that without VB Migration Partner they would end up building their own library. Fortunately we at Code Architects have spent many man/years to extend and fine-tune our library, thus you can focus on less boring facets of the business.

        Equally interesting is that this customer realized that only VB Migration Partner is able to convert VB6 apps that are being modified during the process: this is the methodology we know as “convert-test-fix”. All other conversion tool work on a snapshot of the VB6 codebase, and when the migration seems to be completed you suddenly realize that you still have to re-sync your migrated code with the new features and bug fixes that have been added to the original VB6 code in the meantime.

        Not really smart, uh?...but this is how all other VB6 conversion tools work.Wink

      • VB6 TO VB.NET IS EASYVB6 TO VB.NET IS EASY commented  ·   ·  Flag as inappropriate

        Guess which VB6 migration tool delivers fewer compilation errors?
        clock February 2, 2011 16:48

        Migration from VB6 is a serious matter and choosing the wrong approach might cost you a lot of time and money, or even putting at stake the entire migration project.

        For this reason we always recommend all our prospect customers to test all the available solutions and tools before making their final choise. This is the experience of Solent, France:

        Facing a problem of Microsoft VB6 obsolescence, we spent weeks defining the best way to migrate our customer’s specific enterprise application from VB6 to VB.NET. We tried different COTS migration tools but the results were not the expected ones: too many things to complete manually after the conversion. The idea to develop a proprietary migration tool was in our mind when we finally found VB Migration Partner. It was the solution we needed.

        Indeed, with VB Migration Partner, we ended having to manually deal with only about 100 compilation problems compared to more than 10k given by other tools. Its iterative process with replayable corrections (thanks to "pragmas") was a very useful functionality in order to reach a complete validation of the 150K lines of code application we had to migrate. During this process, we found and fixed a large number of execution problems in our application due to migration. A reactive technical support and the clear "knowledge base" on the website helped us to identify problem causes and to correct them. In only 2 months, we delivered a fully-tested and renewed .NET application to our customer.

        Damien SEURU
        Project Manager, SOLENT

        Completing the migration of 150K LOCs in a couple months is surely a great example of the high productivity you can reach with VB Migration Partner. Likewise, having to solve just 100 compilation errors instead of 10,000 gives a very clear idea of how far ahead we are if compared to our competitors!

        You can read more about our customers and their experience in our Testimonial page.

      • NETRocksNETRocks commented  ·   ·  Flag as inappropriate


        [CASE STUDY] Xcel Energy, USA

        Xcel Energy recently used VB Migration Partner to migrate a VB6 application consisting of multiple projects for a total of 120,000 lines of code (LOCs). The migration project was a complex one, because of many constraints and requirements, such as the adoption of Rockford Lotcha's CSLA.NET framework, but our conversion software proved to be up to its reputation. In the words of our customer:

        VB Migration Partner was able to correctly parse and convert all of the Forms and ActiveX controls to VB.NET. After analyzing the output and reviewing their on-line knowledge base (which is quite extensive), two pragmas were inserted to reduce the number of conversion errors to a handful in most of the programs. All of the forms could be edited without any further intervention. Grid controls that could not be converted were initially left as red rectangles. Within 2-days, all of the source code was cleaned up with no compiler errors. This meant that the existing presentation layer could be converted from VS6 to VS2008 – so the VB Migration Partner option works very well as part of an overall approach.

        120,000 LOCs were translated to the zero-compilation-error stage in 2 days! This is pure productivity!

        You can read the entire Xcel Energy case study here

      • NETRocksNETRocks commented  ·   ·  Flag as inappropriate


        SnelStart, Netherlands choosed VB Migration Partner and happily migrated 450K LOCs

        We just received this great feedback:

        We have investigated the possibilities for a migration after a presentation of Code Architects at the Microsoft TechEd 2010 in Berlin. Before the presentation we assumed that migration would be too complicated en too expensive. After analyzing four different tools, we chose VB Migration Partner for the migration of our accounting and billing software (450K lines of code).

        The big advantage of VB Migration Partner is that it solves the problems directly in the VB6-code by using “pragmas”. Therefore we don’t have to freeze our code and interrupt the new development in our software. With VB Migration Partner it’s also possible to migrate 1:1. This enables us to offer our customers the same user experience, but this time on a new platform. The final reason for us to choose VB Migration Partner is the (online) service and documentation. The tool and the website contain lots of background information and tips that will help you with the migration.

        Ivo Huizinga
        IT Manager, SnelStart

        Netherland-based SnelStart is just another company who has appreciated the beauty and usefulness of VB Migration Partner's innovative approach based on pragma and its advantages over previous-generation, traditional conversion tools. You can find more example in our User Feedback page.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Isn't it funny how Zagor Tenay/WPF is the Future/Pepe Bronco/Marius Orion compliments him (or her) self on his (or her) own posts...

        >>Fantastic article and link. I fully agree. (WPF is the Future to Zagor Tenay)

        >>Thumbs up for such a wonderful analysis. I totally agree (Pepe Bronco to Zagor Tenay)

        >>Thanks Zagor for posting those links. (WPF is the Future to Zagor Tenay)

        >>I agree 100% with Zagor Tenay. WPF rocks! (Marius Orion to Zagor Tenay)

        And what does Zagor Tenay say ? >> No my friend. I assure you that those people have nothing to do with me and I am not any of them. You are free to believe or not.

        Guess what Zagor Tenay/WPF is the Future/Pepe Bronco/Marius Orion ?
        No one here believes you.

      • Trollfinder GeneralTrollfinder General commented  ·   ·  Flag as inappropriate

        There used to be an obsessive poster here who hid behind the name 'Anonymous'. He posted hundreds of spam comments. He was finally banned by Microsoft last month and all his posts deleted.

        He is now back posting here using multiple names -
        Zagor Tenay
        WPF is the Future
        Pepe Bronco
        Anonymous
        Marcos Triam
        Alan Hughes
        Valerie
        Bill Hutchkins
        Marius Orion
        Michael
        VB6 is Useless
        Olaf Schmidt

        and others.

      • WPF is the FutureWPF is the Future commented  ·   ·  Flag as inappropriate

        @Zagor Tenay

        Fantastic article and link. I fully agree. VB6 was encouraging bad programming and thus shall be thrashed into the history bin. It was good in the 1990s but it means nothing today. NET and especially WPF is the new king and the future.

      • Pepe BroncoPepe Bronco commented  ·   ·  Flag as inappropriate

        @Anonymous

        This is a duplicate forum to this one and shall be deleted. Same subject and discussions, same people. Why is there two uservoice forums with same purpose???

      • Pepe BroncoPepe Bronco commented  ·   ·  Flag as inappropriate

        @Zagor Tenay

        Thumbs up for such a wonderful analysis. I totally agree that VB6 was doomed to fail since the beginning, but it has taught the programming community a good lesson, never to produce such a tool again. Regards.

      • dotNetterdotNetter commented  ·   ·  Flag as inappropriate

        @Zagor Tenay

        >>"Great News"
        >>"WCF Client is Open Source"

        Who uses WCF today ? It is obsolete technology.
        Even when it was used it was too complicated.
        And MS have only open sourced a sub-set of WCF.

        Just like all your "WPF is the Future" spam, this doesn't have any relevance to .Net.
        WPF isn't being open sourced, MS are only dumping their obsolete technologies.

        Try googling JSON, you may learn something. Then give your foolish posting a REST.

      • Zagor TenayZagor Tenay commented  ·   ·  Flag as inappropriate

        To me creation of a tool like VB6 was a very good lesson for the programming community and taught the programming world a good lesson that nobody should produce anything such as VB6 in the future. The reasons may be listed as follows:
        1- VB6 was a "patch-up" tool from the beginning. The VB6 developers at Microsoft were trying to make everybody happy by adding patches here and there, sometimes quite in unorthodox ways. There has never been a top to bottom approach from the beginning. The big picture of the forest was never there. When someone wanted something new, they were planting some more exotic trees into that forest which become slowly but surely an uncontrollable ecosystem, namely a jungle. When they have created VB6, it was that moment, I believe, that things start getting out of control. There were so many unorthodox, unconventional hacks into the heart of windows APIs, that the VB ecosystem started cracking and the collapse would have been imminent, if it had continued as VB7,8,9 ETC...
        2-The other factor that the VB ecosystem was doomed to fail sooner or later, was the fact that the entire windows structure was exposed to programmers through API hooks in dangerous ways. It was an unmanaged way of reaching to the heart of windows which could only worsen the entire operating system. There were OCX and third party vendors, which have mushroomed almost overnight,quite uncontrollable and able to do all kind of hacks without giving any thought about the consequences. Big companies producing important, mission critical code and informed programmers with vision could see that VB6 was sinking in it's own weight. Maintainability, expandability, creating standard coding practices was impossible. It was a dead end. That's why they were more than willing to jump on the managed ecosystem that we call NET today.
        So in short, it was a huge necessity to get rid of a flawed tool called VB ecosystem and design something properly engineered, which would live a long and healthy life.

      • Zagor TenayZagor Tenay commented  ·   ·  Flag as inappropriate

        Great News

        "WCF Client is Open Source"

        What does it mean? Gradually NET is turning into a great cross platform tool. With much richer graphical interface than Java, and enhanced cross communication with multiple platforms and web, IronPython, Xamarin etc., I firmly believe that NET is the future and every serious programmer should get his/her hands on it sooner than later.

        http://www.dotnetfoundation.org/blog/wcf-is-open-source

        "WCF targets the .NET Core framework which is designed to support multiple computer architectures and to run cross-platform. Right now the WCF project builds on Windows, but .NET Core offers the potential for it to run on OS X and Linux."

      • axisdjaxisdj commented  ·   ·  Flag as inappropriate

        HMan, I need to release in a month, would not have time to do a complete rewrite.

      • HManHMan commented  ·   ·  Flag as inappropriate

        I don't understand, you are already completely refactoring your code, why wouldn't you take this opportunity to rewrite it in a more modern language? How is this any different than porting to .NET (or any other language)? Your solution would undoubtedly look better and work better in any other language, and any .NET language will let you sell your app on the store TODAY.

      ← Previous 1 3 4 5 221 222

      Feedback and Knowledge Base