On Thu, 24 Apr 2008 03:14:26 -0700, _DD <_D*@nospam.com wrote:
Is there any practical way to protect .NET demo programs from being
reverse-engineered?
With what kind of reliability?
In general, the answer is "no". The basic issue is that the more value
you put on not having the code reverse-engineered, the more value someone
else will put on actually doing so. Since it is literally impossible to
protect your code from reverse-engineering unless you simply don't provide
access to it, it's a losing battle on your part.
You can use obfuscators, and these will provide a small margin of
protection against the casual inspector. But beyond that, you'll never be
able to justify a cost for any attempt to block reverse-engineering that
is high enough to protect against a sufficiently motivated hacker.
If you don't want people to see your code, don't give it to them.
Pete
