ocx, etc.) was compiled using Visual Basic 5 / 6 and with what compilation mode (native or P-Code ?). You all know that Visual Basic 6 allows you to choose between Native Code and P-Code compilation.īecause one of the most recurrent questions of my customers was if VBReFormer Pro will support decompilation of their application, due to the simple fact they don’t know if it was compiled in Native or P-Code, I’ve made a tool called “VBCompTester”, some years ago, which show you if a binary file (.exe. Load (or not) the project in Visual Basic, or the destination folder once you saved itįixed issue on Font properties in property editor and GUI editionįixed issue on default language setting (French was setup by default, now replaced by English language).įixed issue on VBReFormer setup packages for 圆4 Windows operating systemįixed issue at loading some ActiveX libraries (“Run-time error `339` Component `MSCOMCT2.OCX or one of its dependencies not correctly registered. “)įixed issue on re-opening a VB6 application / library previously edited with VBReFormer Proįixed issue on resource image preview, export, and replacementįixed issue on false negative detection of VBReFormer by antivirus or browsers as malicious softwareįixed “Object not found” exception at opening some executable New: New settings windows that allows to:Įdit colors of source code’s syntax highlightingĬhoose if you want only Visual Basic, assembly, or both (mixed) differently for viewing and savingĬhoose your own prefix for private method and private variable name New: Support of COM / OLE property edition New: Support of OLE, PropertyPage, and UserDocument elements in GUI recovery & edition New: support of type consistency at decompilation time, this means that the decompiler engine can now be determinist about variable type New: Improved support of string statements:
New: Improved support of internal system statements: New: Improved support of FOR / NEXT loop-related statements: New: Improved support of array-related statements: New: Improved support of error statements: New: Improved support of file I/O operation statements: Lot of other improvement has been made, here is the full details:
We also added for/next support, and multi-dimensional array-related statements decompilation.ĭim myArr1(0 To 20, 14 To 50, 25 To 45) As Stringĭim var_2 (0 To 20, 14 To 50, 25 To 45) As String This means that VBReFormer is now able to guess the type of a variable and argument from its use inside the code. The decompiler engine has been improved as it can now perform variable type determination. This new version improve such a lot the decompiler engine and this is one of the most important release I’ve done until now. As annouced previously, we just release the Free and Professional editions of VBReFormer 6.4.
0 kommentar(er)
