License lost every time a new version of control is released

License lost every time a new version of control is released

Posted by: Ranba790 on 21 April 2018, 5:13 pm EST

• 

  Ranba790

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 21 April 2018, 5:13 pm EST

  Hi
  
  This issue exist from day one, i have been using component one for winform for about 10 years. every time you release a new version some of the component entry in the licenses.licx disappear and you need to add each control back to the form and rebuild.
  
  We have a lot of project with different winform controls and this is very annoying to redo every time, Also the eval screen doesn’t popup till you load the form so we already released software where the customer get the evaluation license screen.
  
  I think its about time you fix it .

• 

  gkayne

  • Post Options:
  • Link
    Copy

  Posted 22 April 2018, 4:44 am EST

  For the last release I ran the C1LicenseActivation utility (C:\Program Files (x86)\Common Files\ComponentOne Shared\C1LicenseActivation.exe) and all controls were updated.

• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 23 April 2018, 2:50 am EST

  Hello,

  If you have updated through C1Live and used the ProjectUpdater utility to update the projects, they will automatically be updated for the current version.
  
  In case this does not work for you, please use the LicxGenerator utility that does the job of updating the licx file entries. You can learn more about the same from the below mentioned blog:
  
  https://www.grapecity.com/en/blogs/licensing-and-licenses-licx-file-licxgenerator-tool
  
  Let us know if you face any issues while doing the same.

  Best Regards,
  
  Esha

• 

  Ranba790

  • Post Options:
  • Link
    Copy

  Posted 29 April 2018, 11:56 pm EST - Updated 3 October 2022, 11:13 pm EST

  Hi
  
  I tried running the licx generator but i don’t get any file generated
  
  

  

  982×513 7.04 KB

  Can you tell me what am i doing wrong
  
  Thanks

• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 30 April 2018, 3:45 pm EST - Updated 3 October 2022, 11:13 pm EST

  Hello,

  Is the folder selection dialog shown when you run the utility?
  
  If not, please specify the sourcePath related to the application for which you wish to generate the licenses.licx file. Further, avoid adding backslash([b][/b]) at the end of the path for source and output both (see the attached screenshot). Now, the licenses.licx file should be generated.

  Let us know if the file is still not generated for you.

  Best Regards,
  
  Esha
  
  

  

  1033×249 14.6 KB

• 

  Ranba790

  • Post Options:
  • Link
    Copy

  Posted 9 May 2018, 6:50 pm EST

  I got it to work by generating a license file for all the C1 component and then figure out which ones i need for my project in order to copy it to the my project license file.
  
  But the main problem remains, i can’t do it every 3 month when you come out with a new version. i have 100s of projects with lots of forms, it is very time consuming and frustrating specially when i missed a component and my customer finds it
  
  Please Fix this issue

• 

  meenakshi.singh

  

  • Post Options:
  • Link
    Copy

  Posted 10 May 2018, 5:00 pm EST

  Hi Ran!

  I understand your situation regarding this behaviour. However, there are only these utilities - ProjectUpdater and LicxGenerator, as mentioned earlier.

  Apart from this, you can do one thing - set Specific Version property of all the C1 assemblies in References to false. And, you must have noticed entries in licenses.licx file, like this :
  
  C1.Win.C1FlexGrid.C1FlexGrid, C1.Win.C1FlexGrid.4, Version=4.0.20181.296, Culture=neutral, PublicKeyToken=79882d576c6336da

  You need to remove Version, Culture and PublicKeyToken information for each control in this file. It should look like this :
  
  C1.Win.C1FlexGrid.C1FlexGrid, C1.Win.C1FlexGrid.4

  Now, when you upgrade C1 on your machine then you simply need to rebuild the solution. No licensing issue should occur.

  Best regards,
  
  Meenakshi

• 

  Ranba790

  • Post Options:
  • Link
    Copy

  Posted 23 July 2018, 10:23 pm EST

  New Version and this issue is poping up again. you must do something about it.

• 

  Ranba790

  • Post Options:
  • Link
    Copy

  Posted 23 July 2018, 10:23 pm EST

  New Version and this issue is poping up again. you must do something about it.

• 

  Ruchir.Agarwal

  

  • Post Options:
  • Link
    Copy

  Posted 24 July 2018, 11:14 pm EST

  Hi,

  First of all, I really regret the inconvenience you have to face due to this issue.

  Coming to the concern, the behavior that the license screen pops up for all your projects every time you update ComponentOne is very strange. We have never come across any such issue nor any of our customers reported about this everytime they update.
  
  For any nag/evaluation screen issue, following are the check-ups that once ensured resolves the issue forever:

  1. Ensuring that the entries for all ComponentOne controls are present in licenceslicx file for all the projects present in your solution/application.
  2. Removing version & token information from the license entries.
  3. Setting the SpecficVersion of all ComponentOne dlls to False.
  4. You update ComponentOne using C1Live, installed at ‘C:\Program Files (x86)\ComponentOne\C1Live’
  5. You keep Visual Studio closed while updating.
  6. You are not adding references to your project by any location other than the default ‘C:\Program Files (x86)\ComponentOne\WinForms Edition\bin’
     
     However, since you are still facing the issue even after ensuring the above checks, would it be possible for you to share any of your applications, so that we can check what’s it’s structure and try to find the cause.
     
     Thank you for your cooperation.

  Regards,
  
  Ruchir