Licensing issues
Posted: Thu Feb 02, 2006 3:48 pm
When reading the tutorial 17 on licensing it seems clear to me that the steema chart component has to be installed on the machine where you build your application, is that correct?
I get that impression from the fact that you need to have a registry key set for the license to be able to compile into the DLL (I am not entirely sure how this licensing stuff works).
Here comes the problem / issue we have with this.
We have just branched the project in one release, let's call it 1.1 and we continue in parallell with the main "stream" of the project.
This means that on the build server we might want to build either version at any given time, with bug fixes and new added features, whatever might show up.
In this case, say v 1.1 uses v2.0.1 of TeeChart.
The main stream continues and uses a newer version of TeeChart - v2.0.5 or whatever.
To properly build these without having to manually install / deinstall the correct version every time we just want to have the .DLL in a certain folder of the build server. This means that building v1.1 looks in the folder for v2.0.1 for TeeChart, the main stream looks in the folder for v2.0.5.
If we install the component on the build server the build process will always get the DLL it finds in the GAC (or wherever it is stored) since it looks there first. This means that if I fix a bug in v1.1 it will build with the wrong version of TeeChart - a newer one.
Or the other way around, if I install the older one, the main stream won't compile since the older version doesn't have all the same methods and properties as the newer version.
This works fine with all the rest of our third-party components.
Any ideas on how to handle this somehow?
Cheers,
Tommie
I get that impression from the fact that you need to have a registry key set for the license to be able to compile into the DLL (I am not entirely sure how this licensing stuff works).
Here comes the problem / issue we have with this.
We have just branched the project in one release, let's call it 1.1 and we continue in parallell with the main "stream" of the project.
This means that on the build server we might want to build either version at any given time, with bug fixes and new added features, whatever might show up.
In this case, say v 1.1 uses v2.0.1 of TeeChart.
The main stream continues and uses a newer version of TeeChart - v2.0.5 or whatever.
To properly build these without having to manually install / deinstall the correct version every time we just want to have the .DLL in a certain folder of the build server. This means that building v1.1 looks in the folder for v2.0.1 for TeeChart, the main stream looks in the folder for v2.0.5.
If we install the component on the build server the build process will always get the DLL it finds in the GAC (or wherever it is stored) since it looks there first. This means that if I fix a bug in v1.1 it will build with the wrong version of TeeChart - a newer one.
Or the other way around, if I install the older one, the main stream won't compile since the older version doesn't have all the same methods and properties as the newer version.
This works fine with all the rest of our third-party components.
Any ideas on how to handle this somehow?
Cheers,
Tommie