I encountered two problematic cases with exporting Visio diagrams to SVG format. I do a simple transformation via the method Diagram.Save according to documentation -Diagram.Save | Aspose.Diagram for .NET API Reference
After transformation, SVG elements differ from the original Visio content. I attached the original Visio diagrams (InputFile1.vsdx and InputFile2.vsdx) and SVG files (OutputFile1.svg and OutputFile2.svg) obtained after transformation.
Could you review my files from the attached archive and fix the problem in the next release?
Summary
We are aware of the issue where converting certain VSDX files to SVG results in two arrow shapes being rendered at an incorrect (very large) size.
Why it happens
The problem is caused by a defect in the SVG export implementation of the current Aspose.Diagram library. It mis‑calculates the geometry of some line‑end (arrow) shapes, so the generated SVG does not match the original Visio diagram.
What to do next
Report the issue – Please open a support ticket (or reply in the forum thread) and attach the original VSDX files and the generated SVG files. This information helps the product team reproduce the problem and work on a fix for an upcoming release.
Check for a newer version – Occasionally, bugs are addressed in later builds. Verify whether a newer Aspose.Diagram version is available and test the conversion again. If the issue persists, continue with the steps below.
Work‑around (if you need a quick fix) – As a temporary measure you can disable the rendering of line‑end shapes, which will produce plain lines instead of arrowheads. This can be done by setting the appropriate option in SvgSaveOptions (e.g., ExportLineEndings = false). Note that this removes the arrowheads from the output SVG.
Provide environment details – When contacting support, include:
.NET runtime version (e.g., .NET 6, .NET Framework 4.8)
Operating system (Windows 10/11, Linux, etc.)
Any custom stencils or shape libraries used in the VSDX file
The exact version of Aspose.Diagram you are using
The support team will use this information to investigate further and provide a permanent resolution.
We appreciate your patience while we work on fixing this bug.
I could not fully verify this explanation against the retrieved sources. Please double-check the behaviour in your environment and confirm the exact SDK/version.
@krserg
Thanks for the template file and output svgs.
After an initial testing, I am able to reproduce the issue as you mentioned by using your template file.
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): DIAGRAMNET-53851,DIAGRAMNET-53852
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.
I could not fully verify this explanation against the retrieved sources. Please double-check the behaviour in your environment and confirm the exact SDK/version.