devexpress-wpf-dependency-injection

Read this file to the end before acting: the order of the steps is what makes the migration safe, and skipped steps are the ones that break the app at startup.

Step 1 — Inspect

In a git working tree, first record which files already have uncommitted changes: run the check script with -Baseline (see "Running the scripts"). Line endings are later restored only in the files you change.

Count the project's .cs and .xaml files (Glob, excluding bin/obj).

• Up to 40 files: inspect yourself per references/detection.md — you will read these files to edit them anyway.
• More, or several projects: spawn inspect (see Subagent protocol) and afterwards open only the files you are going to change. Without a sub-agent dispatch tool, inspect yourself per detection.md whatever the size: search with the patterns it lists first, then read only the files the hits point to.

Either way the result is the same list: DevExpress version and package, target framework, any existing container or host, and every place a view model, view or service is created, classified per detection.md.

Step 2 — Choose the wiring

Apply references/wiring.md to the inspection facts. It decides:

• built-in IocServiceProvider + {dxmvvm:Ioc} or a custom markup extension (by DevExpress version and package);
• extend an existing container, or create one — never a second one;
• Generic Host or plain ServiceCollection.

State the choice and the fact behind each part in one or two lines.

Step 3 — Plan

List every creation site from Step 1 with what it becomes, and every registration with its lifetime from references/lifetimes.md. Show the list and continue with Step 4 in the same turn, unless the user asked to review the plan before any change. The host's own approval of file edits and commands still applies. Stop only for a question the code cannot answer, one at a time, with a structured question tool if available. If nobody can answer (unattended run), take the default from lifetimes.md, say so, and continue.