Click here to Skip to main content
Rate this: bad
good
Please Sign up or sign in to vote.
See more: C# licensing
I will sell components for .Net , and i need to protect my product. In your opinion, what should i do?
Posted 9-Jan-13 5:17am
thoahn560
Comments
joshrduncan2012 at 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.
Sergey Alexandrovich Kryukov at 9-Jan-13 10:30am
   
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.)
 
—SA
joshrduncan2012 at 9-Jan-13 10:36am
   
Thanks SA!
Abhishek Pant at 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 at 10-Jan-13 1:31am
   
So, should i use installer that helps licensing (register key , product key ,etc.) ?
Rate this: bad
good
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.
 
—SA
  Permalink  
v2
Comments
Marcus Kramer at 9-Jan-13 10:54am
   
+5.
Sergey Alexandrovich Kryukov at 9-Jan-13 11:39am
   
Thank you, Marcus.
—SA
thoahn at 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 ?
Sergey Alexandrovich Kryukov at 10-Jan-13 2:03am
   
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...
—SA
Rate this: bad
good
Please Sign up or sign in to vote.

Solution 1

Hi,
 
You can give a try with http://licenser.codeplex.com/[^]
 
More Info: Refer my blog http://ranjandotnet.blogspot.in/[^]
  Permalink  

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

  Print Answers RSS
0 DamithSL 485
1 Maciej Los 288
2 OriginalGriff 229
3 Zoltán Zörgő 200
4 BillWoodruff 170
0 OriginalGriff 7,934
1 DamithSL 6,084
2 Sergey Alexandrovich Kryukov 5,449
3 Maciej Los 5,174
4 Kornfeld Eliyahu Peter 4,539


Advertise | Privacy | Mobile
Web02 | 2.8.141223.1 | Last Updated 9 Jan 2013
Copyright © CodeProject, 1999-2014
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