WinRT : A case for VB6 (classic VB)
-
As we discussed the other day, VB6 was the best COM client ever! The big hassle though was that it could only handle
IDispatchor dual interfaces. Well, we don't haveIDispatchanymore but we do haveIInspectable. It should not be too hard to update VB6 to handleIInspectable. 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. :-DRegards, Nish
My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics
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
-
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
:laugh:
Regards, Nish
My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics
-
As we discussed the other day, VB6 was the best COM client ever! The big hassle though was that it could only handle
IDispatchor dual interfaces. Well, we don't haveIDispatchanymore but we do haveIInspectable. It should not be too hard to update VB6 to handleIInspectable. 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. :-DRegards, Nish
My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics
Nishant Sivakumar wrote:
The big hassle though was that it could only handle
IDispatchor 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.
-
Nishant Sivakumar wrote:
The big hassle though was that it could only handle
IDispatchor 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.
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
-
Nishant Sivakumar wrote:
The big hassle though was that it could only handle
IDispatchor 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.
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
-
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
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 -
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 KreskowiakAh 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
-
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 KreskowiakUnless you have text to speech turned on for your browser, you probably just saw him say it rather than hearing him. :laugh:
-
As we discussed the other day, VB6 was the best COM client ever! The big hassle though was that it could only handle
IDispatchor dual interfaces. Well, we don't haveIDispatchanymore but we do haveIInspectable. It should not be too hard to update VB6 to handleIInspectable. 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. :-DRegards, Nish
My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics
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
-
As we discussed the other day, VB6 was the best COM client ever! The big hassle though was that it could only handle
IDispatchor dual interfaces. Well, we don't haveIDispatchanymore but we do haveIInspectable. It should not be too hard to update VB6 to handleIInspectable. 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. :-DRegards, Nish
My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics
Noooo!!! Burn the heretic!
-
Noooo!!! Burn the heretic!
:-D
Regards, Nish
My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics
-
As we discussed the other day, VB6 was the best COM client ever! The big hassle though was that it could only handle
IDispatchor dual interfaces. Well, we don't haveIDispatchanymore but we do haveIInspectable. It should not be too hard to update VB6 to handleIInspectable. 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. :-DRegards, Nish
My technology blog: voidnish.wordpress.com Part 2 in my WinRT/C++ series : Visual C++ and WinRT/Metro - Databinding Basics
-
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.
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