G
Guest
Hi,
If this is a stupid question, please accept my apologies!
I want to create 'trial' based software that expires after 30 days unless
the user purchases a licence.
However, it generally doesn't take long before some smartass has cracked the
software and posted in emule/edonkey, etc!
Generally these cracks come in the form of a replacement .dll that has
bypasses the checks made in the original .dll.
Since it is possible to strong name all libraries in your application and
make the application die if the correct strong name is not applied to one of
the libraries, does this make .net applications more/less/as secure than
'traidional' EXEs ?
I guess where I am leading is...
"What is the most effective way of protection applications from cracks?"
I appreciate that absolutely nothing will keep the crackers away if they are
persistent enough but I am looking for something that will make cracking my
app as difficult as possible.
Any ideas?
Best wishes.
If this is a stupid question, please accept my apologies!
I want to create 'trial' based software that expires after 30 days unless
the user purchases a licence.
However, it generally doesn't take long before some smartass has cracked the
software and posted in emule/edonkey, etc!
Generally these cracks come in the form of a replacement .dll that has
bypasses the checks made in the original .dll.
Since it is possible to strong name all libraries in your application and
make the application die if the correct strong name is not applied to one of
the libraries, does this make .net applications more/less/as secure than
'traidional' EXEs ?
I guess where I am leading is...
"What is the most effective way of protection applications from cracks?"
I appreciate that absolutely nothing will keep the crackers away if they are
persistent enough but I am looking for something that will make cracking my
app as difficult as possible.
Any ideas?
Best wishes.