Assembly Chat
Open the app: Chat with a .NET assembly → (products.documentize.ai)
In one sentence
Assembly Chat reads the public API of a .NET assembly (a DLL, an EXE or a NuGet package), then lets you scan it into diagrams and tables, ask questions about it in plain English, get statistics, or compare two versions to see what changed.
What makes it unique
Most "chat with code" tools read source code. Assembly Chat reads the compiled library, so it answers from the real signatures and XML doc comments of the exact version you give it, not from a guess about the library. It is also the only app in this family that can diff two package versions before you upgrade. Its answers come from a searchable index (RAG) built from your assembly, which is why follow-up questions are fast: the scan is done once and reused.
When to use it / when not to
- Use it to learn a dependency you do not know ("how do I read a document and save it as PDF with this library?"), to get class diagrams for a design review, or to see what a new package version removed or changed.
- Use it before an upgrade: compare the version you run with the one you want.
- Not for your own source code → Code Graph maps a repository, and Repo Docs writes its documentation.
- Not for non-.NET libraries. The page documents managed .NET assemblies only.
Before you start
- A managed .NET assembly (
.dllor.exe), or the name of a NuGet package (and optionally a version). The page's FAQ lists .NET Framework 4.6.2+, .NET Core 3.1+ and .NET 5 to 8. - What the AI sees: public types and their public or protected members. Internal and private members are left out unless you tick Include Internal.
- For a Diff, either two DLLs, or the package name and version for the "before" and for the "after".
Step by step
- Open Assembly Chat and pick a Command (see the table below). The default is Scan.
- Provide the input: upload a DLL, or type a NuGet Package (and NuGet Version; leave blank for the latest).
- For Chat, type your question in Query. For Diff, fill in the "After" package and version too.
- Run it. For a chat, the answer appears in a chat pane.
- Ask follow-up questions in the same pane. The scan is reused, so follow-ups should come back much faster than the first answer. New scan (or the new-chat button) starts over.
Options explained
| Option | What it does | Default | Recommended |
|---|---|---|---|
| Command: Scan (generate UML and CSV) | Reads the assembly and produces diagram sources and tables | selected | First look at a library |
| Command: Chat (ask a question) | Answers your question from the assembly | – | Everyday use |
| Command: Stats (assembly statistics) | Counts and summarises what the assembly contains | – | Quick size and shape check |
| Command: Diff (compare two versions) | Compares a "before" and an "after" assembly and reports the API changes | – | Before you upgrade |
| Query | Your question (Chat only) | empty | Name the type or task: "how do I merge two PDFs?" |
| NuGet Package / NuGet Version | Fetches a package from nuget.org instead of an upload | blank | Leave the version empty for the latest |
| After NuGet Package / Version | The second assembly for a Diff | blank | The version you plan to move to |
| Include Internal | Also reads internal members | off | Only for libraries you own |
| AI Comments | During a scan, asks the AI to write comments for members | off | Only if the library has few doc comments (verify the effect on the live app) |
A chat answer can come with alternatives: other candidate answers you can click to re-answer the same question with a different primary match.
What you get
- Scan: several files, including UML diagram sources (
.puml) and CSV tables of types and members. SVG renders are produced only when the worker is asked for them (verify on the live app whether the page offers this). - Chat: the answer as markdown text in the chat pane, with code samples and, when you ask, diagrams.
- Stats: a text report and a PDF of it.
- Diff: a markdown report, a PDF of the report, and diagram files for the changes.
Quality & limits
AI-generated, but grounded in the signatures it actually read. It can still misjudge which method you meant, so treat code samples as a strong first draft and compile them. Only the public surface is known: the AI cannot tell you what a method does internally beyond its doc comments. What is sent to a model: your question and the matching API excerpts go to the language-model service Documentize uses; the assembly itself is read by the app's own scanner. The page says extracted metadata is kept only temporarily for your session and not used to train models.
Works well with
- Before: NuGet Updater tells you what is out of date; Assembly Chat tells you what the new version changes.
- After: Repo Docs for documenting your own code.
- Related: Trust, verification and limits of AI output.
Common mistakes & fixes
- "No DLL was uploaded and no NuGet package specified" → give one of the two.
- "Diff needs a second DLL" → upload two files, or fill in the "After" package.
- Query is empty → Chat needs a question.
- Answer mentions a type you cannot see → you may have scanned a different version; check the version field.
Same thing elsewhere
Not verified for this app. See channels for what exists for other apps.
Try it
Choose Scan, type Newtonsoft.Json as the NuGet Package and leave the version empty. When the scan finishes, switch to Chat and ask: "How do I serialize an object to a JSON string?" Then run Diff with two versions of the same package and read the report's list of changed members.