Do you have a solution implemented for barcode translation, we do not need to generate barcodes, only translate
Could you please elaborate and provide more details on your requirements. We will then understand your needs and assist you accordingly. Do you need to read barcodes?
The aspose bar code .net has barcode reading and barcode creation capabilities. We only need barcode reading capabilities without memory leak. If this has been implemented and released, please let me know. Otherwise, could it be an option to release barcode reading if this works without barcode generation being changed, and then release again when you have the barcode generator implemented with aspose.drawing.
Thanks for providing further details about your requirements.
We now understand your needs. We will update you soon on it.
Any news on this topic?
The feature (Aspose.Drawing support to Aspose.Barcode) is still in progress.
We still need more time on your query:
Please spare us more time. Once we have any new information available on it, we will update you here.
We are sorry for any inconvenience caused!
To update you on it. currently we have problems with fonts fallback on linux but it already works. We will add/include it in current state to February release next month. Also, we have problems with GIF processing in .NET Core, but GIF is obsolete format and modern formats are PNG and TIFF which are supported well. So we are good to go with it.
Could you test Aspose.Drawing.Common on your system.
This library which replaces System.Drawing.Common in February release, but currently it has porblems on some Linux systems.
Could you test text drawing fuctions - draw some text on bitmap. It has simular to System.Drawing functions but namespaces Aspose.Drawing.*?
What should I test? We use aspose barcode, but does not use the drawing component. we only use it for reading barcodes, and not generating barcodes.
We see memory leak when reading/decoding the barcodes in linux.
Just to make sure that Aspose.Drawing.Common would work in your environment, we requested you to kindly test text drawing functions - draw some text on bitmap. It is similar to System.Drawing functions but namespace is as Aspose.Drawing. This way you would at least know Aspose.Drawing.Common would work fine in advance. Aspose.Drawing.Common would be included into February release.
I am also having this memory leak problem in linux systems due to System.Drawing.
I have seen in the release notes of 23.2 version that you have finally switched to the Aspose.Drawing implementation. I am looking forward to try if this new version solves all the System.Drawing related problems but I can’t see the new version released in NuGet. Any ETA for this? Is there any other way to get this new version?
1 Like
Yes, Aspose.BarCode for .NET 23.2 was not released to nuget repos. yet. We will surely do it after performing certain configurations. We will check if we could provide latest updates on it.
In the meantime, you may download the Dlls version and manually add reference to your desired Aspose.BarCode for .NET assembly in your project.
We are sorry for any inconvenience caused!
I am trying to use the 23.2 Aspose.Barcode DLL as you suggested but I am facing an issue.
Barcode reader needs Aspose.Drawing.Bitmap but It doesn’t exist in the Aspose.Drawing assembly. I have tried 23.1 and 23.2 versions of Aspose.Drawing. Which is the correct one that works with Aspose.Barcode 23.2?
We have:
- Aspose.Drawing.Bitmap from Aspose.Drawing.Common
- System.Drawing.Bitmap from Aspose.Drawing.
Currently older Aspose.Drawing uses System.Drawing namespace and conflicts with System.Drawing.Common (or any libraries which use it).
You need to use latest Aspose.Drawing.Common.
<ItemGroup>
<PackageReference Include="Aspose.Drawing.Common" Version="23.2.0" />
<PackageReference Include="System.Text.Encoding.CodePages" Version="7.0.0" />
</ItemGroup>
Hope, this helps a bit.
Aspose.PDF will be updated after Aspose.Drawing reorganizes namespaces and nuget packages (Aspose.Drawing will be in Aspose.Drawing namespace and Aspose.Drawing.dll, Aspose.Drawing.System will be in System.Drawing namespace and Aspose.Drawing.System.dll). It will be done to middle of April 2023.
1 Like
Hello amjad.sahi,
Can we confirm is this issue is solved. We are using Aspose.BarCode 24.9.0?
Regards,
Yulian
You may use Aspose.BarCode 24.9.0 but it is recommended to use latest version/fix: Aspose.BarCode v25.4 which has more enhancements and fixes.
Hello amjad.sahi,
Thank you for your quick answer. My question is can you confirm that the Barcodes memory leak on Linux is fixed in the cited version. We plan to update to the latest one, but in the meantime we want to be sure that the issue is fixed, so we can release some changes that we made, that contains code that was affected by this memory leak
Regards
Yes, the memory leak issue should be resolved in the newer versions. Therefore, it is recommended to try the updated versions. We utilize Aspose.Drawing.Common as the graphics API for .NET Standard 2.0, .NET 6.0, 7.0, 8.0, and later versions on non-Windows operating systems (e.g., Linux). It is advisable to test the latest version in a simple project using evaluation mode (without applying the license) on a test Linux server or machine before proceeding with the upgrade.
1 Like
Yes, Aspose.BarCode works stable on Linux from version 23.8.1 since it uses Aspose.Drawing.Common.
However new Aspose.BarCode versions have new improvements and it is recommended to use last version.