Hello,
Following an upgrade to the most recent version of GroupDocs.Conversion, I am now seeing compile errors as PublisherLoadOptions class no longer exists.
What is the replacement for this? What load options should I be using instead? Is this still supported?
Thanks
It appears that the PublisherLoadOptions class has been removed in the latest version of GroupDocs.Conversion, which has led to compile errors in your project. Unfortunately, there hasn’t been a clear announcement regarding a direct replacement for this class in the release notes.
Currently, the support team is aware of this issue and is investigating it. They have indicated that the resolution of this matter is dependent on another internal ticket. As of now, there is no specific alternative load option provided for handling MS Publisher (.pub) files in the latest version.
For the most accurate and up-to-date information, I recommend keeping an eye on the official release notes and the support forum for any updates regarding this issue. If you have specific requirements or need further assistance, consider reaching out to the support team directly for guidance.
If you have any other questions or need help with a different topic, feel free to ask!
Thanks for the reply, I can continue using a generic conversion.
However I notice that a lot of constructors and methods are now obsolete, giving me warnings everywhere.
What is the new expected way to convert a file stream with load options and convert options and get an output stream?
Below is what I am currently using
var loadOptions = new WordProcessingLoadOptions();
using (var converter = new Converter(() => ms, () => loadOptions))
{
var convertOptions = new PdfConvertOptions();
converter.Convert(() => new MemoryStream(), (fileName, fileType, outputStream) =>
{
outputStream.CopyTo(fs);
}, convertOptions);
fs.Seek(0, SeekOrigin.Begin);
}
Thank you for contacting us. This class, GroupDocs.Conversion.Options.Load.PublisherLoadOptions, has not been removed or hidden and should be available at the specified path. Could you please specify the version of the product you’re using and share a sample of your code?
We look forward to assisting you.
v24.10 of GroupDocs.Conversion.NET doesn’t have a GroupDocs.Conversion.Options.Load.PublisherLoadOptions as far as I can see?
I have resolved the issue around obsolete methods now.
Apologies for any confusion. We’ve confirmed that this class is indeed only accessible through the GroupDocs.Conversion.CrossPlatform package. Please feel free to contact us if you have further questions—we’re here to help.
Hello,
Publication2.zip (195.9 KB)
Thanks for the update. Why has publisher conversion been removed from .NET? I really need it added back in.
There is no mention of it being removed and the documents imply it should still work.
Convert publisher formats | Documentation
I have a very simple sample file that I have tried converting and it just fails altogether, with the below error.
I’m certain this was supported in previous versions. I have attached the sample file in the .zip as upload of .pub is not supported.
Conversion from () to pdf (PDF) is not supported.
Hello @rthomas95,
Could you confirm the .NET framework you’re working with? As mentioned, this format remains supported in the cross-platform version. Are there specific reasons you’re not considering that option?
It is using .NET Framework 4.8.
The CrossPlatform package wasn’t a thing when this was first added in.
Thanks for providing the details. This will require extra time on our side to resolve. Would it suit you if we shared a custom library build that includes .pub format support?
Ideally I would prefer if support was in the main product, not necessarily the PublisherLoadOptions, as I know there are lot of challenges around converting this format. We reference and build everything via Nuget so having it in the normal feed is preferred.
If support has been completely removed from the product then I would understand, but it is still documented and in CrossPlatform so I’m very confused as to why it was removed from one?
Due to the 250MB NuGet package size limit, we had to remove support for this format from the main package. We’re currently evaluating how to include .NET Framework builds in the main package, and we’ll inform you as soon as we reach a decision.
Ah, I understand. I did not realise Nuget had a limit on package sizes to be honest. Would a separate package of GroupDocs.Conversion.Publisher or something work?
Or even GroupDocs.Conversion.UnstandardTypes or something that you could potentially expand in the future? Just an idea.
Thanks for your ideas. We’ll carefully review all potential solutions and will get back to you with the results at the earliest opportunity.