Protecting code when distributing demo programs

  • Thread starter Thread starter _DD
  • Start date Start date
D

_DD

Is there any practical way to protect .NET demo programs from being
reverse-engineered? This will be for a one-shot thing, and I'm far
from making any money on this, so I'd prefer an economical solution if
that's available.

I'm thinking a combination of code 'obfuscation' and maybe a timeout,
but I don't know what is available for either. I'm open to other
suggestions in addition to those.
 
Is there any practical way to protect .NET demo programs from being
reverse-engineered?  This will be for a one-shot thing, and I'm far
from making any money on this, so I'd prefer an economical solution if
that's available.

I'm thinking a combination of code 'obfuscation' and maybe a timeout,
but I don't know what is available for either. I'm open to other
suggestions in addition to those.
Click to expand...

obfuscation is your best bet. But if you have no commercial license
you will have to use the community version provided in the IDE
 
Back
Top