How to Create Quality Code Examples for C# and VB.NET
Have a look, most of the public API members of our new Aspose.Editor component have code examples http://www.aspose.com/Products/Aspose.Editor/Api/Index.html. You decide whether they are good or not, but we think they are great and hope you like them.
We went through a lot of hurdles trying to find a suitable solution and I thought you might find it useful to know how we produce code examples now.
In my earlier post Authoring API Help for .
Aspose.Editor 1.0.0 Released!
Dear Ladies and Gentlemen,
Please welcome Aspose.Editor - our latest addition to the Aspose components family.
Aspose.Editor is a new breed of word processor control for Windows Forms .NET. A specially crafted page layout engine displays, edits and prints pages a lot like Microsoft Word, but inside your application. The native format for documents in Aspose.Editor is WordprocessingML with a unique feature of roundtripping even for complex documents. When used together with Aspose.
How to Install Your Control Into VS.NET 2003 or VS.NET 2005 Toolbox
We needed to make sure some of the Aspose components are installed into the Toolbox in VS.NET during installation. We sifted through many discussions about this on the net.
It is a trivial task, but looks like a lack of thought from Microsoft made it very complex. It is especially problematic because a reasonable way of installing the control to Toolbox in VS.NET 2003 does not work in VS.NET 2005.
Aspose.Words Testimonials
We were happy to find a bunch of great Aspose.Words testimonials at 411ASP.NET recently. Apparently, our marketing team knows this place (since Aspose has an advert there), but we, the development team came across it first time and it was a big pleasure to read. There is also a separate topic in the Support Forums for testimonials.
Remember you are always welcome to post, it does make difference to us. Positive and constructive is appreciated and leads to a better product.
Performance Test of Large File
Just wanted to share results of one of the performance tests we do right now before finalizing Aspose.Words 4.0. We think the results are very good, hence we want to share them. The test is for a quite LARGE file, so it is pretty much a stress test if you like. Most of the files you will process with Aspose.Words are likely to be smaller and process much faster.
Test Setup
Follow up to Drawing Objects
In the previous topic I forgot to really tell why support for drawing objects in Aspose.Words for .NET 4.0 is really AWesome.
Current support for drawing objects in Aspose.Words for .NET 4.0 is by far the most thorough and comprehensive comparing to any existing competing commercial or open source packages. Support for drawing objects is only better of course in Microsoft Word itself.
There is also the high-fidelity conversion from DOC to RTF and WordprocessingML without losing any of the formatting.
AWesome Drawing Objects
I liked the AWesome line started by my colleague Dmitry Vorobyev in a post about his work on RTF export and I want to carry it on to describe what we’ve done for drawing objects in Aspose.Words 4.0.
Drawing objects in Microsoft Word documents are images, shapes (also called auto shapes), group shapes, textboxes, diagrams, OLE objects, ActiveX controls, horizontal lines and WordArt objects.
In the binary DOC format they are sometimes called “Escher”, probably an early code name from Microsoft.
Aspose.Words for Java 1.0.5.0 Released
In this version:
Updated Aspose.Words for Java API Reference. It is always up to date now since it is auto-generated from C# XML documentation with appropriate changes for Java. Ported the DocumentExplorer demo to Java, added as a demo project. Added basic PDF export using iText to the demo projects. Note this export is very basic and is only intended to show how to extract content from a Word document using Aspose.
Going Transitional (exporting to XHTML)
A number of customers asked for Aspose.Words to produce XHTML compliant HTML when exporting and I’m happy to tell you that we did it.
Aspose.Words used to output some unclosed tags, for examplethat were okay from HTML point of view, but precluded customers from using those as XML files.
Starting from Aspose.Words 4.0, we always output well-formed XML when exporting to HTML format. It is the main point that we addressed.
Happy Import of HTML Tables and CSS Length Units
There’s been a public outcry for Aspose.Words inability to import CSS length units other than points. A related issue was about Aspose.Words throwing exceptions when encountering HTML that it cannot recognize. Yet another popular support issue was about HTML tables, that when imported, had cell and table widths quite different from the original.
We are happy to announce all of these issues were addressed in Aspose.Words 4.0.
All CSS length units (except em and ex at this stage) are now supported.