Guide for using MSBuild Server to improve CLI build performance. Only activate in MSBuild/.NET build context. Activate when developers report slow incremental builds from the command line, or when CLI builds are noticeably slower than IDE builds. Covers MSBUILDUSESERVER=1 environment variable for persistent server-based caching. Do not activate for IDE-based builds (Visual Studio already uses a long-lived process).
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmsbuild-serverExecute the skills CLI command in your project's root directory to begin installation:
Fetches msbuild-server from dotnet/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate msbuild-server. Access via /msbuild-server in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
2.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
2.6K
stars
| name | msbuild-server |
| description | "Guide for using MSBuild Server to improve CLI build performance. Only activate in MSBuild/.NET build context. Activate when developers report slow incremental builds from the command line, or when CLI builds are noticeably slower than IDE builds. Covers MSBUILDUSESERVER=1 environment variable for persistent server-based caching. Do not activate for IDE-based builds (Visual Studio already uses a long-lived process)." |
| license | MIT |
Use the MSBuild Server to cache evaluation results across CLI builds, matching the performance advantage Visual Studio gets from its long-lived MSBuild process.
dotnet build) are slower than expected| Input | Required | Description |
|---|---|---|
| Shell context | No | The shell where the environment variable will be set (bash, PowerShell, or Windows persistent) |
Verify the developer is building from the command line (dotnet build), not from Visual Studio or another IDE. The MSBuild Server provides no benefit inside an IDE.
# Bash / CI
export MSBUILDUSESERVER=1
# PowerShell
$env:MSBUILDUSESERVER = "1"
# Windows (persistent)
setx MSBUILDUSESERVER 1
Run two sequential builds of the same project and compare times:
dotnet build -- server starts, no cache benefitdotnet build -- should be noticeably fasterThe most noticeable improvement is in repos with many projects or complex Directory.Build.props chains.
MSBUILDUSESERVER=1 is set in the shelldotnet build-server shutdown followed by a rebuild confirms the server restarts cleanly| Pitfall | Solution |
|---|---|
| Expecting improvement in Visual Studio | VS already uses long-lived MSBuild nodes; the server adds no benefit |
| Build correctness issues after enabling | Run dotnet build-server shutdown to reset; if issues persist, disable the server |
| Server process using unexpected memory | The server persists in background; shut down with dotnet build-server shutdown when idle |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
dotnet/skills
dotnet/skills
dotnet/skills
dotnet/skills
dotnet/skills
dotnet/skills
msbuild-server has been reliable in day-to-day use. Documentation quality is above average for community skills.
msbuild-server fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for msbuild-server matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: msbuild-server is focused, and the summary matches what you get after install.
msbuild-server reduced setup friction for our internal harness; good balance of opinion and flexibility.
msbuild-server reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend msbuild-server for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
msbuild-server reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: msbuild-server is the kind of skill you can hand to a new teammate without a long onboarding doc.
msbuild-server fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 58