How to manage two apps
-
I'm creating two version of a program: A free version (myprogram) and an enhanced version (myprogram_PRO). The source code has to be released with the free version since it will be open source. Is there some way to have both programs in the same project? I can create two projects but if I make a change to one version then I have to be sure to update the other. If I have to add a dialog, for example, then it is not a simple matter to make everything match between the two. Any suggestions? Using .Net Jack
-
I'm creating two version of a program: A free version (myprogram) and an enhanced version (myprogram_PRO). The source code has to be released with the free version since it will be open source. Is there some way to have both programs in the same project? I can create two projects but if I make a change to one version then I have to be sure to update the other. If I have to add a dialog, for example, then it is not a simple matter to make everything match between the two. Any suggestions? Using .Net Jack
Hi Jack, this is interesting problem. Two versions of same app is usually handled by
#ifdefand things like that. Anyway, it doesn't help with open source. It could be good idea to make a tool which will remove "pro" code. I wish I had time... I think it can be useful tool. Is anything like that already done? Try google... best regards, David 'DNH' Nohejl Never forget: "Stay kul and happy" (I.A.) -
Hi Jack, this is interesting problem. Two versions of same app is usually handled by
#ifdefand things like that. Anyway, it doesn't help with open source. It could be good idea to make a tool which will remove "pro" code. I wish I had time... I think it can be useful tool. Is anything like that already done? Try google... best regards, David 'DNH' Nohejl Never forget: "Stay kul and happy" (I.A.)I think it may be already set up to be done with .Net but I can't figure it out. I usually just add a project and go at it. This is the first time I needed something more involved. I set up a test project and added two different projects to it (the solution they call it). That would at least make copying from one file to another easier. But when I tried it on my main project, it won't let me do it since they have the same internal names. Supposedly, you can just click on Rename to have .Net rename the project but that didn't work. Although it wouldn't surprise me to find I am doing it wrong. If anyone knows how to rename a project with .Net I would appreciate the help. Jack
-
I'm creating two version of a program: A free version (myprogram) and an enhanced version (myprogram_PRO). The source code has to be released with the free version since it will be open source. Is there some way to have both programs in the same project? I can create two projects but if I make a change to one version then I have to be sure to update the other. If I have to add a dialog, for example, then it is not a simple matter to make everything match between the two. Any suggestions? Using .Net Jack
I think something can be accomplished with a good source control system. They have a feature called Branching, so that you can keep the separate source for two versions of your project. Say you have version 1.0 final, and then you start working on 2.0. If you find a big bug in 1.0, you fix it and release 1.0a. So you create a branch for updating 1.x code, while working on 2.0 (both based on 1.0) and you can merge branches, so 1.x modifications are merged into 2.0 code. Well, it's something like that. -- LuisR
Luis Alonso Ramos Intelectix - Chihuahua, Mexico Not much here: My CP Blog!
-
Hi Jack, this is interesting problem. Two versions of same app is usually handled by
#ifdefand things like that. Anyway, it doesn't help with open source. It could be good idea to make a tool which will remove "pro" code. I wish I had time... I think it can be useful tool. Is anything like that already done? Try google... best regards, David 'DNH' Nohejl Never forget: "Stay kul and happy" (I.A.) -
I'm creating two version of a program: A free version (myprogram) and an enhanced version (myprogram_PRO). The source code has to be released with the free version since it will be open source. Is there some way to have both programs in the same project? I can create two projects but if I make a change to one version then I have to be sure to update the other. If I have to add a dialog, for example, then it is not a simple matter to make everything match between the two. Any suggestions? Using .Net Jack
You could have all your Pro functionality contained in a dll that acts as a plugin to the free version -- Help me! I'm turning into a grapefruit! Phoenix Paint - back from DPaint's ashes!
-
:confused: Never forget: "Stay kul and happy" (I.A.)
-
You could have all your Pro functionality contained in a dll that acts as a plugin to the free version -- Help me! I'm turning into a grapefruit! Phoenix Paint - back from DPaint's ashes!
-
I'm creating two version of a program: A free version (myprogram) and an enhanced version (myprogram_PRO). The source code has to be released with the free version since it will be open source. Is there some way to have both programs in the same project? I can create two projects but if I make a change to one version then I have to be sure to update the other. If I have to add a dialog, for example, then it is not a simple matter to make everything match between the two. Any suggestions? Using .Net Jack
You may have bigger problems depending on the licence you use. For example if you licence the free version using the GNU licence [^]then you also have to distribute your PRO version under the GNU licence and provide the full source code as it is using code from your free version. If you use the BSD licence [^]you can just make sure you include the same copyright info in both versions.
-
You may have bigger problems depending on the licence you use. For example if you licence the free version using the GNU licence [^]then you also have to distribute your PRO version under the GNU licence and provide the full source code as it is using code from your free version. If you use the BSD licence [^]you can just make sure you include the same copyright info in both versions.
Hmm, Thanks for mentioning this - I wasn't aware of it. I'm not sure if the BSD license is acceptable by the place I am submitting it to. In the event it is not, is it OK to have the free version, say "MyProgram," and then a non-free version but call it "My Other Program." And then mention in the description for My Other Program that it does everything My Program does and more. How do others get around this? I see free and non-free versions all of the time on various web sites. Jack
-
Hmm, Thanks for mentioning this - I wasn't aware of it. I'm not sure if the BSD license is acceptable by the place I am submitting it to. In the event it is not, is it OK to have the free version, say "MyProgram," and then a non-free version but call it "My Other Program." And then mention in the description for My Other Program that it does everything My Program does and more. How do others get around this? I see free and non-free versions all of the time on various web sites. Jack
It was something I came across with the GNU license, which many people use for open source development. Where I work we had our own license drawn up by experts which covers our particular oddities. Writing your own license does solve the problem as you can say whatever you want. I have come across a number of forum posts recently that advocate the BSD license over the GNU license. For my own free stuff I just put in a "use this at your own risk" disclaimer. That way I can use it at my own risk in a non-free version and license that completely differently. The issue is more to do with making your source code available, or not, than anything else. If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850)