Evaluation Nag Screen

Evaluation Nag Screen

Posted by: bdwest on 10 September 2017, 11:27 am EST

• 

  bdwest

  • Post Options:
  • Link
    Copy

  Posted 10 September 2017, 11:27 am EST

  I am using web reports for ASP.net. The nag (evaulation screen) keeps coming up for Reports for .net. This is not the WEB REPORTS nag screen but the REPORTS nag screen. I have hit the activate button many times. It shows the license information and the serial number is correct but it refuses to show the component as activated.

  I even tried manually copying this into the license file

  C1.C1Report.C1Report, C1.C1Report.2, Version=2.6.20092.52106, Culture=neutral, PublicKeyToken=594a0605db190bb9

  am using verions 2.6.20092.52106

  This is one the things I truly hate about C1 products is the constants quirks and troubles with the nag screens - patricularly after updates. Once they reappear I normally can just drag the componet onto a new form or page and rebuild. The problem with this is that you can not drag the reports for .net onto an asp.net page because it is a winforms component. I keep hoping C1 will get this fixed. We only have this problem with C1 componets. Components from other vendors give us no licensing problems. In case you can't tell I am little peeved at the moment but after being a C1 customers since the early days of .Net (7 or 8 years?), I feel like venting.

  What do I need to do?

  Brian

• 

  c1_suelindaw

  • Post Options:
  • Link
    Copy

  Posted 10 September 2017, 11:27 am EST

  Hello Brian,

  Visual Studio does not always update the licenses.licx of your project when you update your controls to a new build. However, you can remove the version specific information from the licenses.licx file.

  For example, your .licx entry:

  C1.C1Report.C1Report, C1.C1Report.2, Version=2.6.20092.52106, Culture=neutral, PublicKeyToken=594a0605db190bb9

  Would become:

  C1.C1Report.C1Report, C1.C1Report.2

  However, there was an issue with build 52106 where you may also need to reference the C1PrintDocument in the licenses.licx file manually. So, you should add this additional line to your .licx file:

  C1.C1Preview.C1PrintDocument, C1.C1Report.2

  If you use both lines, without the version information, that should fix your nag screen problem.

  For your issue with not being able to drag winforms components onto a web page, VS2005 and VS2008 does not let you drag winforms components directly onto the webpage like you could with VS20022003. You have to open your .aspx page or the .aspx.vb.aspx.cs page, then go to View | Component Designer in the Visual Studio menu. You can then drag and drop ASP.NET compatible winforms components onto the Component Designer.

  Suelinda Webster
  
  Customer Engagement
  
  ComponentOne, LLC
  
  

• 

  bdwest

  • Post Options:
  • Link
    Copy

  Posted 10 September 2017, 11:27 am EST

  Suelinda,

  Here are the C1 references now in the license file. The nag screen for " Reports for .NET" still appears. I have rebuilt the entire solution.

  C1.Web.C1WebReport.C1WebReport, C1.Web.C1WebReport.2

  C1.C1Report.C1Report, C1.C1Report.2

  C1.C1Preview.C1PrintDocument, C1.C1Report.2

  I also tried dragging the C1Report1 from the tool box to the component designer of an asp.net page as you describe. It does work but the nag screen still appears.

  I truly do appreciate your response but we have been spent untold hours over the years dealing with this very issue on .net and asp.net components. I expect we spend as much in deloper time dealing with the nag screens as we spend in licenses to C1 annually. This is close to driving us to other solutions. Do you have any other suggestions?

  Brian

• 

  soapware

  • Post Options:
  • Link
    Copy

  Posted 10 September 2017, 11:27 am EST

  I have to agree, it seems that every 4 months or so we are dealing with these extremely frustrating licensing issues. Here I am now with deadline in a week and for no reason, these screens start popping up again. This is unacceptable, period. I don't care what license scheme Microsoft or Visual Studio suggests that you use. I don't have this problem with other controls so either you guys aren't understanding what they are doing or all the other controls have gone a different direction. Either way, I will be going a different direction asap because this is just flat out unacceptable.

• 

  karl

  • Post Options:
  • Link
    Copy

  Posted 4 June 2020, 10:24 am EST

  Soapware, I’m with you…

  Here it is, June of 2020 and I’m still having license issues. ComponentOne, get your act together. This is rediculous.

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 5 June 2020, 12:15 am EST

  Hi Karl,
  
  We are sorry for the inconvenience for the issue. Could you please make sure that you have remove all version-specific entries from the licenses.licx and web.config files.
  
  Also, the dll’s specific version is not set to true.

  Please make sure the above and let us know if the issue persists. It would be great if you may share the demo application depicting your issue so that we may investigate it at our end.

  Regards,
  
  Manish Gupta