The Aspose.Svg and Aspose.Drawing.Common libraries are incompatible with each other. An example of code.
Aspose.Svg.Rendering.Image.ImageRenderingOptions test = new Aspose.Svg.Rendering.Image.ImageRenderingOptions();
test.SmoothingMode = Aspose.Drawing.Drawing2D.SmoothingMode.AntiAlias;
The error we have : CS0266
The question is, why does Aspose.Svg use System.Drawing.Common instead of Aspose.Drawing.Common? If it’s a question of compatibility, why not make your library compatible with both? Is there a workaround for this issue?
As a second point, the fact that many Aspose products use System.Drawing.Common, makes it complicated to use System.Drawing.Primitives with the Aspose.Drawing library (not Aspose.Drawing.Common) at the same time.
As an example of a use case, we have a project and within this project we use the Aspose libraries and also other external libraries. These libraries need System.Drawing.Color, present in System.Drawing.Primitives. When using Aspose.Drawing.Common, we have a CS0266 incompatibility between Aspose.Drawing and System.Drawing in the external library. This problem only arises when Aspose products use System.Drawing.Common (e.g. Aspose.HTML, Apose.SVG) instead of Aspose.Drawing. When they use Aspose.Drawing, the problem disappears. The Aspose.Tasks product had the same behavior, now, after an update on your part, it’s gone https://releases.aspose.com/tasks/net/release-notes/2024/aspose-tasks-for-net-24-6-release-notes/ .
A new question arises here: why are Aspose products incompatible with each other?
Thank in advance.
