GrapeCity.ActiveReports.Viewer.Win.dll dependencies

GrapeCity.ActiveReports.Viewer.Win.dll dependencies

Posted by: info on 10 October 2022, 6:59 am EST

• 

  info

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 10 October 2022, 6:59 am EST

  Getting a ‘Could not load file or one of its dependencies’ error for GrapeCity.ActiveReports.Viewer.Win.dll when attemping to bring up viewer from Windows form. What are the dependencies for GrapeCity.ActiveReports.Viewer.Win.dll?? Works in VB.net environment but of course dozens of GrapeCity files are loaded there.

• 

  akshay.rajput

  

  • Post Options:
  • Link
    Copy

  Posted 10 October 2022, 6:33 pm EST

  Hi,

  Please make sure to have the following packages added to your project from the NuGet Package Manager.

  • GrapeCity.ActiveReports.Viewer.Common (https://www.nuget.org/packages/GrapeCity.ActiveReports.Viewer.Common)

  • GrapeCity.ActiveReports.Viewer.Win (https://www.nuget.org/packages/GrapeCity.ActiveReports.Viewer.Win)

  The packages version must match the one you have installed for GrapeCity.ActiveReports. Set the preference Copy Local = True from Visual Studio for all the packages.

  After this make sure you have the package listed in the packages.config file with the correct version of the packages. This file is usually situated at the project location(.csproj or .vbproj file).

  If the above solution doesn’t work for you. You may simply add a new ActiveReports 15 Code Based Section Report in your project and this will automatically add the required packages for it in your WinForms application.

  Once all this is done please delete the bin and obj folder from the project location and the packages folder from the solution’s location(.sln file). And, then Clean and Rebuild the Solution.

  As “Could not load file or one of its dependencies” is a generic error you can also refer to other forum posts on GrapeCity Forum or from other third party forums like StackOverFlow which are already resolved.

  I hope the above solution resolves your issue.
  
  If the issue still persists please share the list of all the references in your applications and also the packages.config file.

  Also please share a stripped down sample of your application replicating this issue so we can reproduce this behavior at our end and investigate further on this.