25.12 Aspose.Drawing Problems

GroupDocs.Conversion Product Family
1

Updating to version 25.12 looks to have removed the dependency on Aspose.Drawing and Aspose.Drawing.Common - causing failures when converting image and visio file types.

GroupDocs.Conversion.Exceptions.GroupDocsConversionException: Could not load file or assembly ‘Aspose.Drawing, Culture=neutral, PublicKeyToken=null’.

I could add these manually, but 25.10 and 25.11 include them as dependencies. Were they removed for a reason or is this a mistake?

2

@rthomas95

Why the exception appears

You reported that after updating to GroupDocs.Conversion 25.12 the SDK throws

GroupDocsConversionException: Could not load file or assembly 'Aspose.Drawing…'

This is the same “cannot resolve reference: Aspose.Drawing” error that other users have posted about when the Aspose.Drawing assembly is missing from the application output [1]. A similar FileNotFoundException has also been observed for other Aspose libraries (e.g., Aspose.PSD) when the required assembly is not present [3].

Earlier releases of GroupDocs.Conversion (for example 25.4) depended on System.Drawing.Common instead of Aspose.Drawing [2]; the newer 25.12 build therefore expects the Aspose.Drawing assembly at runtime.

How to resolve it

  1. Add the missing Aspose.Drawing package

    dotnet add package Aspose.Drawing

    or add the package via Visual Studio’s Manage NuGet Packages dialog.

  2. Ensure the assembly is copied to the output folder
    Verify that the reference’s Copy Local (or equivalent) property is set so that Aspose.Drawing.dll appears next to your executable after the build.

  3. Re‑build and run – the conversion of image formats (PNG, JPG, BMP, TIFF) and Visio files (.vsdx) should succeed.

  4. If you encounter a similar “Aspose.Drawing.Common” error (a hypothesis based on other Aspose dependencies), you may also need to add the Aspose.Drawing.Common package.

If adding the package is not possible

  • Revert to a previous GroupDocs.Conversion version (e.g., 25.4) that still uses System.Drawing.Common [2].
  • Open a support thread with the full stack trace; the issue is most likely a missing runtime dependency rather than a bug in the SDK.

Summary

The GroupDocs.Conversion 25.12 update requires the Aspose.Drawing assembly for image and Visio conversions. Adding the corresponding NuGet package (and ensuring it is copied to the output) resolves the GroupDocsConversionException you are seeing [1][3][2].

3

@rthomas95
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CONVERSIONNET-8147

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.