> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/uwp/learn-more.md). # Learn more - [Add license key](https://docs.apryse.com/uwp/learn-more/add-license.md): Ready to get a production license for your application? Learn how to purchase a license key and properly use it to avoid watermarked demo/trial mode. Contact sales now for more information! The Apryse - [Displaying full error message when working with UWP](https://docs.apryse.com/uwp/learn-more/error-handling.md): Learn how to handle exceptions effectively in PDFNet with the Apryse SDK for UWP. Get detailed error messages and custom information using the PDFNetException class. Follow this code snippet for bette - [UI icon cheat sheet for UWP viewer](https://docs.apryse.com/uwp/learn-more/icon-cheatsheet.md): Discover a variety of tools like rectangles, ellipses, arrows, and more to enhance your document editing experience. Try out the free highlighter, signature, and ink drawing features now! The Apryse u - [Mobile supported file types for document conversion in UWP](https://docs.apryse.com/uwp/learn-more/format-mobile.md): Discover the best tips for writing an effective SEO meta description. Learn how to craft compelling descriptions that drive clicks and improve your website's search engine visibility. The Apryse uwp S --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.apryse.com/uwp/learn-more.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.