Save opened document after changes (VSD format)?

Aspose.Diagram Product Family
1

Hi Aspose team,

I saw that other people had same question - when will we be able to create VSD files?

Btw. I need to open VSD file, manipulate it and save it. Filename, fil format will stay the same so at the end I need

doc.save()

which will save opened document.

As far as I can see there is request DIAGRAM-31002 since 2009.

Thanks,
Oliver

2

Hi Oliver,


Thank you for contacting support. Well, saving Visio diagrams in VSD (binary format) is a complex task and we have a less number of this feature requests. It is because users can save to an alternative format as VDX. Anyway, our development team has plans to save Visio diagrams in VSDX format first. Recently, we did not have plans to support saving in VSD format. The saving of Visio diagram in VSDX format support is expected in the second half of year 2015. It’s all depend if everything goes by plan.

3
Hi,

any news regarding support to save Visio documents in VSxx formats?
Are you going to support all types => VSDX, VSDM, VSSX, VSSM, VSTX, VSTM?

Thanks,
Oliver
4

Hi Oliver,


Thank you for the inquiry. Please note, our product team has plans to save Visio drawing in the VSDX format in the recent year. We have logged your requests to support other Visio 2013 formats as follows:

DIAGRAMNET-50015 - Writing support for new MS Visio 2013 VSDX format.
DIAGRAMNET-50564 - Writing support for new MS Visio Stencil 2013 VSSX format
DIAGRAMNET-50565 - Writing support for new MS Visio Template 2013 VSTX format
DIAGRAMNET-50566 - Writing support for new MS Visio Macro-Enabled Drawing 2013 VSDM format
DIAGRAMNET-50567 - Writing support for new MS Visio Macro-Enabled Stencil 2013 VSSM format
DIAGRAMNET-50568 - Writing support for new MS Visio Macro-Enabled Template 2013 VSTM format

Your post has also been linked to these issues. We’ll keep you informed regarding any available updates. We’re sorry for the inconvenience caused.

5

Hi Oliver,


Thank you for being patient. We have a good news for you that the issue id DIAGRAMNET-50015 has now been resolved. If there is no issue in the QA phase, then this fix will be included in the next version of Aspose.Diagram for .NET 5.8.0. We’ll inform you via this forum thread as soon as the new release is published.

6

The issues you have found earlier (filed as DIAGRAMNET-50015) have been fixed in Aspose.Diagram for .NET 5.8.0.

This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
(6)
7

Hi Oliver,


Thank you for being patient. We have a good news for you that the issue ids DIAGRAMNET-50564 and DIAGRAMNET-50565 have now been resolved. If there is no issue in the QA phase, then their fixes will be included in the next version of Aspose.Diagram for .NET 5.9.0. We’ll inform you via this forum thread as soon as the new release is published.

8

The issues you have found earlier (filed as DIAGRAMNET-50564;DIAGRAMNET-50565) have been fixed in Aspose.Diagram for .NET 5.9.0.

This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
9

Hi Oliver,


Thank you for being patient. We have a good news for you that the ticket ids DIAGRAMNET-50566, DIAGRAMNET-50567 and DIAGRAMNET-50568 have now been resolved. If there is no issue in the QA phase, then their fixes will be incorporated in the next version 6.6.0 of Aspose.Diagram for .NET API. We’ll inform you via this forum thread as soon as the new release is published.

10

The issues you have found earlier (filed as DIAGRAMNET-50566;DIAGRAMNET-50567;DIAGRAMNET-50568) have been fixed in Aspose.Diagram for .NET 6.6.0.

This message was posted using Notification2Forum from Downloads module by Aspose Notifier.