We have a major update for our customers who are using our metadata manipulation API – GroupDocs.Metadata for .NET. We have revamped the architecture of the API to improve and simplify the process of reading, updating, searching or removing the metadata properties from the documents. So let’s take a tour of the latest release.
Why do you need to upgrade?
You should upgrade to the latest release because:
- The Metadata class is introduced as a single entry point to manage metadata in all supported formats.
- Extracting and updating metadata has been unified for all supported formats.
- The product architecture has been redesigned from scratch in order to simplify the most common operations with metadata properties.
- The process of getting document information and preview generation has been simplified.
How to migrate?
All public types of the legacy API have been moved from the GroupDocs.Metadata namespace to the GroupDocs.Metadata.Legacy namespace. Furthermore, all the legacy types have been marked as obsolete and will be removed in future releases.
Once you upgrade to the latest release, you will have to do the project-wide replacement of GroupDocs.Metadata. namespace with the GroupDocs.Metadata.Legacy. to successfully build your solution.
Comparison of Coding Styles
Since the API has gone under the major updates, the classes/properties/methods and the way they are used has also been changed. The following is the code comparison of some common metadata operations. This will give you an overview of how things have changed.
Finding Metadata using Regular Expressions
The following code samples retrieve metadata from a file using a regular expression.
v19.11 or Later
Replacing Metadata using Regular Expressions
The following code samples show how to replace metadata properties using a regular expression.
v19.11 or Later
For more details, please have a look at the migration notes.
You can download and evaluate the source code examples of the latest release from the GitHub repository. For more details about every feature of the API, please visit the documentation. In case you find something difficult for you, feel free to contact us via our free support forum.