5 ms·
It was useful for more than that. We built most of our COM components in C++. As we started prototyping COM components in VB... and discovered they were only
by heelix 4y ago
It was useful for more than that. We built most of our COM components in C++. As we started prototyping COM components in VB... and discovered they were only about 5% slower and very easy to crank out. It was a heretical discovery kept very quiet.
- sumtechguy 4y agoCOM in C++ ... shudder. That interface was very nicely hidden in VB6. It could be done in C++ but getting the typing and interface correct was awful. That switching to vb6 to make com components was easier was my exp as well. That VARIANT struct they created was a nightmare to do correctly. Which you would use a lot if you thunked between VB6 and C++.
- pjmlp 4y agoIn case you miss doing it, the new C++/WinRT is hardly any better.
- electroly 4y agoSimilarly I reached for VB6 any time I needed to consume a COM component. Stunningly easy compared to the absolute nightmare of consuming COM in C++. There really was no better way to do it than VB6.
- ptx 4y agoPython with pywin32 [1] was also, and still is, a pretty good way to work with COM APIs. There is a book on it [2] from twenty years ago that is still surprisingly applicable. [1] https://github.com/mhammond/pywin32/ https://github.com/mhammond/pywin32/ [2] https://www.amazon.com/Python-Programming-Win32-Windows-Programmers/dp/1565926218 https://www.amazon.com/Python-Programming-Win32-Windows-Prog...