We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Aspose.Words.Reporting.FieldMergingArgs class not being found

Aspose.Words Product Family
#1

I am trying to implement the document merging solution described here:
http://www.aspose.com/documentation/.net-components/aspose.words-for-.net/howto-insert-a-document-into-another-document.html

But for some reason the
Aspose.Words.Reporting.FieldMergingArgs class
and
Aspose.Words.Reporting.IFieldMergingCallback interface

are not being found. I am including the following Words libraries:
using Aspose.Words.Fields;
using Aspose.Words.Reporting;
using Aspose.Words;

#2

Hello

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Thanks for your request. Could you please try using the latest version of Aspose.Words (9.2.0). You can download this version from here:

http://www.aspose.com/community/files/51/.net-components/aspose.words-for-.net/category1188.aspx

Best regards,

#3

While this fixed that particular issue it broke a lot of my other code. Here is a short list:

Document.SaveToImage - no longer exists
Aspose.Words.SaveType - no longer exists
doc.MailMerge.MergeField - no longer exists

Is there a solution that won’t break my other code?

#4

Hi Abe,

Thank you for this additonal information. You are correct, there have been some changes to the public API in verison 9.2. These changes are minor and are mostly to make things easier. Fixing up your code is very simple, please see the table at the bottom of the download page here. It outlines the new names for the members that have changed.

  • SaveToImage has been integrated into the Save method now. You can find details from the API page here.
  • SaveType has become ContentDisposition, please see the API entry here
  • This event has become a property, you can find the details here

If you need any further help please feel free to ask.

Thanks,

#5

I can understand adding new features, but it seems strange to stop supporting old ones. This will require me to rewrite a significant portion of my code.

Is there a reason you removed them all together rather than deprecating them?

Is there any chance you will have a future release that will be backward compatible? If so, what would be the time frame?

#6

Hi Abe,

Sorry let me clarify, there have been no features removed from the latest version. The names of some features have simply been renamed or moved in the API. You can find the new names in my post above.

i.e instead of calling SaveToImage() now you simply call Save("out.tiff"). This will have the same affect as calling SaveToImage in the previous version. The SaveToImage method has been integrated into the Save method.

Thanks,

#7

I understand that I can achieve the same end with your updated library. I just think it’s unfortunate that certain methods have disappeared (which requires me to make code changes).

Can I humbly suggest that in your next release you keep the old methods in there and just hide them in intellisense?

Here’s a good link:
http://msdn.microsoft.com/en-us/library/system.componentmodel.editorbrowsableattribute.aspx

Thanks for your help!

#8

Hi

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Thanks for your suggestion, but there were few reasons of these breaking changes. These reasons are described in 9.2.0 version release notes:

http://www.aspose.com/community/files/51/.net-components/aspose.words-for-.net/entry247974.aspx

Also, it is no so difficult to change your code because none of functionality is lost. There two very good tutorial videos, which show how it is easy to change your code:

http://www.aspose.com/community/files/51/.net-components/aspose.words-for-.net/entry247978.aspx

http://www.aspose.com/community/files/51/.net-components/aspose.words-for-.net/entry247976.aspx

Best regards.