Steema Central

Hi,
We have purchased a new version of TeeChart and we are working with it in C#.
We have DLL (in C#) that uses TChart.
Also a application that refers the above DLL for display of graph.
Now we have built both these projects, DLL and exe on my machine which has licensed version of TChart.
Now I copy the my exe, dll and tchart dll to our target machine.

We tried running our exe and it results in null reference exception being thrown. The exe works fine on my machine that has tchart licensed version.

This is very critical issue for us and we need a solution for this problem ASAP.

Please help us out.

Thanks

Hi Lakshmi,

You should read "Tutorial 17 - Designtime, Runtime and License Requirements". You'll find the tutorials at TeeChart's program group.

There is also a licensing aspect that came to light that we weren't aware of in time for the documentation and that may help to know.

The issue relates to applications that compile TeeChart into a DLL that is then used in turn by a different application. Please note the comments from a TeeChart Developer who ran through runtime licensing steps:

"...
It was not enough to provide
the .licx entry in building the DLL that instantiates and uses TeeChart -
no! In fact, even though the main project (the EXE module) did not
reference TeeChart, apparently it was necessary to add the TeeChart
licensing entry to this project's own .licx file
..."

Please check that the point might not apply in your case. If that's not relevant or of help and the test below doesn't help either, please let us know what type of application TeeChart is being built into along with any other information you might feel is of use and we'll look for other causes of the problem.

Another test (assuming your application doesn't fall into the dll type described above), would be to recompile the TeeChart demo (assuming you ran the precompiled exe?) on your development machine and then test that on the runtime machine. That would confirm that the designtime license is correctly in place on your development machine and able to correctly 'compile-in' the license.

Please let us know if the above doesn't help resolve the issue.