VB6-Programming

The twinBASIC programming language is a modern VB6 - and it can import VB6 source code and forms.

The new twinBASIC programming language gives you the simplicity of VB6 with modern powerful features.

The twinBASIC programming language is a modern successor to VB6 - and it can import existing VB6 source code and forms.

You can import VB6 source code and forms into the twinBASIC programming language (with a good expectation it will run first time). And then you can add modern features and upgrade to 64-bit. And it is all familiar to VB6 coders :)

Take a look at the twinBASIC programming language. VB6 compatible and can import VB6 source code and forms and adds modern features too.

Yes, the twinBASIC programming language is a genuine successor to VB6 (and VBA). twinBASIC can import VB6 source code and forms.

And XYplorer will be even faster when it has been upgraded to the VB6 compatible 64-bit twinBASIC programming language with its optimising compiler.

And the VB6 compatible twinBASIC programming language supports unicode and 64 bit compilation - and has a modern IDE. And it can import VB6 source code and forms.

Very true!

PhotoDemon has now been updated to 64 bit using the twinBASIC programming language. twinBASIC is backwards compatible with VB6 (and VBA) and can import VB6 source code and forms.

twinBASIC programming is backwards compatible with VB6 (it intends to be 100% and is very close to that now). Existing VB6 source code and forms can be imported and run (at least as 32 bit apps.). twinBASIC can compile to 64 bit and has many modern features. There is also an optimising compiler. There is a free Community Edition. VBA can also be replaced with twinBASIC programming. Future plans include Linux, MacOS and Android versions.

twinBASIC programming has a free Community Edition.

twinBASIC programming is VB6 compatible and can import VB6 source code and forms.

The 64 bit version of XYplorer is written in the twinBASIC programming language (actually an import of the VB6 source code and forms).

>Looks like you need to call InitCommonControls(Ex), in addtion to the manifest.

Often all you need is the manifest. If the app won't run at all after you have added the manifest, then add a call to InitCommonControls(Ex)