> For the complete documentation index, see [llms.txt](https://www.tvrename.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.tvrename.com/technical/development.md).

# Development

Details of the way that TV Rename is written and developed

### Source Code <a href="#source-code" id="source-code"></a>

You can find TV Rename’s source code (along with executables and this website) in [The TV Rename GitHub Repository](https://github.com/TV-Rename/tvrename).

### Development Links <a href="#development-links" id="development-links"></a>

* You can find the Developers Wiki [here](https://github.com/TV-Rename/tvrename/wiki)…
* For the longer term you can visit the “[Roadmap](https://github.com/TV-Rename/tvrename/milestones?direction=asc\&sort=due_date\&state=open)” which lists the proposed Milestones (a high level view of what's planned for when).
* In addition there is a [Developers Forum in Google Groups](https://groups.google.com/forum/#!forum/tv-rename-development) which you can request access to.

### Frameworks <a href="#framework" id="framework"></a>

#### Winforms C# application

#### .NET 10

TV Rename runs on the Microsoft .NET 10 Desktop Runtime. The installer doesn’t include it; if it isn’t on your PC, Windows tells you when you start TV Rename. It’s a free download from [Microsoft](https://dotnet.microsoft.com/en-us/download/dotnet/10.0).

#### C++

TV Rename needs the Microsoft Visual C++ Redistributable (v14, 2017 or newer) for the built-in browser it uses to show information (the CEF Framework). The app checks for it and, if it's missing, downloads the installer for you.


---

# 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://www.tvrename.com/technical/development.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.
