Do I need dotfuscator for C++

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I was just wondering, since normal C++ does not need dotfuscation
because it is not decompilable, what is the situation with C++ Dot Net ?
 
guy,

Since managed C++ is not supported for the Compact Framework, I'm a little
surprised to see your question. But since managed C++ still produces MSIL
like other .Net compilers, it would also need obfuscation to protect it from
the usual IL decompilers. Try it and see!
 
O.k. sorry, I didn't realise C++ was not supported on CF
as I have not used it, but was considering if I should, but
thanks for your reply, it helps to see the large picture
regarding the different languages.
 
All .NET compatable dll's contain a manifest. Obfuscation makes this
manifest less "user-friendly".

In short, yes.

Open your C++ DLL in ILDASM (In the .NET SDK) before and after obfuscation.

--ROBERT

P.S. Anything can be de-compiled :) It's just a matter if how easy and how
long.
 
guy,

It is confusing about C++. Unmanaged C++ for mobile devices will be
supported as part of Visual Studio 2005 (and is supported today in eVC++),
but managed C++ is not supported on the Compact Framework and won't be for
..NetCFv2. Sometimes you can get it to work even in version 1, but it's not
supported.
 
All .NET compatable dll's contain a manifest. Obfuscation makes this
manifest less "user-friendly".

In short, yes.

Open your C++ DLL in ILDASM (In the .NET SDK) before and after obfuscation.

--ROBERT

P.S. Anything can be de-compiled :) It's just a matter if how easy and how
long.
 
Back
Top