2 ms·
Even though they had a pair of great BASIC compilers, IIRC VB/DOS didn't include the ability to create a standalone .EXE file. It was a "bytecode" compiler with
by h2odragon 5y ago
Even though they had a pair of great BASIC compilers, IIRC VB/DOS didn't include the ability to create a standalone .EXE file. It was a "bytecode" compiler with a required "VM/Interpreter" runtime that was rather large.
This was about the time that Microsoft was buying up all the 3rd party BASIC libraries and pulling the redistribution licenses from customers, too.
- p_l 5y agoThe article shows the process to generate a standalone EXE file even ;) (It's one option switch in compilation)
- pjmlp 5y agoVB only got a proper native code compiler on VB 6.0, which was when it got support to produce COM libraries just like C++, until then it could only consume them. Ironically it was taken away with .NET (NGEN was only designed for quick startup scenarios), then got it again with .NET Native (again dropped), and may finally get it back in .NET 7 (lets see if they actually deliver it).
- Koshkin 5y agoCuriously, according to Wikipedia, A free, downloadable Control Creation Edition [of Visual Basic 5.0] was also released for creation of ActiveX controls. Visual Basic 6.0 was the best thing since sliced bread.
- pjmlp 5y agoIndeed, although I think on VB 5, only IDispatch was supported given the ActiveX references. https://news.microsoft.com/1996/12/11/microsoft-visual-basic-5-0-control-creation-edition-launches-explosion-in-component-market/ https://news.microsoft.com/1996/12/11/microsoft-visual-basic...
- wdb 5y agoWhat about PDS Basic?
- h2odragon 5y agoQB 4/ 4.5 and PDS (7? iirc was its version?) were the great MS basic compilers. paired with judicious abuse of assembly tricks they enabled some very cool things.
- blibble 5y agoI used vb1 for dos, it produced standalone exes that required nothing (other than the exe itself)