"Larry Heller" <larry.heller nospam at practeng.com> wrote in message
news:usSe6pQaEHA.3524@TK2MSFTNGP12.phx.gbl...
> Hi everyone,
>
> I'm sorry if this has been discussed before, as the news server only has
> posts from the past few days, but I am looking for some recommendations on
> products which discourage reverse engineering of .NET code. Please be
> aware
> that we make heavy use of COM interop.
>
> The products I am considering are:
>
> Obfuscators:
> Dotfuscator Professional Edition
> Salamander Obfuscator
> Wiseowl Demeanor for .NET
> others?
>
> Encapsulators/Code Protectors
> PC Guard for .NET (we also would use this for Win32 modules)
> Salamander Protector
> others?
>
> Any positive or negative experiences, comparative insights or
> recommendations would be appreciated. Also, does anyone know how PC Guard
> works? In particular, how can it encapsulate a .NET assembly and yet still
> work with the CLR assembly loader and strong name verification process?
> Salamander Protector seems to pre-JIT the code (thus making it an x86
> file);
> is this how PC Guard works?
>
> How effective are all these products? Are they easily circumvented?
>
>