We started to target .NET Framework 1.1 since Aspose.Word 1.6. Sorry the requirements page was not updated.
You should be able to edit your application configuration file and make Aspose.Word target .NET Framework 1.0 as described in MSDN article Targeting a .NET Framework Version.
Improved list formatting when integrating with Aspose.Pdf. Support for indentation, restart numbering, different bullets.
Support hyperlinks when integrating with Aspose.Pdf. Hyperlinks both inside a document to bookmarks and external links to urls are correctly recreated in the PDF document.
Fixed STG_E_FILENOTFOUND thrown for some .doc files.
Fixed NullReferenceException thrown when saving a Word document. This is only applicable if you used an evaluation license and your normal character style had some shading set explicitly (even empty shading).
Allow multiple paragraphs inside text form fields.
Custom bullet characters are now correctly output into PDF, you need to use latest Aspose.Pdf for this too.
Images can now take 100% width of the page when saving in PDF format.
Allow inserting and removing text that contains multiple paragraphs into form fields. Previous version was just letting multiparagraph text in form fields to pass from input to output document.
Added DocumentBuilder.EndTable method that you should (but not required) to call at the end of a table. Calling this method explicitly moves the cursor out of the table.
Hello,
I just started using the Aspose.Word evaluation assembly today, and I’m pretty sure I ran into a bug. I’ll bet that’s what many users say when they’re doing something wrong, though, so I’ll let you decide for yourselves:
Using a letter size (8.5 x 11in = 612 x 792pt) page, the DocumentBuilder.PageSetup.PageWidth and DocumentBuilder.PageSetup.PageHeight are reversed…
I added a Watch on the DocumentBuilder.PageSetup object in debug, and the following items are of interest to the situation: