> For the complete documentation index, see [llms.txt](https://docs.vezel.dev/ruptura/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vezel.dev/ruptura/usage.md).

# Usage

Broadly speaking, Ruptura's packages can be split into three different categories of functionality:

* [Vezel.Ruptura.Injection](https://www.nuget.org/packages/Vezel.Ruptura.Injection) and [Vezel.Ruptura.Hosting](https://www.nuget.org/packages/Vezel.Ruptura.Hosting) provide the ability to inject the CoreCLR runtime and managed assemblies into a target process.
* [Vezel.Ruptura.Memory](https://www.nuget.org/packages/Vezel.Ruptura.Memory) provides function hooking, memory manipulation, and call tracing capabilities.
* [Vezel.Ruptura.System](https://www.nuget.org/packages/Vezel.Ruptura.System) provides managed wrappers around operating system APIs and kernel objects.

You can pick and choose which of these packages you would like to use. For example, if you already have a working solution for injection, you may want to just use **Vezel.Ruptura.Memory** for its function hooking APIs, or **Vezel.Ruptura.System** for convenient Win32 API access. You could also use **Vezel.Ruptura.Injection** and **Vezel.Ruptura.Hosting** to inject your managed assembly, but choose to implement your own function hooking method.

Either way, simply use `dotnet add package <name>` to add the relevant package(s) to your project and start writing code. No further configuration is required.


---

# 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.vezel.dev/ruptura/usage.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.