Home VS Pro version design help
-
I am working on an app which will have three version named Home (free), Pro (very little cost), Corporate (costly). What is the best approach to accomplish this task? 1- Should I make three different Projects and apply necessary settings accordingly? 2- Should I make two different projects (one for home and pro and one for corp.) and use the settings (the license key) to find out which version user has Installed? 3- Should I make just one project and use the product key to distinguish which version was installed? 3- Other technique... I would appreciate your help and advice. Thanks.
-
I am working on an app which will have three version named Home (free), Pro (very little cost), Corporate (costly). What is the best approach to accomplish this task? 1- Should I make three different Projects and apply necessary settings accordingly? 2- Should I make two different projects (one for home and pro and one for corp.) and use the settings (the license key) to find out which version user has Installed? 3- Should I make just one project and use the product key to distinguish which version was installed? 3- Other technique... I would appreciate your help and advice. Thanks.
Hi, if you trust the licensing key or copy protection mechanism sufficiently to protect the expensive version, I see no point (other than maybe size, or time to market) to create trimmed versions; just let the license stuff control which parts are functional and which are not. That basically is what Microsoft did when they launched XP Home and XP Pro. Dont know about Vista. Hope this helps.
Luc Pattyn
try { [Search CP Articles] [Search CP Forums] [Forum Guidelines] [My Articles] } catch { [Google] }
-
I am working on an app which will have three version named Home (free), Pro (very little cost), Corporate (costly). What is the best approach to accomplish this task? 1- Should I make three different Projects and apply necessary settings accordingly? 2- Should I make two different projects (one for home and pro and one for corp.) and use the settings (the license key) to find out which version user has Installed? 3- Should I make just one project and use the product key to distinguish which version was installed? 3- Other technique... I would appreciate your help and advice. Thanks.
IMO, the best approach is to put the pro only and corporate only functionality in dlls, which are dynamically loaded. That way you have one version, but you never ship people code that they are not allowed to use ( givn that they can decompile your code to remove any blocks that you put in there )
Christian Graus - Microsoft MVP - C++ "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
-
I am working on an app which will have three version named Home (free), Pro (very little cost), Corporate (costly). What is the best approach to accomplish this task? 1- Should I make three different Projects and apply necessary settings accordingly? 2- Should I make two different projects (one for home and pro and one for corp.) and use the settings (the license key) to find out which version user has Installed? 3- Should I make just one project and use the product key to distinguish which version was installed? 3- Other technique... I would appreciate your help and advice. Thanks.
student_rhr wrote:
1- Should I make three different Projects and apply necessary settings accordingly?
That is a bit of redundancy.
student_rhr wrote:
Should I make two different projects (one for home and pro and one for corp.) and use the settings (the license key) to find out which version user has Installed?
You could, but you may run into versioning nightmares.
student_rhr wrote:
3- Should I make just one project and use the product key to distinguish which version was installed?
You could, but someone could look into the code and try to hack a workaround.
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
-
student_rhr wrote:
1- Should I make three different Projects and apply necessary settings accordingly?
That is a bit of redundancy.
student_rhr wrote:
Should I make two different projects (one for home and pro and one for corp.) and use the settings (the license key) to find out which version user has Installed?
You could, but you may run into versioning nightmares.
student_rhr wrote:
3- Should I make just one project and use the product key to distinguish which version was installed?
You could, but someone could look into the code and try to hack a workaround.
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
What is the best industry practice?
-
What is the best industry practice?
I am not 100% sure. It is something that does vary from software shop to software shop.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer