Script BASIC COM

[JRS]

Yes. The Bitbucket repository has all the code for the examples I posted.

[JRS]

As promised, I posted VB6 calling back to Script BASIC script functions.

See latest Script BASIC forum post.

[Mike Lobanovsky]

Yes.

Thanks, John.

Then this maxim

Dave's COM interface is more than an OLE automation interface.

doesn't seem to be well-proven. Calling properties and methods of OLE (= ActiveX) objects (= VB and C# controls) from an inproc (= DLL) server is exactly what "OLE automation interface" stands for. In other words, I'm sorry to say but I'm feeling a little, erm, frustrated since my "looking forward to" expectations have not been satisfied.

In other respects, your SB OLE code looks nice and easy to follow, and this COM-aware extension may indeed be handy for basic interaction with COM based applications.

[JRS]

In other respects, your SB OLE code looks nice and easy to follow, and this COM-aware extension may indeed be handy for basic interaction with COM based applications.

Good enough for me. Thanks for having a peek. Can I ask you to try it on Win 10 when you have time?

Are your VB6 and .NET GUI's compiled as ActiveX DLL's?

You can you use the FREE VB controls edition to create ActiveX DLLs that work with SB COM. (I was successful theming it as well)

[Mike Lobanovsky]

Sure John,

I'll try to do it tomorrow.

[JRS]

I posted an VB5CCE (VB5 Controls Edition) OCX example using SB COM.

I also included a link to download the FREE VB5CCE + xp manifest + help (10.2 MB) if you want to give it a try.

[Mike Lobanovsky]

if you want to give it a try.

Dear John,

IIRC I gave it a try somewhere in early 90's of the last century. Let's however leave "you" in place as an indefinite reference to our juniors who may have never seen VB CCE in action.

[Kuron]

For nostalgia reasons, it is nice to see somebody besides Chris Boss trying to keep VB6 alive.  But, VB6 has had its run and has nothing to offer in this modern era.  Code produced is not remotely optimized for modern processors, does not properly handle multi-threading, and does not support 64-bit.

[Mike Lobanovsky]

Yet it may be a good start before plunging headlong into VB.NET and C#. It was rock solid and very entertaining for its time. And it's still being used by thousands of small businesses and tens of thousands of programmers that cater for the needs of the former.

[JRS]

I agree that VB classic is still widely used. There seems to be considerable effort to keep it relevant by the user base. (theme support, updating libraries, ...) It makes a nice GUI designer for Windows and the SB COM interface is the easiest method I've used so far working with it outside the box.

I'm still interested to see if the SB IDE/Debugger works with Win 10.

[Mike Lobanovsky]

I'm still trying to stand up to my promise to let you see if the SB IDE/Debugger works with Win 10.

[JRS]

Thanks Mike!

It would make me feel better to know my efforts will still be valid on Win 10. It should be interesting news for all VB classic programmers.

[Mike Lobanovsky]

I hasten to inform you that msvbvm60.dll is safe and sound at its usual place in the \system32 folder of Windows 10.

And my computer has just informed me robotically that this is my test of your SB debugger installation.

Slight inconsistencies with GUI control placement/sizing may be corrected in VB6 IDE to allow for generally thicker non-client margins (borders) and taller titlebar under more modern Windows OSes.

(IIRC (but I may be wrong!) mscomctl.ocx is not a redistributable module; it's a licensed component that comes with your legit VB6 installation. But I repeat I may be confusing it with some other one that spells or sounds close enough to that.)

.

[Kuron]

It makes a nice GUI designer for Windows

I do keep VB6 installed as I am slowly porting a lot of old stuff over to a different language.  But you did highlight a VERY good point.  The GUI designer is VERY nice and I have used it with many different languages via custom FRM converters over the years.  I did love VB6 back in the day and it is the RAD IDE that all others should be judged by (the only thing that ever came close for MSVC++ at the time was the third-party Octopod IDE).

[Mike Lobanovsky]

Yes Brice,

I've read a thousand VB6 user messages that the only chance for other BASICs to cause people to leave VB6 behind would be a compatible IDE of at least equal functionality.