Unable to resolve type 'GrapeCity.ActiveReports.Viewer.Win.Viewer

Unable to resolve type 'GrapeCity.ActiveReports.Viewer.Win.Viewer

Posted by: paul.kahl on 8 August 2022, 8:01 am EST

• 

  paul.kahl

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 8 August 2022, 8:01 am EST

  I’m working on the upgrade from v15 to v16 of ActiveReports. I’ve used the Convert to Active Reports 16 tool in Visual Studio, and performed a few dozen builds fixing various issues. The latest issue, I can’t seem to resolve. The error I get is: Error LC0003: Unable to resolve type 'GrapeCity.ActiveReports.Viewer.Win.Viewer, GrapeCity.ActiveReports.Viewer.Win, Version=16.1.3.0…’

  I did the Googling, and followed GrapeCity’s instructions to just “Install the NuGet package for ‘GrapeCity.ActiveReports.Viewer.Win’”, but that didn’t resolve the issue, as ‘GrapeCity.ActiveReports.Viewer.Win.Viewer’ still cannot be found.

• 

  paul.kahl

  • Post Options:
  • Link
    Copy

  Posted 8 August 2022, 8:28 am EST

  Referencing both GrapeCity.ActiveReports.Viewer.Win and GrapeCity.ActiveReports.Viewer.Common fixes the issue, but the GC KB article doesn’t reference that solution.

• 

  dushyant.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 8 August 2022, 10:32 pm EST

  Hello,

  The above error generally arises when there is an entry of the given assembly in the licenses.licx file but that assembly is missing from the project. To resolve the issue, please add references to the assembly/dll mentioned in the error message in the project and rebuild the solution or if you are not using the assembly, simply remove the entry from the license.licx file.

  If the issue still persists, it might due to the difference in the version of the Assembly reference used in the project and the one specified in the license.licx file. Thus, we would recommend removing the Version, Culture, and PublicKeyToken information from the licensing.licx file and then try rebuilding your project.

  For more information on the same, please refer to the below link:

  However, If it is still not resolved, please provide a stripped-down sample application depicting the issue or if that’s not possible, provide a screenshot of the project references along with all the entries in the licenses.licx file so that we may investigate and reply accordingly.

  Regards Dushyant Sharma