Hi,
You fully support reading of OST files (up to Office 2021), and writing of PST files.
So why this method no longer works?
(not implemented error)
If you think can be added as suggestion please go on, otherwise you’ve got a sample to manually read ost and write all items to pst, keeping the source hierarchy in the target?
Since Office 2013, the OST format has been changed significantly. The changes have not been documented in the MS specification. On the other hand, the old OST format was same as the PST format, which is fully described in the MS specification.
The methods PersonalStorage.ConvertTo and SaveAs were implemented to work with the old OSTs. These methods were developed for the fast OST to PST converting; just change the file header.
But this does not work for the new OSTs. To convert the new OST to PST, create a PST and use the MergeWith method. Unfortunately, for big-sized files the conversion process won’t be that fast.
We will fix reported bugs related to MergeWith method in further releases.
That’s very fine, doesn’t matter if not fast, but I’m getting errors preventing the conversion, any guess if will be fixed by the end of the year?
And, for large file conversions, will you add a manner of progress/simple report event to the storage writers (pst/mbox) so at least the developer can show the progress via a ProgressBar?
Peace
Dude, of course Aspose Email is not a UI component, I meant adding storage_process / storage_report events so we can show the time consuming operations’ progress using a ProgressBar (and show basic operation reports)