Steema Central

We use the TeeChart under MS VS .NET 2005
The licenses.licx contains the proper keys and this file is compiled as an embedded ressource into the EXE file.
EXE is running properly on different system (with or without the developer licence installed) except the following case:

If I rename the EXE, the application throws an "can get no licence error" on sytems where the developer licence is not installed.

Any ideas to fix that?

Background: Our customer needs to rename the EXE depending on different end customers without a new compilation ...

Hello,

I can't see an easy solution for this. Whilst Microsoft do offer lc.exe (http://msdn.microsoft.com/en-us/library/ha0k3c9f.aspx) that allows a license file to be prepared for any executable name, that license cannot, as far as I can see, be embedded into the exe without recompiling it. If anyone knows otherwise it would be useful to hear it ...

An option might be to create aliases (shortcuts) to the file. You can use any name you like for the alias and have it point to the original executable.

I hope that might be of use.
Regards,
Marc Meumann

The problem is, that only the TeeChart component is affected.

I have other licenced components in the same app witout any problems (after renaming the EXE):

Steema.TeeChart.TChart, TeeChart, Version=4.0.2009.21354, Culture=neutral, PublicKeyToken=9c8126276c77bdb7
DevExpress.XtraEditors.CheckEdit, DevExpress.XtraEditors.v8.1, Version=8.1.4.0, Culture=neutral, PublicKeyToken=9b171c9fd64da1d1
DevExpress.XtraEditors.ComboBoxEdit, DevExpress.XtraEditors.v8.1, Version=8.1.4.0, Culture=neutral, PublicKeyToken=9b171c9fd64da1d1

Hello,

One of the goals of Microsoft's license control is to protect against renaming of executables; I'm not sure what license protection the DevExpress components are offering. TeeChart is available in an unlocked form with no protection, you can request access to it from sales @ steema.com, please note though that 'no protection' means that the TeeChart control is then be susceptible to use without license authorisation in a development environment.

Regards,
Marc

Hello,

As a followup ... We'll review the default license way of working for future updates to see whether we can offer a more flexible license-check technique whilst continuing to give protection against improper designtime use.

Regards,
Marc

Hello,

We've implemented some changes to the licensing model, to be included in the next maintenance release, that lighten the control at runtime to permit the renaming of executables.

Regards,
Marc

That sounds good - thanks for the fast solution...