Once install permitted for c# program

Question

0.00/5 (No votes)

See more:

hey ...
i wrote a software and wanna publish it ...
i want one customer who buy my soft, just intall on one pc ... means peremitted just install once! or atleast on one pc just install ...
im asking for some idea! and how should do this!
i think its better we have central controller program to allow instal or not! whats your idea about this plan?

EDIT
i want check current install package used before or not with the visual studio setup project and custom action !
for this i should use for overriedn methods , install,unistall,commit and rollback ! i want do my propose whit a ustomer information form... in which one of the above overriden methods i should check this? commit ? so how i recognize user is in customer information form to write fit codes ?

thanks all!

Posted 21-Apr-13 2:04am

ali_heidari_

Updated 21-Apr-13 8:48am

v2

Add a Solution

1 solution

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)

OriginalGriff · Answer 1 · 2013-04-21T02:20:00

Copy protection generally comes in two varieties:
1) Annoying to legitimate users
and
2) Completely useless.

You have to work out how long it will take you to implement copy protection, and balance the cost of that against the savings against piracy you think you will make. If you are expecting to sell one copy, then you don't need copy protection. If you are expecting to sell 100,000 copies, then you may - but remember that Adobe et.al. invest millions in copy protection. And the cracked versions are on torrent sites the same day the release version is shipped...

If you want to proceed, then start with google: Protect my software C#[^] - there are a huge number of ways to do it.