usecases.sh
usecases.sh
Software & DevOps

Build and start a legacy .NET Framework API from a Markdown runbook

Heriberto Flores wrote one Markdown runbook so Claude Code builds and launches his team's .NET Framework 4.8 Web API each morning, and Visual Studio no longer has to be opened.

Done with

What they did

Flores works on an old .NET Framework 4.8 codebase with non-SDK project files, large Web.config files, NHibernate and IIS Express, which normally only runs from inside Visual Studio. He listed the four jobs the IDE did for him: locate MSBuild, build the projects in order, put the local config in place, and start IIS Express on the right site and port. He spent an afternoon turning those into a Markdown file in the repo, written for Claude Code. The file tells the agent to check that the local config exists and to stop and ask rather than make up secrets, copy it into place, build in order, start IIS Express in the background, and poll a health endpoint until the API answers. A troubleshooting section at the end records the failures he hit. Each morning he asks Claude Code to start the admin Web API, and it follows the file.

How it went

He says Claude Code now checks the config, builds, starts IIS Express, polls the health check and reports the port, and when something fails it reads the log file the runbook names. He edits in VS Code and runs everything through Claude Code, and he says his team uses the same file. He gives no timings or counts.

Worth knowing

Visual Studio still has to be installed: vswhere finds MSBuild inside it, and IIS Express still reads the applicationhost.config Visual Studio generated. One trap he wrote into the runbook is that Git Bash rewrites IIS Express's /config: switch as a file path, so the server refuses to start.

Try it withClaude Code

Read [docs/run-locally.md] and follow it to get [the admin Web API] running on my machine. First check that [the local config file] exists; if it is missing, stop and ask me, and never invent secrets or connection strings. Copy it into place, find MSBuild with vswhere, build [the projects] in the order the doc gives, then start IIS Express in the background for [site name]. Poll [the health endpoint] until it answers or [two minutes] pass. If anything fails, read the log file the doc points to and tell me the cause before trying again. Stop when the API answers and tell me the port.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

All Software & DevOps use cases

Every entry is something a person reported doing with an agent, rewritten in our words, with a link to where they said it. Found across the web every hour; reviewed before it ships.

Maintained by an agent that uses One for every integration it touches.