Thank you for your inquiry.
We are sorry to hear that you are facing such issue. We have reproduced this scenario at our end and sharing this with product team for resolution. Once we have any update regarding this issue we will notify you here.
Thank you for your patience.
We are pleased to apprise you that your reported issue (CONVERSIONNET-2042) is resolved. The fix is available in 17.9.0 version of the API. Please download and evaluate the latest release.
Thanks for the update. I will give it a shot when I finish my current task.
I’m still not seeing version 17.9 version of groupdocs-conversion-dotnet available via NuGet even when allowing pre-release versions. Will this be coming out soon?
GroupDocs.Conversion for .NET 17.9.0 is already released. See NuGet package here. You can also get DLL from GroupDocs public API download page. However, the latest version of the API is 17.11. We’d recommend you to utilize latest release in your project.
It’s not showing anything greater than 17.8.0 available for my project in the package manager. Seems odd.
So it appears you all recently changed the name of the nuget package from “groupdocs-conversion-dotnet” to “GroupDocs.Conversion”. “groupdocs-conversion-net” only goes up to 17.8.0.
Anyway, changing the dependencies really quickly on my machine, updating per the obsolesced properties and methods, and running a sample image through, it appears to now output my requested G4 TIFF.
I will have to change the dependencies of my NuGet package and do a couple builds tonight for it to be ready for QA tomorrow. Hopefully they can get to it tomorrow but, again, in my quick test it seemed to work perfectly.
One last thing hopefully: Is there a place where I can see what the changes were in the various versions? Do you recommend simply using the latest version?
We are pleased to hear that.
Yes, you can see what changes were made or introduced in different releases/versions in release notes of the API.
Yes, you can see what changes were made or introduced in different releases/versions in release notes1 of the API.
Thanks for that. Very well organized. Kudos.
QA was good with my new version based on your fix. Thanks again!