Saving out native constituent files while performing GroupDocs.Conversion on container file formats?

While performing recursive conversion of container file formats, e.g. in these 3 samples:

Convert PST or OST documents to different formats | Documentation (groupdocs.com)

Convert each email attachment to different format | Documentation (groupdocs.com)

Convert each email attachment to different format | Documentation (groupdocs.com)

Is it possible to also intercept each of the constituent files that are converted so that we can save out copies of the native constituent files?

@jarrodwee
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CONVERSIONNET-6831

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

Thanks, will create a new ticket in the Paid Support.

Additionally, the original filenames of the native constituent files will be required for setting the filenames of the native and converted files.

1 Like

@jarrodwee

This ticket is escalated to paid support.

The issues you have found earlier (filed as CONVERSIONNET-6831) have been fixed in this update. This message was posted using Bugs notification tool by nikola.yankov

@atir.tahir will this fix make it into GroupDocs.Total.NETFramework 24.4?

@jarrodwee

We are investigating this, your investigation ticket ID is TOTALNET-72. You’ll be notified in case of any update.