Is VC++ native executables of Visual Studio 2005 safe?

[enum5]

My company is finding more suitable language, which can be more safe to protect its IP. I read one interesting thread in the link below.

http://www.vbforums.com/showthread.p...ight=decompile

From what I understand, some experts said that the native executables created by using VB6 is hard to decompile back to original source code or impossible.

How about the native executables created by C++ in Visual Studio 2005? Is it possible to decompile back to original source code? Is the native executables created by Visual Studio 2005 also hard to be decompiled like VB6?

Please advice. Thanks.

[sunburnt]

My company is finding more suitable language, which can be more safe to protect its IP. I read one interesting thread in the link below.

http://www.vbforums.com/showthread.p...ight=decompile

From what I understand, some experts said that the native executables created by using VB6 is hard to decompile back to original source code or impossible.

How about the native executables created by C++ in Visual Studio 2005? Is it possible to decompile back to original source code? Is the native executables created by Visual Studio 2005 also hard to be decompiled like VB6?

Please advice. Thanks.

C/C++ compile directly to machine code. It is not feasible to go from machine code back to a higher-level language; at best you can get assembly.

In fact, most languages compile to machine code, with a few exceptions.

JAVA and .NET compile to byte code, which is easier to translate back into their respective languages.

Earlier versions of Visual Basic compiled to P-CODE, which is similar to byte code and could be decompiled. VB5/6 can compile to P-CODE, but by default they compile to machine code as well. They are, however, slightly easier to reverse because they make so many API calls to the VB Runtime.


Hope this helps.