Thank's

>Hi Daniel
>
>It is not easy to protect .NET code right out of the box. As you have established, obfuscators are the standard approach. I was involved in a .NET job some time ago where the owner of the code wanted to protect his investment. The only way we could do this was to buy into third party tools that applied quite complex encryption techniques to your distributable files and provide JIT decryption at runtime.
>
>You might have to Google around for these type of tools.
>
>HTH
>
>
>>Hi
>>
>>I'm use Dotfuscator to protect my code , but that app only change my methods a properties to a,b,c and I want to no show anything, How i do that.