Migrating from GrapeCity.ActiveReports v17 to MESCIUS.ActiveReports v20

Migrating from GrapeCity.ActiveReports v17 to MESCIUS.ActiveReports v20

Posted by: julien.iseli on 28 September 2026, 3:32 am EST

• 

  julien.iseli

  • Post Options:
  • Link
    Copy

  Posted 28 September 2026, 3:32 am EST

  We are currently migrating from GrapeCity.ActiveReports v17.3.0 to MESCIUS.ActiveReports v20.1.4 and are encountering numerous compilation errors related to renamed or missing namespaces and types.

  We have reviewed the migration documentation available to us, but it does not appear to cover many of the issues we are facing. As a result, we’re struggling to identify the required code changes to complete the migration.

  Is there a migration guide, breaking change documentation, or any additional resources that could help us migrate from v17 to v20? Any assistance would be greatly appreciated.

  The type or namespace name 'Services' does not exist in the namespace 'GrapeCity.ActiveReports.Aspnetcore.Designer' (are you missing an assembly reference?)
  The type or namespace name 'IDataSetsService' could not be found (are you missing a using directive or an assembly reference?)
  The type or namespace name 'DataSetTemplate' could not be found (are you missing a using directive or an assembly reference?)
  The type or namespace name 'IImageInfo' could not be found (are you missing a using directive or an assembly reference?)
  The type or namespace name 'IReportInfo' could not be found (are you missing a using directive or an assembly reference?)
  The type or namespace name 'Theme' could not be found (are you missing a using directive or an assembly reference?)
  The type or namespace name 'IThemeInfo' could not be found (are you missing a using directive or an assembly reference?)

  https://developer.mescius.com/activereportsnet/docs/v19.1/developers/breaking-changes

• 

  anand.sinha

  

  • Post Options:
  • Link
    Copy

  Posted 28 September 2026, 6:51 am EST

  Hi Julien,

  Yes, the namespace references for ActiveReports have been migrated from ‘GrapeCity.ActiveReports.’ to 'MESCIUS.ActiveReports.’. Please refer to the following breaking changes (from v18 to v20) to learn more about this:

  • Breaking changes from ActiveReports 17 to ActiveReports 18
  • Breaking changes from ActiveReports 18 to ActiveReports 19
  • Breaking changes from ActiveReports 19 to ActiveReports 20

  For the latest ActiveReports 20 samples, please refer to Web Samples.

  If the issue persists, please try sharing a minimal replicable sample so we can replicate the issue on our end and further investigate the same.

  Regards,
  
  Anand

• 

  julien.iseli

  • Post Options:
  • Link
    Copy

  Posted 29 September 2026, 2:07 am EST - Updated 29 September 2026, 2:12 am EST

  Thanks for your feedback. Actually, the namespaces still reference GrapeCity.ActiveReports.. Only the NuGet package names have changed to MESCIUS.ActiveReports..

  The breaking changes documentation appears to be incomplete, as it does not mention the removal of the IDataSetsService interface, DataSetTemplateInfo, or several other types that also seem to be missing (see the attached screenshots).

  As a result, we’re having difficulty determining the intended migration path for these APIs and whether direct replacements exist in the newer versions.

  

  818×412 40.4 KB

  
  
  

  

  1798×487 59.1 KB

• 

  anand.sinha

  

  • Post Options:
  • Link
    Copy

  Posted 29 September 2026, 4:52 am EST

  Hi Julien,

  With ActiveReports v20, you no longer need the IDataSetsService, instead you can just place all the resources ‘datasets’, ‘templates’ within the ‘resources’ folder, and in ‘UseReportDesigner.UseFileStore’ you can set the FileStoreOptions to ‘NestedFoldersLookup’ like:

  app.UseReportDesigner(config =>
  {
      config.UseFileStore(ResourcesRootDirectory, null, FileStoreOptions.NestedFoldersLookup);
      config.UseConfig(Path.Combine(app.Environment.ContentRootPath, "ActiveReports.config"));
  });
  

  Please find our v20 WebDesigner sample that implements the same for reference.

  However, if your issue persists, please try sharing a minimal runnable sample that replicates the issue so we can test the same on our end and further investigate the issue.

  Thanks,
  
  Anand