Current License implementation
Current License implementation
In version 3 will you be implementing licensing as is implemented in version 2? TChart is the only 3rd party product I have that requires an entry in the top level application. We need to create a plugin that uses TChart. The main application is created by another group within the company. They have an issue with having to add the license at the framework level before they build.
-
jchriswaters
- Newbie
- Posts: 1
- Joined: Mon Sep 18, 2006 12:00 am
We are critically near the end of a large project facing this same issue. We have developed DLL's that are "housed" within one of our parent companys "rich client containers" - we have no control of that application's executable and are thus unable to impose on them the licensing requirement seemingly required by Steema to enable our distribution of a DLL with a TeeChart.
Is there way to distribute a DLL containing a run time licensed version of the TeeChart control within an application where we are unable to force the addition of the license file to the "parent" exe?
Is there way to distribute a DLL containing a run time licensed version of the TeeChart control within an application where we are unable to force the addition of the license file to the "parent" exe?
Last edited by jchriswaters on Fri Nov 03, 2006 9:20 am, edited 1 time in total.
Current License implementation
This issue caused great concern at a demo I did last week with the other groups within our company. I was asked at that time if we could remove TeeChart and go with another charting object. As I said previously I have no other 3rd party controls that require this so am trying to understand why Steema has taken this approach and if this is something that will be corrected in version 3. We are only in the prototype stages and do not plan on releasing our plugins for another 6 months and would be going out with the newest version.
Current License implementation
Have not heard from anyone from Steema. I need to know if the Licensing for version 3 will change. This is an important issue to us and I am sure to other groups in large companies that use the control to develop corporate application plugins.
Thanks
Thanks
Hello,
TeeChart's licensing approach uses the standard Microsoft Licensing framework. It was incorporated to TeeChart in response to requests from some TeeChart customers, to prevent unauthorised designtime use of TeeChart in environments where the TeeChart dll is delivered as part of a runtime solution.
Steema does not require that a license be purchased for a machine in a groupwork environment where no development is made with TeeChart, ie. where a compilation is made of an end-level application that uses a TeeChart module, developed by someone else in the development team who is licensed to use TeeChart. For that reason Steema provide the TeeRegister.exe utility, downloadable from the customer download page, to permit installation of the designtime license in such an 'end-of-workflow' machine. To successfully bind the license in, the top-level assembly project should include the TeeChart license line in its Licenses.licx file (see Tutorial 17).
Under certain circumstances, if a groupwork scenario is unable to work within the flexibility of the model outlined above then Steema can make a TeeChart assembly available with no physical license requirement for compilation. Steema would require a request sent to sales@steema.com describing requirement and reason for which the standard licensing model cannot apply. We would like to remind customers that TeeChart's use in a DLL, where TeeChart's API is made accessible either directly or indirectly for ondevelopment requires a Developer License at its place of use. If access to the TeeChart API in that DLL is closed then no designtime license is required to use that DLL.
We expect the same licensing model to apply to TeeChart for .NET version 3.
Regards,
Marc Meumann
TeeChart's licensing approach uses the standard Microsoft Licensing framework. It was incorporated to TeeChart in response to requests from some TeeChart customers, to prevent unauthorised designtime use of TeeChart in environments where the TeeChart dll is delivered as part of a runtime solution.
Steema does not require that a license be purchased for a machine in a groupwork environment where no development is made with TeeChart, ie. where a compilation is made of an end-level application that uses a TeeChart module, developed by someone else in the development team who is licensed to use TeeChart. For that reason Steema provide the TeeRegister.exe utility, downloadable from the customer download page, to permit installation of the designtime license in such an 'end-of-workflow' machine. To successfully bind the license in, the top-level assembly project should include the TeeChart license line in its Licenses.licx file (see Tutorial 17).
Under certain circumstances, if a groupwork scenario is unable to work within the flexibility of the model outlined above then Steema can make a TeeChart assembly available with no physical license requirement for compilation. Steema would require a request sent to sales@steema.com describing requirement and reason for which the standard licensing model cannot apply. We would like to remind customers that TeeChart's use in a DLL, where TeeChart's API is made accessible either directly or indirectly for ondevelopment requires a Developer License at its place of use. If access to the TeeChart API in that DLL is closed then no designtime license is required to use that DLL.
We expect the same licensing model to apply to TeeChart for .NET version 3.
Regards,
Marc Meumann
Steema Support