software distribution issues to clients

Question

0.00/5 (No votes)

See more:

.NET3.5

Hi All,

I have few questions please share your ideas. You may find this question interesting.

1) I have developed a windows application. Sometimes client ask me to send them exe of you application they want to see its functionality. In that case, they already get my software. <b>What I want to include is a kind of trial period functionality in it so that he/she can use it only use it for specific time duration.</b>

2) Few of clients ask for complete code also. Now what I am thinking is he/she can further sale to N number of client. <b>So I want some kind of functionality in code. Whenever he will sale to someone I will get intimation.</b>

Any idea regarding this issue, Any key generations can solve this.

I need idea how to solve this issue. So that I can implement it in my product.

Thanks in advance.

Posted 19-Jun-11 18:53pm

sunder.tinwar

Updated 19-Jun-11 19:17pm

v2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

SvenMe · Answer 1 · 2011-06-19T18:59:00

Solution 1

Hi,

you are looking probably for an obfuscation solution.
There are many products out there. Just try to google it.

A quite cheap one is for example .Net Reactor which comes also with some basic licensing functionality (http://www.eziriz.com/[^])

EDIT
----------------------------------------------------
Ah ok. Then I got you wrong :) Maybe this will help you Application Trial Maker[^] or if you are only interested in some ideas http://www.codeproject.com/Messages/2901545/Create-dll-file-and-add-implement-trial-period.aspx[^]

Best regards

Posted 19-Jun-11 18:59pm

SvenMe

Updated 19-Jun-11 19:22pm

v2

Comments

sunder.tinwar 20-Jun-11 1:08am

hi thanks for reply, I know this kind of functionality already exits in many products in market.

I want to implement similar functionality. I need idea how to solve this issue.

So that I can implement it in my product.

Thanks

SvenMe 20-Jun-11 1:19am

Ah ok. Then I got you wrong :)
Maybe this will help you

http://www.codeproject.com/KB/cs/Trial_Maker.aspx
or if you are only interested in some ideas
http://www.codeproject.com/Messages/2901545/Create-dll-file-and-add-implement-trial-period.aspx

thatraja 20-Jun-11 1:23am

Hi, you can update your answer by clicking Improve solution button on your answer.

thatraja 20-Jun-11 1:24am

BTW now I have updated your answer & do the same here after which is easy to you & best for OP

SvenMe 20-Jun-11 1:28am

Thank you.

sunder.tinwar 20-Jun-11 1:59am

thanks shoputer for reply your first solution trial maker looks good. I need to explore more something in this area only. Something like this only.

Roger Wright · Answer 2 · 2011-06-19T19:51:00

I've got a couple of ideas, though I'm not a good enough programmer to implement them...

For the first issue, a time-limited distribution of your software, have the installer contact a time server - not a local one - using the Windows Time Service to record when it was installed. Add to your code a function to check the current datetime against the installation datetime value, and disable it if the allotted time has passed. It's too easy for users to evade time limitations by changing the local PC time, and this will avoid that risk.

On the second issue, reselling your software, have the installer capture a signature of each machine it's installed on using stuff like the CPU idenitity code and the PCI codes of all the installed devices, then send this code to a website under your control. You might also try to capture the identity of the computer from which the illegal copy was made in the same message. You can then fabricate a disabling message to return to the source machine to render the illegal installation useless, perhaps including a "Buy Now!" popup.

There are some really good reasons for a client to ask for the source code, so don't limit your sales by removing that option. But do protect yourself as best you can, and accept that no protection is perfect.

As usual, the details are left as an exercise for the student...:-)