Source code recovery
From the EXE, DLL or OCX, we rebuild the project, reopen it in Visual Basic 6, fix what blocks compilation and deliver a project that recompiles, with a report of what was found and what was not.
The software does most of the work. When you also need someone who has known Visual Basic 6 since 1999, the binary format and what the IDE agrees to reload, this is the place. The work is done by the publisher of VBReFormer, in France, with the tools you see on this site.
From the EXE, DLL or OCX, we rebuild the project, reopen it in Visual Basic 6, fix what blocks compilation and deliver a project that recompiles, with a report of what was found and what was not.
A fix to make, a caption to change, a connection to update in a program nobody has the source of any more: we work on the recovered project or directly on the compiled binary, and document what was done.
Before migrating, you need to know what the application contains: modules, dependencies, third-party controls, data access, code volume. We produce that inventory from the binary, with or without the source, so that the decision and the estimate rest on facts.
A Visual Basic executable nobody knows the purpose of: we decompile it and report on its behaviour, calls, strings, network and file access. VBReFormer is also the Visual Basic analysis component of Malva.RE, our static malware analysis platform.