Render STL and IFC File Formats using GroupDocs.Viewer for .NET 17.10

GroupDocs Viewer for .NET

We are pleased to announce the release of version 17.10 of GroupDocs.Viewer for .NET. This monthly release has come with 3 new features and more than 10 improvements and bug fixes. GroupDocs.Viewer for .NET 17.10 allows you to render STL and IFC file formats. Furthermore, settings to hide/show hidden pages have been extended for Microsoft PowerPoint documents. Please continue to read more about the latest version.

Render STL and IFC File Formats

From version 17.10, GroupDocs.Viewer supports rendering of STL and IFC file formats. For more details on supported file formats, please visit this documentation article.

Rendering Hidden Sheets, Slides or Pages

Microsoft Excel, PowerPoint and Visio documents may contain hidden pages (slides or sheets). By default, hidden pages are not rendered. In order to include them into the rendering, set ShowHiddenPages property of the RenderOptions (ImageOptions or HtmlOptions) class as true. This new setting has replaced obsolete CellsOptions.ShowHiddenSheets and DiagramOptions.ShowHiddenPages properties in RenderOptions class.

For more details on rendering hidden pages, please visit this documentation article.

Rendering Worksheets by Dividing into Pages

By default, GroupDocs.Viewer for .NET renders the whole Excel sheet into a single HTML/image page or into a single page of the PDF document. However, the API also allows dividing large Excel sheets into multiple pages. From version 17.10, this feature is supported for rendering the document as PDF and as image with enabled text extraction.

For more details, please visit this documentation article.

Improved Document Rendering from Stream into HTML

In earlier versions, when we render document from the stream and do not provide document name, API has been suppressing saving resources separately and embedding resources into HTML regardless of IsResourcesEmbedded setting. Since the version 17.10, when document name is not provided, API tries to generate document name from the stream. When that stream is rendered again, API will generate the same name. However, try to avoid not passing document name in cases when document name is known because API does not guarantee that document type will be detected and that document name will be unique for the stream (as in some cases, API may generate the same name for two different streams).

.NET Document Viewer API – Fixes

Following are the issues that are fixed in version 17.10.

  • Gray rectangles instead of image parts
  • Empty space between text is lost when rendering email documents
  • The parameter ‘address’ cannot be an empty string exception when rendering MSG document
  • Some rows/records are missing when rendering Excel document to HTML
  • Parameter is not valid exception when rendering Excel document to image
  • The output image gets cut when rendering PowerPoint presentation
  • All pages are same when rendering Microsoft Project document into an image
  • Incorrect rendering of PDF document into HTML
  • Exception when rendering CAD file into image

Related Links and Resources

We have a few channels and resources for you to download, learn, try and get technical support on document viewer API.

Feedback

As always, if you have any questions or suggestions, feel free to write on our forum.

Share on FacebookTweet about this on TwitterShare on LinkedIn