quote:
Originally posted by anubis_kree_
eah I just did it then...looks like I'm wrong ...but it does look like a VB application...the first VB application I made was an adding machine actually...
Looks doesn't matter and say nothing.... You can make the same in ASM if you like...
As far as I know, not a single application of Windows is made in VB, and all in C++...
quote:
Originally posted by Mike2
If you reshack it will you see it thingys.
You cant do this if the program is writen with VB
Reshacking doesn't say a thing also... A VB-application can also have resources to look at in reshack...
Reshack only views RESOURCES, nothing more. If the program doesn't use resources then there is nothing to see (this goes for any programming language). Don't think of reshack as the ultimate tool of which you can do almost anything. I suggest to read about what resources actually are in the helpfile of reshack...
Although, this said... it is true that
most VB programs don't have dialog and string resources (etc...) because the dialogs and strings the VB-program uses are stored in the compiled code and not in resources...
So instead of using reshack (which only can view resources which don't realy tell a thing), look at the program with a debugger tool or something to find out which DLL's the programs needs (also strong indicator) or use a hexadecimal/binary viewer to look at its bits and bytes. If the program isn't compressed with an executable-compressor, you can get very good hints there if you know what to look for:
a)
__vbaxxxxx can indicate VB-programming. Although C++ programs in theory could also use these routines, 99% changes are you got a VB-program...
b)
MSVBxxxxx.DLL is a typical DLL needed for VB-programming.
c)
text1,
text2,
Frame1,
Frame2 are standard default names for controls and frames in VB. This also indicates that the programmer didn't change the default names to a more proper name (lazyness?).
d)
Project1 is the default name for a new project you make in VB. (Again lazyness?)
e)
FRM_SIMPLE is a typical indication/name of a simple frame in VB.
f) Browsing thru the bits and bytes, you will always find huge gaps with nothing in VB-programs.
g)
R6009,
R6002 are typical errornumbers in C++.
h) You often find these kind of routines in C++-programs.
i)
Microsoft Visual C++ Runtime Library... Need I say more ...
j)
msvcrt.dll is a typical DLL needed for VC++-programming.
And of course there are many more indicators. If you find many of those, you can be pretty sure of the language in which the program is written...
btw: Every programming language has his own typical "indicators" like that...