We have a pptx file. When convert it to pdf on Windows only 1G memory has been used. But convert it on Linux.It will take more than 3.5G memory. And the process will keep more than 2G memory don’t free.
Then we trace the problem and find that :
That problem looks like System.Drawing.Common caused. And .net6 will ship on november. Then the library which dependent on System.Drawing.Common 6 will not run on linux.And we checked that
is dependent on System.Drawing.Common now.
Is there any roadmap or time point for replace it?
We are already working on replacing System.Drawing dependency with one of our components i.e. Aspose.Drawing. The ticket is DRAWINGNET-331 which was logged in order to integrate Aspose.Drawing with Aspose.PDF to remove System.Drawing dependency. The ticket has been linked with this post now and you will be notified once it is resolved. As far as Aspose.Slides is concerned, we will share related information with you soon.
From Aspose.Slides perspective, we will include support of .NET 6 in our roadmap which is no earlier than Q1 of 2022. We have added a ticket with ID SLIDESNET-42778 in our issue tracking system so that we may share notification with you once the support will be included.
Hello, .NET6 is coming real soon (about a month).
System.Drawing.Common is used a lot in Aspose : Aspose.pdf, Aspose.Barcode, Aspose.Drawing, …
This is critical now, as the support in .NET5 will stop in 7 month.
Is there any update on this issue ?
We are gathering details on our end and will share details with you as soon as they will be shared.
We have logged a ticket in our database to investigate this scenario in Aspose.BarCode. You will be notified here once any update is ready for sharing.
This issue is logged as:
BARCODENET-37915 - Support for .NET6 and alternate of System.Drawing.Common
To update you regarding Aspose.BarCode (ticket logged as “BARCODENET-37915”), we decided to replace System.Drawing with Aspose.Drawing as system library (Aspose.Drawing image objects can be used to exchange data between user code and Aspose.Barcode code). However Aspose.Drawing has a lot of problems, so at this time it is unusable. We work with Aspose.Drawing to solve the issues and add support of Aspose.Barcode on Xamarin.IOS, Xamarin.Android and .NET6 platforms. This was previously planned to 2022Q1, but since problems with Aspose.Drawing could be more serious, so the solution could be shifted to more later date/time.
Once we have more updates on it, we will share it here.
The issues you found earlier (filed as SLIDESNET-42778) have been fixed in Aspose.Slides for .NET 23.2 (ZIP, MSI).
You can check all fixes on the Release Notes page.
You can also find the latest version of our library on the Product Download page.