A lot of apps, for instance, have a free version and pro version. Do programmers, when a new update is released, remove lines of code that shouldn't be available in the free version? As for Visual Studio. Or demos. Or a lot of things actually.
closed as too broad by Robert Harvey, Jimmy Hoffa, Blrfl, Bart van Ingen Schenau, MichaelT Aug 19 '14 at 19:54There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question. |
|
How about compile time pre-processor directives? define FREE (or whatever you want to call your flag) in your compiler settings on Visual Studio and some features would not be built into the code. |
|||||
|
Nothing environment specific, but security-wise it would be smart to not include the entire architecture in the "Full Version," because "Free-Trials" tend to be easier to crack/reverse-engineer. |
|||||||||||||
|
#ifdef FREE_VERSION
compile time switch that surrounds code that's run only in free version, orif (is_premium) {...
runtime switch that checks whether correct license is provided, or another kind of switch. – ikh Aug 19 '14 at 18:23