C1TrueDBGrid C# [int, string] indexer broken?

C1TrueDBGrid C# [int, string] indexer broken?

Posted by: jhuang on 19 June 2018, 3:24 pm EST

• 

  jhuang

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 19 June 2018, 3:24 pm EST

  Hi, we recently upgraded to 4.0.20181.296 and it seems the behavior for the indexer has changed.

  When the grid is in the GroupBy view and we use the grid[rowInt, columnStr] to access the data, if the rowInt is greater than the visible row count, the call will error out.

  Prior to upgrading, the rowInt could be up the the count of grid.Rows

  Please advise, thanks.

• 

  Pragati.Kaushik

  

  • Post Options:
  • Link
    Copy

  Posted 20 June 2018, 12:58 am EST - Updated 4 October 2022, 2:31 am EST

  Hi,

  This issue has been fixed in the latest hotfix release 4.0.20181.307. Please refer the attached screentshot demonstrating the same in the change log

  Please update your controls to the latest release using C1Live. You can find out how to use C1Live to update your controls from this link:
  
  https://www.grapecity.com/en/support/c1live

  Thanks,
  
  Pragati
  
  

  

  823×184 9.29 KB

• 

  jhuang

  • Post Options:
  • Link
    Copy

  Posted 20 June 2018, 10:01 am EST - Updated 4 October 2022, 2:31 am EST

  Hi, thanks for pointing out the hotfix.
  
  I updated via C1Live, and the fix is working.
  
  However, now I am getting the “Evaluation version.” nag screens.
  
  My subscription license is good through August 2018, and presumably should cover the release of this hotfix.

  I tried re-activating the ComponentOne license on my PC.
  
  I also checked each control using the “About” screen in the designer, and they show the control is registered to me.

  please advise, thanks!

  

• 

  Pragati.Kaushik

  

  • Post Options:
  • Link
    Copy

  Posted 21 June 2018, 12:18 am EST

  Hi Jason,

  There are 2 elements of our licensing model, the activation of a serial key on your dev machine and the indivdiually licensing the controls in your project.

  The first is accomplished by using the C1LicenseActivation utility (Start > All Apps > ComponentOne > C1LicenseActivation). If you launch the utility and click the ? at the end of the serial number box, you can see what keys are installed. If the box is blank, there are no keys activated.

  The second is the individual licensing of the controls in the solution. For Winforms, this is accomplished via a text file called licenses.licx that’s included in your project. It will contain a line items for each control and this is how your project creates run-time licenses for our controls when you deploy your solution. Check to see if your project contains this file and verify all the controls are listed.
  
  If one or both of these items are not complete, your application will nag.

  In this particular case, please add the following entry in the licenses.licx file of the project, save and rebuild the solution:

  C1.Win.C1TrueDBGrid.C1TrueDBGrid, C1.Win.C1TrueDBGrid.4
  

  The problem should no longer occur.

  Thanks,
  
  Pragati

• 

  jhuang

  • Post Options:
  • Link
    Copy

  Posted 21 June 2018, 8:51 am EST

  Thanks.
  
  I checked the CV1LicenseActivation utility which shows I have the Studio Ultimate license installed
  
  and i have all the C1.Win.xxx.xxx components in my licenses.licx file for my project/solution including ```
  
  C1.Win.C1TrueDBGrid.C1TrueDBGrid, C1.Win.C1TrueDBGrid.4

  I did not have the nags prior to installing the hotfix updates via C1Live.

• 

  jhuang

  • Post Options:
  • Link
    Copy

  Posted 21 June 2018, 8:57 am EST

  Ok, I am good now.
  
  I ended up deleting all the C1 entries in licenses.licx and used the Grape City License Manager to rebuild the entries using the ‘Update Project(s)’ command.
  
  Thanks!