Making an executable file with the .vb extension?

[TTn]

Apparently VB6 can make and use executable files with an intermediate file extension (.vb), because it shares compatibility features with eVB3. This intermediate file is a tokenized version of the program, that is CPU-independent. The .vb file appears to invoke an interpreter on Windows 10/11, running the tokenized executable file.

Did this work on XP/Vista/7?
Can anyone make and test a simple hello world application, by adding the .vb extension to the executable name, ie Project1.vb.

Perhaps the most important point to be made is that eMbedded Visual Basic does not contain a compiler. Applications run in an interpreter that is summoned when PVBLOAD.EXE, the Pocket Visual Basic Loader program, is run.

The eMbedded Visual Basic environment does not create an .EXE file, but rather a .VB file that contains a tokenized version of your program. Unlike regular Windows CE executable files, this is a CPU-independent file that can be copied to any Windows CE-based device. That fileâ"plus the runtime libraries and other support files, which are device-dependentâ"are what you need to run a Visual Basic-based program on Windows CE-based device.

eMbedded Visual C++ is practically a clone of Visual C++ 6.0; you'll have to look very hard to find the few places where the two are not the same. Both environments feature familiar editors, menus, and settings windows. Both offer a starting point for building apps, although in this arena the eMbedded Visual C++ environment offers the richer collection.

More details posted about eVB and VB6.