> 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/basic-operations/samples.md).

# Code samples for basic document operations in UWP

Learn how to read & write a PDF file from/to memory buffer, merge, copy, delete, rearrange PDF pages, and more with this informative guide. The Apryse uwp SDK streamlines secure document processing.

[Read & write a PDF file from/to memory buffer](/uwp/get-started/samples.md#pdfdocmemory) The sample illustrates how to read/write a PDF document from/to memory buffer. This is useful for applications that work with dynamic PDFdocuments that don't need to be saved/read from a disk.

[Merge, copy, delete, and rearrange PDF pages](/uwp/get-started/samples.md#pdfpage) The sample illustrates how to copy pages from one document to another, how to delete, and rearrange pages and how to use ImportPages() method for very efficient copy and merge operations.

[Read elements across all PDF pages](/uwp/get-started/samples.md#elementreader) Illustrates how to traverse page display list using ElementReader.

[Build, write, embed elements in PDF pages](/uwp/get-started/samples.md#elementbuilder) Illustrates how to use PDFNet page writing API, how to embed fonts and images and how to copy graphical elements from one page to another.


---

# 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/basic-operations/samples.md?ask=<question>&goal=<user_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.