Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. WinRT : A case for VB6 (classic VB)

WinRT : A case for VB6 (classic VB)

Scheduled Pinned Locked Moved The Lounge
c++phpcomannouncement
16 Posts 8 Posters 2 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Nish Nishant

    As we discussed the other day, VB6 was the best COM client ever! The big hassle though was that it could only handle IDispatch or dual interfaces. Well, we don't have IDispatch anymore but we do have IInspectable. It should not be too hard to update VB6 to handle IInspectable. Update: That was wrong. It's VBScript that needs dispatch. VB6 actually works more efficiently with COM interfaces. Thanks to Rama for the correction. So basically VB6 is already a good candidate as a WinRT consumer :-) And voila! We now have a fast, easy to use, 100% native code language for consuming WinRT. :-D

    Regards, Nish


    My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

    D Offline
    D Offline
    Dave Kreskowiak
    wrote on last edited by
    #2

    I just threw up in my mouth a little bit. Did I just hear you say VB6 had an actual use??

    A guide to posting questions on CodeProject[^]
    Dave Kreskowiak

    N M 2 Replies Last reply
    0
    • D Dave Kreskowiak

      I just threw up in my mouth a little bit. Did I just hear you say VB6 had an actual use??

      A guide to posting questions on CodeProject[^]
      Dave Kreskowiak

      N Offline
      N Offline
      Nish Nishant
      wrote on last edited by
      #3

      I always thought you were a VB6 sympathizer.

      Regards, Nish


      My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

      D 1 Reply Last reply
      0
      • N Nish Nishant

        As we discussed the other day, VB6 was the best COM client ever! The big hassle though was that it could only handle IDispatch or dual interfaces. Well, we don't have IDispatch anymore but we do have IInspectable. It should not be too hard to update VB6 to handle IInspectable. Update: That was wrong. It's VBScript that needs dispatch. VB6 actually works more efficiently with COM interfaces. Thanks to Rama for the correction. So basically VB6 is already a good candidate as a WinRT consumer :-) And voila! We now have a fast, easy to use, 100% native code language for consuming WinRT. :-D

        Regards, Nish


        My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

        N Offline
        N Offline
        Nagy Vilmos
        wrote on last edited by
        #4

        Why don't you go the whole hog and borrow Sean's mankini?


        Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett

        N 1 Reply Last reply
        0
        • N Nagy Vilmos

          Why don't you go the whole hog and borrow Sean's mankini?


          Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett

          N Offline
          N Offline
          Nish Nishant
          wrote on last edited by
          #5

          :laugh:

          Regards, Nish


          My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

          1 Reply Last reply
          0
          • N Nish Nishant

            As we discussed the other day, VB6 was the best COM client ever! The big hassle though was that it could only handle IDispatch or dual interfaces. Well, we don't have IDispatch anymore but we do have IInspectable. It should not be too hard to update VB6 to handle IInspectable. Update: That was wrong. It's VBScript that needs dispatch. VB6 actually works more efficiently with COM interfaces. Thanks to Rama for the correction. So basically VB6 is already a good candidate as a WinRT consumer :-) And voila! We now have a fast, easy to use, 100% native code language for consuming WinRT. :-D

            Regards, Nish


            My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

            R Offline
            R Offline
            Rama Krishna Vavilala
            wrote on last edited by
            #6

            Nishant Sivakumar wrote:

            The big hassle though was that it could only handle IDispatch or dual interfaces.

            Any C++/COM developer who has programmed in VB will know that the above statement is not correct. :) So no one has to do any work to support WinRT.

            N 2 Replies Last reply
            0
            • R Rama Krishna Vavilala

              Nishant Sivakumar wrote:

              The big hassle though was that it could only handle IDispatch or dual interfaces.

              Any C++/COM developer who has programmed in VB will know that the above statement is not correct. :) So no one has to do any work to support WinRT.

              N Offline
              N Offline
              Nish Nishant
              wrote on last edited by
              #7

              Yeah, my mistake. It's VBScript that needs dispatch! Thanks - will update the OP! :-)

              Regards, Nish


              My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

              1 Reply Last reply
              0
              • R Rama Krishna Vavilala

                Nishant Sivakumar wrote:

                The big hassle though was that it could only handle IDispatch or dual interfaces.

                Any C++/COM developer who has programmed in VB will know that the above statement is not correct. :) So no one has to do any work to support WinRT.

                N Offline
                N Offline
                Nish Nishant
                wrote on last edited by
                #8

                OP has been updated. Thanks again.

                Regards, Nish


                My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

                1 Reply Last reply
                0
                • N Nish Nishant

                  I always thought you were a VB6 sympathizer.

                  Regards, Nish


                  My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

                  D Offline
                  D Offline
                  Dave Kreskowiak
                  wrote on last edited by
                  #9

                  Oh God, that's offensive! ;) I started getting rid of my VB6 development the day I got my hands on the C# and VB.NET Beta bits back in 2001. Yes, I was writing code in Notepad and compiling it on the command line and found it better than VB6.

                  A guide to posting questions on CodeProject[^]
                  Dave Kreskowiak

                  N 1 Reply Last reply
                  0
                  • D Dave Kreskowiak

                    Oh God, that's offensive! ;) I started getting rid of my VB6 development the day I got my hands on the C# and VB.NET Beta bits back in 2001. Yes, I was writing code in Notepad and compiling it on the command line and found it better than VB6.

                    A guide to posting questions on CodeProject[^]
                    Dave Kreskowiak

                    N Offline
                    N Offline
                    Nish Nishant
                    wrote on last edited by
                    #10

                    Ah good to know :-)

                    Regards, Nish


                    My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

                    1 Reply Last reply
                    0
                    • D Dave Kreskowiak

                      I just threw up in my mouth a little bit. Did I just hear you say VB6 had an actual use??

                      A guide to posting questions on CodeProject[^]
                      Dave Kreskowiak

                      M Offline
                      M Offline
                      Marc A Brown
                      wrote on last edited by
                      #11

                      Unless you have text to speech turned on for your browser, you probably just saw him say it rather than hearing him. :laugh:

                      1 Reply Last reply
                      0
                      • N Nish Nishant

                        As we discussed the other day, VB6 was the best COM client ever! The big hassle though was that it could only handle IDispatch or dual interfaces. Well, we don't have IDispatch anymore but we do have IInspectable. It should not be too hard to update VB6 to handle IInspectable. Update: That was wrong. It's VBScript that needs dispatch. VB6 actually works more efficiently with COM interfaces. Thanks to Rama for the correction. So basically VB6 is already a good candidate as a WinRT consumer :-) And voila! We now have a fast, easy to use, 100% native code language for consuming WinRT. :-D

                        Regards, Nish


                        My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

                        A Offline
                        A Offline
                        Andy Brummer
                        wrote on last edited by
                        #12

                        Nishant Sivakumar wrote:

                        Update: That was wrong. It's VBScript that needs dispatch. VB6 actually works more efficiently with COM interfaces.

                        As long as it is compatable and there is a typelib. :-\ I can't believe that I still remember that crap. :doh:

                        Curvature of the Mind now with 3D

                        1 Reply Last reply
                        0
                        • N Nish Nishant

                          As we discussed the other day, VB6 was the best COM client ever! The big hassle though was that it could only handle IDispatch or dual interfaces. Well, we don't have IDispatch anymore but we do have IInspectable. It should not be too hard to update VB6 to handle IInspectable. Update: That was wrong. It's VBScript that needs dispatch. VB6 actually works more efficiently with COM interfaces. Thanks to Rama for the correction. So basically VB6 is already a good candidate as a WinRT consumer :-) And voila! We now have a fast, easy to use, 100% native code language for consuming WinRT. :-D

                          Regards, Nish


                          My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

                          D Offline
                          D Offline
                          djdanlib 0
                          wrote on last edited by
                          #13

                          Noooo!!! Burn the heretic!

                          N 1 Reply Last reply
                          0
                          • D djdanlib 0

                            Noooo!!! Burn the heretic!

                            N Offline
                            N Offline
                            Nish Nishant
                            wrote on last edited by
                            #14

                            :-D

                            Regards, Nish


                            My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

                            1 Reply Last reply
                            0
                            • N Nish Nishant

                              As we discussed the other day, VB6 was the best COM client ever! The big hassle though was that it could only handle IDispatch or dual interfaces. Well, we don't have IDispatch anymore but we do have IInspectable. It should not be too hard to update VB6 to handle IInspectable. Update: That was wrong. It's VBScript that needs dispatch. VB6 actually works more efficiently with COM interfaces. Thanks to Rama for the correction. So basically VB6 is already a good candidate as a WinRT consumer :-) And voila! We now have a fast, easy to use, 100% native code language for consuming WinRT. :-D

                              Regards, Nish


                              My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

                              M Offline
                              M Offline
                              Mark AJA
                              wrote on last edited by
                              #15

                              It's amazing how many times I see someone answering a question about VBA, VBNet or VBScript, and thinks it's Visual Basic. There are some similarities between these languages, but the deeper you dig the bigger the differences are.

                              N 1 Reply Last reply
                              0
                              • M Mark AJA

                                It's amazing how many times I see someone answering a question about VBA, VBNet or VBScript, and thinks it's Visual Basic. There are some similarities between these languages, but the deeper you dig the bigger the differences are.

                                N Offline
                                N Offline
                                Nish Nishant
                                wrote on last edited by
                                #16

                                Yeah, my bad :sigh:

                                Regards, Nish


                                My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics

                                1 Reply Last reply
                                0
                                Reply
                                • Reply as topic
                                Log in to reply
                                • Oldest to Newest
                                • Newest to Oldest
                                • Most Votes


                                • Login

                                • Don't have an account? Register

                                • Login or register to search.
                                • First post
                                  Last post
                                0
                                • Categories
                                • Recent
                                • Tags
                                • Popular
                                • World
                                • Users
                                • Groups