Click here to Skip to main content
13,145,851 members (51,081 online)
Rate this:
Please Sign up or sign in to vote.
See more:
I will sell components for .Net , and i need to protect my product. In your opinion, what should i do?
Posted 9-Jan-13 4:17am
joshrduncan2012 9-Jan-13 10:24am
What do you mean "protect your product"? That is a broad term. Do you want to ssl your product, if so, digital signature certs are a recommendation.
You are right. But... please see my answer.

SSL has nothing to do with protection. They protect users from phishing, not publishers. (Well, there is also a user certificate, I did not mean it, it's rarely used.)

joshrduncan2012 9-Jan-13 10:36am
Thanks SA!
Abhishek Pant 9-Jan-13 11:48am
well ,Sergey Alexandrovich Kryukov explained very well below ;If you still want you can use installshield(full version) to make your setup of your products!
thoahn 10-Jan-13 1:31am
So, should i use installer that helps licensing (register key , product key ,etc.) ?
Rate this: bad
Please Sign up or sign in to vote.

Solution 2

Everything written for .NET can be reverse-engineered easily enough, due to the nature of CIL and .NET. There are reverse-engineering programs; and authors claim that each and every well-known protection product is not a problem for them. I can understand why.

I seriously recommend you to consider working without any protection. If some your user is a regular user, you won't really loose anything, but the fair use will be easy. If the user is a pirate, you have no a chance to withstand. Or you can use some really light protection, to filter out only those who would just make a couple of copies for friends without any efforts. At the same time, protection is a serious hassle for development and testing, and it is always at least some hassle for the fair use, so it will repel some users.

You can compensate it by providing service and other incentives for registered users.

At least, think about all that.

Marcus Kramer 9-Jan-13 10:54am
Thank you, Marcus.
thoahn 10-Jan-13 1:39am
Thanks for explaining Sergey. But i have a question more; In order to license my product ( with registry code , license key , etc. ) should i use installer which allows it, or is there anything else which you recommend ?
I'm not familiar with installer-based approach. Of course, you can add any arbitrary files to the installation, but how can it help licensing scenario? I'll try to explain:

These things are not directly related. One usual approach is that the product is installed without any key, for evaluation. It's your business to recognize the key and decide what to do depending on it: limit functionality, time of use, etc. When the key is obtained, the user gets the instruction to install the key. (It could be simply copied to the application directory.) On next start of the application, you recognize the key and then proceed with your runtime accordingly...
Rate this: bad
Please Sign up or sign in to vote.

Solution 1


You can give a try with[^]

More Info: Refer my blog[^]

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy |
Web03 | 2.8.170915.1 | Last Updated 9 Jan 2013
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100