Can any one tell me of a good VB6 decompiler and where I can find it??

Hi Tony,
I tried to find one for myself. Its very tough to find and I almost searched everywhere. If you find let me know too.
Sajid Mohammed
sajleo@yahoo.com

here you are something about VB decompiler... I didn't try it yet... good luck... if something better email me...thanks

http://www.geocities.com/rayrxu/vbdownload.html

what are you guys talking about when you say "vb 6 decompiler?" maybe i dont know enough about what you are talking about, but if you are looking to find a program that will take a binary file and turn it into vb 6 forms and module code, i doubt there is one. this is because a binary file just dosent contain the origianl info in your forms and stuff, like variable names. how would a decompiler know what language was even used to create the binary file? how would it then rename everything in it as was named by the author? names are just for you, the compiler dosent use em for anything 'cept to make sure the pointers point to the right things. you can decompile things into assembly language though... because that info IS in the binary. you could then translate the assembly into vb 6 instructions if you knew what the heck you were doing. but you would still have to rename all of the variables and re-enter comments, so the meaning of the code may be unclear. thats why people dont make decompilers that translate the assembly language instructions taken from the binary files into vb 6 format. how could a decompiler guess at how you wanted it translated? i think you might want to try a "decompiler" or "debugger" rather than a "vb 6 decompiler"

The Famous VB6Decompiler doesn't exist , and it never will.
'cause the VB 6 compiler, is an "translator" to VC++, all programs you write in vb6 will be converted into c code and compiled for windows, then theres no way to return from binary files to source code.

Lucas

ok then smart-arse... why do we need vb6 runtime files, (msvbvm6whatever.dll), if it is CONVERTED into C, and THEN compiled into an exe?

huh? huh?

msvbvm6whatever.dll s are required only for code that is compiled into p-code.

VB6 has two kinds of output file types:

* Native Code: The ordinary Win32Exes &
* P - Code: This code is interpreted with the
help of the above mentioned dlls

These options are set under the project properties dialog box. One more thing to note is that VB generated only p-code until about version 4.0