[![Aspose.Diagram for .NET logo][1] is now live. The new version of the API allows developers to insert a text shape in the Visio diagram. Developers can also now retrieve an ActiveX control to edit all its available properties. This month’s release also improves performance in converting VSD diagrams to PDF format and covers a number of regular bug fixes and enhancements. Developers can install an Aspose.Diagram Nuget package in their .NET applications because we publish each version as [a NuGet package on the NuGet gallery][2]. We recommend our clients upgrade old version of Aspose.Diagram API to this latest one. For details on API fixes, please check Release Notes having a complete list of the features, enhancements and bug fixes.

Insert a Text Shape in the Visio Page

The Microsoft Office Visio application allows users to insert a text shape by clicking “A Text” button available in the Home tab under the Tools section. Using Aspose.Diagram API, developers can now achieve this feature in their project applications. From now onward, they may not add any alternative shapes from the stencil files. This help topic shows how to insert a text shape in the Visio page: Insert a Text Shape in the Visio Page

Retrieve an ActiveX Control from a Shape Object to Modify Properties

The last couple of Aspose.Diagram API releases has the support of inserting an ActiveX control in the Visio page. Developers were not able to retrieve and edit an ActiveX control. Using this new version, developers can retrieve an ActiveX control from a shape object, and then edit its properties. This help topic shows a code example to achieve this: Retrieve an ActiveX Control from a Shape Object to Modify Properties

This version also addresses the issues of general formatting problems, the invisibility of the group shapes, rendering cross signs in place of the various shapes and other minor layout problems of the drawings. These enhancements and bug fixes improve performance and accuracy of Aspose.Diagram API. Please check a list of the resolved defects:

  • Fixed: Can’t add shape menu item (action).

  • Fixed: VSDX to PDF conversion, incorrect sequence of line breaks in the text items.

  • Fixed: VSDX to PDF export, incorrect font of bold text items.

  • Fixed: VSD to PDF export - the bounding box color of the form icons is changed.

  • Fixed: Background color of the shape is changed on converting a VSD to PDF - I.

  • Fixed: Background Color of the shapes is changed on converting a VSD to PDF - II.

  • Fixed: The background color of shapes is changed on saving VSD to PDF.

  • Fixed: VSDX to PDF export - Solid lines of shapes are converted to dashed lines.

  • Fixed: Incorrect text alignment of the shape on converting a VSDX to PNG.

  • Fixed: The menu icons are not properly visible on converting Visio pages to SVGs.

  • Fixed: Shapes become invisible on grouping and saving in VSDM.

  • Fixed: Missing shapes on converting a VST to PDF.

  • Fixed: The background color of the page is not being preserved on converting a VSD to SVG.

  • Fixed: Open and Save VSDX - the cross signs appear in place various shapes.

  • Fixed: Open and save VSDX - the text of the shape turns into dummy characters.

  • Fixed: The text items are not aligned on saving a Visio in PDF.

  • Fixed: The width of connector lines is changed on saving a Visio in PDF.

Aspose.Diagram for .NET Resources

The following resources will help you work with Aspose.Diagram for .NET:

  • [Home page for Aspose.Diagram for .NET API][3].

  • Download Aspose.Diagram for .NET

  • Aspose.Diagram for .NET wiki docs - Help documentation and API reference documents.

  • [Aspose.Diagram product family forum][4] - Post your technical questions, queries and any other problem you faced while running Aspose.Diagram APIs.

  • [Enable email subscription][5] - Don’t limit yourself, stay up-to-date with the latest news about the Aspose.Diagram APIs and new features, fixes, plus other API related topics by subscribing to Aspose.Diagram blog.

  • [Aspose.Diagram for .NET Examples][6] – We have published our code examples on the social coding website GitHub.com. Anyone can explore the code examples for learning purposes.

  • Migrate from Earlier Versions of Aspose.Diagram API - We keep track of Aspose.Diagram API change version by version. So we recommend to get help from this section while upgrading to the latest API version or if Aspose.Diagram API code is broken at some stage.

We hope you’ll enjoy this new release that saves time and efforts. The API is quite simple and developers can use it in application easily.

Edit a Page-Level Comment in the Visio

[1]: https://blog.aspose.com/wp-content/uploads/sites/2/2013/06/aspose-Diagram-for-net_100.png “Aspose.Diagram for .NET logo”)](https://blog.aspose.com/wp-content/uploads/sites/2/2013/06/aspose-Diagram-for-net_100.png)We're pleased to announce that the [new version 16.11.0 of Aspose.Diagram for .NET API](http://downloads.aspose.com/diagram/net/new-releases/aspose.diagram-for-.net-16.11.0/ [2]: https://www.nuget.org/packages/Aspose.Diagram [3]: http://www.aspose.com/products/diagram/net [4]: http://www.aspose.com/community/forums/aspose.diagram-product-family/489/showforum.aspx [5]: https://blog.aspose.com/category/aspose-products/aspose-diagram-product-family [6]: https://github.com/asposediagram/Aspose_diagram_NET