Decompile .NET assemblies to C#
VB Decompiler is a decompiler for programs (EXE, DLL, or OCX) written in Visual Basic 5.0 or 6.0. As you know, a VB program can be compiled either into interpreted p-code or into native code. Originally Answered: How does decompiling an executable (.exe) software file work? The decompiler has at its heart a big table of instruction codes and the assembly language value. It also knows what parameters each instruction has. So it reads a value say 67.
dotPeek is a free-of-charge standalone tool based on ReSharper's bundled decompiler. It can reliably decompile any .NET assembly into equivalent C# or IL code.
The decompiler supports multiple formats including libraries (.dll), executables (.exe), and Windows metadata files (.winmd).
Export decompiled code to Visual Studio projects
As soon as you've decompiled an assembly, you can save it as a Visual Studio project (.csproj). This can potentially save a lot of time if you need to restore lost source code from a legacy assembly.
Download source code and debug third-party code
dotPeek can identify local source code based on PDB files, or fetch source code from source servers such as Microsoft Reference Source Center or SymbolSource.
dotPeek can also perform as a symbol server and supply Visual Studio debugger with the information required to debug assembly code.
dotPeek inherits a lot of features from ReSharper. These include contextual and context-insensitive navigation, usage search, as well as different code structure and hierarchy views.
Find usages of any symbol
Use Find Usages to search for all usages of a symbol, be it a method, property, local variable or a different entity. The Find Results tool window lets you group usages, navigate between them, and open them in the code view area.
Jump to a type, symbol or anything
Whenever you put a caret on a symbol in the code view area, dotPeek offers a plethora of contextual navigation options that are all available via Navigate To drop-down menu.
Navigate to related code
dotPeek indexes all assemblies in your assembly list, as well as all assemblies that they reference, and provides features to quickly jump to specific code. For instance, Go to Everything allows searching for an assembly, namespace, type, member, or a recently opened file.
Long-time users of JetBrains ReSharper will feel at home working with dotPeek as it provides ReSharper-like navigation and search, code insight, and familiar keyboard shortcuts.
dotUltimate: Empowering Your .NET
and Visual Studio Development
dotUltimate is a single license that allows a single developer to use these JetBrains tools:
dotUltimate license also covers plugins for dotCover and dotTrace in Rider.
Decompiler Visual Basic Exe File
VB Decompiler Pro v11.1 Retail Cracked
VB Decompiler is an advanced tool that can decompile programs (EXE, DLL, or OCX) written in Visual Basic 5.0/6.0 and disassemble programs based on .NET technology. As you know, programs written in Visual Basic can be compiled to interpreted p-code or to native code, and a .NET assembly is always compiled to Microsoft intermediate language (MSIL).
Where Is Visual Studio Exe
Source code loss is a very serious problem for many software developers. As most Visual Basic 5.0/6.0 applications were developed a long time ago, their source code (.vbp, .frm, and .bas files) has already been lost due to migrating to a new computer, replacing a hard drive, etc. Based on the experience of most of our customers, we can say that losing source code can be a tragedy. Just imagine that you have written a program, spending a lot of effort, time, and money, but now all that is left is the compiled program (the EXE file with DLL libraries).
Some day you may suddenly discover that your source code is gone. Maybe you have upgraded your PC or migrated your data to another cloud, or your hard drive just failed, and you do not have a backup. You are starting to panic. What should you do? Just take VB Decompiler and decompile most parts of your project! VB Decompiler will recover as much as possible of your source code with a higher success rate than any competitive product.
Visual Basic has two different compilation modes: p-code (pseudo code) and native code (assembler). VB Decompiler can restore the source code from p-code as close to the original one as possible, so after a few modifications you can get some really workable source code. Of course, in case of a program compiled to native code, the decompilation success rate will be lower, but you still can recover up to 70 percent of the original source code. VB Decompiler has a few powerful built-in tools: an x86/x64 disassembler, an emulator for assembler commands, and a tracing engine. Thanks to them, the result of decompiling the binary code will be very close to Visual Basic code. Because of the diversity of modern code optimization and code protection methods, the result will not always be perfect. But in a dire situation like that, VB Decompiler can really help you with software analysis and reverse engineering.
If you develop your software in Visual Studio 2017 (or in VS 2015, 2013, or lower), using .NET Framework - that's no problem! VB Decompiler can easily restore the code structure from the assembly tables and will be useful for disassembling and analyzing the IL code of Visual Basic .NET, C#, or other .NET assemblies.
VB Decompiler does not require that you install .NET Framework. It works fine on any 32-bit or 64-bit Windows system, as well as on any 32-bit or 64-bit Linux system (with Wine), without requiring that you install any additional software.
As you can see, VB Decompiler is an ideal source code analyzing and restoring tool. It is a must-have for VB developers who value their effort, time, and money.
In case of a program compiled to native code, VB Decompiler will recover as much of the source code as possible; it achieves a higher success rate than any competitive product. Even in this situation, VB Decompiler can help you analyze the program. It contains a powerful disassembler/emulator that will try to decode as many assembler instructions as possible to the most likely VB commands. Of course, VB Decompiler may fail on some assembler code optimizations and may be unable to recover some code. However, currently it provides the best approach to analyzing native-code applications.
In case of a program compiled to a .NET assembly, VB Decompiler will recover all tables and modules from a managed assembly and disassemble all methods, functions, and events using the IL disassembler. Decompilation to original source code is not possible at this time, but we provides decompilation service. VB Decompiler does not require the .NET Framework to be installed for decompilation. Decompilation is supported on all 32-bit Windows operating systems.
What's new in this version:
- New processing engine for __vbaObjSet and __vbaHresultCheckObj (Native Code)
- New processing engine for 24 Late calls: __vbaVarLateMemCallLd, __vbaVarLateMemCallLdRf,
__vbaVarLateMemCallSt, __vbaVarLateMemSt, __vbaLateMemSt, __vbaVarLateMemStAd,
__vbaLateMemStAd, __vbaLateIdCall, __vbaLateIdCallLd, __vbaLateIdCallSt, __vbaLateIdSt,
__vbaLateIdStAd, __vbaLateMemCall, __vbaLateMemCallLd, __vbaLateMemCallSt,
__vbaLateIdNamedCall, __vbaLateIdNamedCallLd, __vbaLateIdNamedCallSt, __vbaLateIdNamedStAd,
__vbaLateMemNamedCall, __vbaLateMemNamedCallLd, __vbaLateMemNamedCallSt,
__vbaLateMemNamedStAd, __vbaRaiseEvent. NamedCall's is partially supported. (Native Code)
- Show 'This Control' (variable with assigned active control) and 'Temporary This'
at Tracer window (Tracing features)
- VB .NET decompiler is optimized and refactored
- Tracing is now supported for P-Code functions and procedures. Just
right click on an address in a decompiled or disassembled code (like
loc_00401000) and select same menu link. Opened code will be emulated up
to the selected address and you'll see stack, previous decompiled line,
and current This object. This function works like a breakpoint on a
debugger, but no code executed, only emulated. (P-Code)
- New feature 'Prototypes Analyzer'. Before decompilation, VB Decompiler will
analyze all Private functions and procedures for prototype. It helps to
provide correctly decompiled calls to this procedures and functions. This
feature can be activated in Options and decrease speed of the opening
file (P-Code and Native Code)
- New option for new feature: Parsing 'If' ... 'Else' ... 'End If'
blocks (Native Code)
- 'Add addresses' option now works in P-Code too
- Support vbaNew2 calls for internal Forms, UserControls and Classes (Native Code)
- Objects is now more strong typized (Native Code)
- Decompile 16777215 as 'True' at 'If .. Then' statements (Native Code)
- Filter calls to VB Runtime wrappers using VTable (Native Code)
- Ukrainian translation by Dmitry Prigornitsky
- Show operand for msvbvmXX.dll functions MemLdPr, LateIdLdVar, MemLdUI1,
MemLdI2, MemLdR4, MemLdR8, MemLdFPR4, MemLdFPR8 (P-Code Lite Version)
- Support for global variables as in a P-Code (Native Code)
- Show Dispatch ID and VTable ID for Public and Private
variables (P-Code and Native Code)
- Support a lot of array in a push, mov, add and sub commands:
[reg+reg], [reg-reg], [reg+Address], [reg-Address],
[reg+reg*2] (Native Code)
- Emulator stack size increased to form 16 to 64 dwords (Native Code)
- Decompile 'ExitProcCbHresult' with and without arguments differently (P-Code)
- Doesn't calculate the entropy (test for packed/protected) for files larger than 5Mb.
Increases download speed and is not required for most files.
- Support disassembling of extremely large functions. Correctly find the
finish part of this functions (for functions with up to 100k lines of code)
- Increase speed for saving to file
- Decompilation of 'Err' object with all properties and methods (P-Code and Native Code)
- Increased Native Code decompilation speed
- Database of external OCX/DLL controls is filtered and optimized
- Show all possible arguments at private procedure prototype by
analyzing code of the procedure (Native Code)
- Use different colors for 'Sub' and 'Functions'
- Try to detect type of the procedure, declared as Private (Sub or Function)
- Filter 'Select Case' jump tables at the end of function (Native Code)
- Declare User Defined Types (UDT) and public variables. For UDT VB Decompiler
show size of the structure and count of string fields. For Public variables
VB Decompiler show name and type
- Add support for msvbvmXX.dll APIs: __vbaR8IntI2, __vbaR8IntI4,
__vbaVargVarCopy, __vbaRedimVar, __vbaVarSetObjAddref, __vbaVarSetUnk,
__vbaVarSetUnkAddref, __vbaVarSetVarAddref, __vbaVarXor, __vbaVarNot
__vbaPowerR8, __vbaVarLateMemSt, __vbaStrLike, __vbaStrTextLike,
__vbaVarLike, __vbaVarTextLike, __vbaVarTextLikeVar, __vbaVarLikeVar,
__vbaDerefAry1, __vbaVargVarRef (Native Code)
- Add partially support for msvbvmXX.dll APIs: __vbaRecAnsiToUni,
__vbaRecAssign, __vbaRecDestruct, __vbaRecDestructAnsi, __vbaRecUniToAnsi
- Add support for msvbvm50.dll APIs: __vbaVarTextCmpEq, __vbaVarTextCmpNe,
__vbaVarMod (Native Code)
- Show variables for msvbvmXX.dll functions: __vbaVarOr,
__vbaVarNeg, __vbaVarMod, __vbaVarMul, __vbaVarPow, __vbaVarDiv,
__vbaVarIdiv
- Support RegExp2 class from vbscript.dll
- Support 'Select Case' statements with more than 255 cases (Native Code)
- Search in a variables at Tracer window (Tracing features)
- Save current Date/Time to the header of text file (Save all in one module)
- Support for Objects: Form.Controls.X, MDIForm.Controls.X, UserControl.Controls.X,
PpropertyPage.Controls.X, UserDocument.Controls.X, ListView.Items.X
- Emulation for direct assembler 'Or' command with variables.
Usually Visual Basic use __vbaVarOr or same APIs, but with __vbaXXXLike
Visual Basic use native 'Or' (Native Code)
- Support loading 4 and 8 byte floats from address by fild FPU command (Native Code)
- Open binary file from *.lnk file. Pure binary parsing, APIs or WScript is not used.
Not all types of *.lnk files is supported.
- BugFix: Update decompiled code after editing any string in String References
- BugFix: Decompile names of global variables in classes
(if it saved to the binary file)
- BugFix: Decompile msvbvmXX.dll function MemLdPr (P-Code)
- BugFix: Decompile msvbvmXX.dll functions: __vbaR4ErrVar, __vbaR8ErrVar,
__vbaR4Var, rtcRandomNext, __vbaBoolVar
- BugFix: Decompile msvbvm50.dll functions: __vbaRedim, __vbaRedimPreserve
- BugFix: Correctly process prototype of the function with more
than the nine parameters parameters via the stack
- BugFix: Correctly process 'End If' in some cases then this address is filtered
by 'Procedure analyzer and optimizer'
- BugFix: Correctly process object properties Left/Top/Width/Height
as Single floating point (Native Code)
- BugFix: Correctly process 'End If' and other block-closing commands in some cases,
if 'Add Address' option is unchecked (Native Code)
- BugFix: Processing strings with only quote (') and apostrophe (') chars
Only for V.I.P