'msbuild' 검색 결과

Diagnose MSBuild failures from an existing binary build log. Inspect errors, settings, project references, and execution details to explain failures that console output alone does not clarify, including failures across multiple projects.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating build errors with unclear console output
• Tracing cascading failures across multiple projects
• Checking MSBuild target execution order

Analyze MSBuild binary logs and timing summaries to find why builds are slow. Identify costly reference resolution, code analysis, file copying, restore work, or serialized tasks, then prioritize improvements by their share of total build time.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate unexplained MSBuild slowness
• Measure code analysis and source generator overhead
• Find expensive reference resolution or file copying

Configure and troubleshoot custom build logic in MSBuild. Check hooks, import order, control properties, and NuGet package layouts to explain why extension files are missing, skipped, or replaced, including paths for specific target frameworks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating MSBuild extensions that fail to load
• Controlling the order of imported extension files
• Checking NuGet build extension package layouts

Diagnose why MSBuild builds across multiple projects fail to run efficiently in parallel. Use build logs and project dependencies to identify blocking chains, then recommend changes to references, scheduling, or parallel execution settings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate builds that do not get faster with -m
• Identify project dependency chains that delay builds
• Review whether graph builds fit a solution

Investigate MSBuild failures, measure slow builds, or review existing build definitions. Use binary logs, project settings, and comparable timing measurements to identify causes, propose focused repairs, and verify behavior without broad configuration changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating build failures from binary logs
• Measuring bottlenecks and comparing build times
• Finding why unchanged projects rebuild

Write and repair custom MSBuild targets, the steps that organize build tasks. Preserve existing build sequences, choose appropriate insertion points, distinguish returned results from rebuild checks, and register generated files for cleanup.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add custom steps to an existing build sequence
• Repair dependency settings that replace SDK build steps
• Correct stale results returned by query targets

Diagnose slow MSBuild startup by measuring project evaluation, the work done before compilation. Inspect logs for costly file searches, imported configuration, and repeated evaluations, then identify targeted changes supported by timing evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating delays before compilation starts
• Checking file searches across large directories
• Analyzing deep import chains

Choose when MSBuild copies files to build or publish folders. The skill explains settings that avoid unnecessary copies, restore output files changed by tests or apps, and apply shared copy behavior across existing projects.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reducing unnecessary file copies on every build
• Restoring test databases changed between builds
• Choosing copy settings for configuration files

Capture MSBuild execution records as binary logs during .NET builds, tests, packaging, publishing, or restores. It explains unique filenames, PowerShell quoting, and file checks so logs remain available for later failure or performance analysis.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Saving logs before investigating a build failure
• Keeping separate logs for Debug and Release builds
• Choosing log filenames for CI artifact uploads

Review MSBuild project files and build definitions for correctness and maintainability. Get prioritized findings with concrete recommendations, distinguishing confirmed defects from conditional risks and valid exceptions such as F# source ordering or required imports.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing build files for maintainability
• Checking path portability across operating systems
• Reviewing import safety and required-file assumptions

Integrate files generated during MSBuild into compilation or build output. Address missing generated source and content by choosing target timing, using the configured intermediate directory, and registering files so Clean can remove them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Including generated .cs files in compilation
• Copying generated configuration or data files to output
• Fixing file patterns that miss files created during a build

Establish repeatable performance measurements for MSBuild and .NET builds before optimizing. Compare clean-output, changed-source, and unchanged builds, record timing ranges, and assess output layouts, dependency references, and parallel build options against the measured baseline.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Measure slow builds before choosing an optimization
• Compare build times before and after changes
• Check rebuild behavior after a small source edit

Diagnose and fix MSBuild property problems, including overwritten settings, ineffective conditions, and environment-dependent paths. Review defaults, list appending, and evaluation order so project files and shared build settings retain the intended values.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fix build settings overwritten by shared files
• Preserve existing compilation constants when adding new ones
• Correct conditions based on the target framework

Diagnose unnecessary rebuilds in MSBuild by examining build logs, file timestamps, and declared inputs and outputs. Identify why work repeats, guide fixes when requested, and verify that a second unchanged build skips the expected targets.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating rebuilds when no files changed
• Reviewing inputs and outputs on custom targets
• Checking generated files and cleanup behavior

Review and fix how MSBuild manages lists of files and their metadata, or attached information. Check Include, Remove, Update, filtering, path transformations, duplicates, and execution grouping to clarify whether item operations behave as intended.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing Include, Remove, and Update usage
• Investigating duplicate or overlapping file entries
• Checking metadata-based execution grouping

Interpret MSBuild performance summaries when ResolveProjectReferences appears unusually expensive. Separate time spent waiting for dependent projects from actual task work, then use task self-time rankings to identify a concrete optimization target.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating a high ResolveProjectReferences time
• Separating dependency wait time from task work
• Finding the actual bottleneck in a build log

Investigate MSBuild failures caused by projects or build configurations writing to the same output folders. Compare build logs, output paths, and project settings to identify collisions behind overwritten files, restore errors, or failures that disappear on retry.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate file access errors during parallel builds
• Find shared intermediate folders causing NuGet restore errors
• Check output paths when building for multiple frameworks

Analyze MSBuild binary logs to diagnose build failures. Only activate in MSBuild/.NET build context. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, and generally any MSBuild build issues. Requires an existing .binlog file. DO NOT USE FOR: generating binlogs (use binlog-generation), non-MSBuild build systems. INVOKES: binlog MCP server tools (overview, errors, search, items, properties); falls back to dotnet msbuild binlog replay + grep/cat when the MCP is unavailable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnose why the dotnet-msbuild binlog MCP server will not start or connect. Check the selected SDK, package sources, and launch logs, then identify a recovery that respects organizational policies and verify that the host discovers the server’s tools.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating CONNECTION_CLOSED during server startup
• Checking SDK selection and package source settings
• Diagnosing Microsoft.AITools.BinlogMcp resolution failures

Canonical patterns for writing custom MSBuild targets. Only activate in MSBuild/.NET build context. USE FOR: diagnosing and fixing custom target authoring anti-patterns, reviewing MSBuild target definitions for correctness, diagnosing broken SDK target chains across files (e.g., Directory.Build.targets silently redefining SDK targets), fixing targets that replace CompileDependsOn instead of extending it with $(CompileDependsOn), fixing query targets that return stale results due to Outputs vs Returns misuse, fixing missing Inputs/Outputs causing unnecessary rebuilds, fixing missing FileWrites registration. Covers DependsOnTargets vs BeforeTargets vs AfterTargets, the Build→CoreBuild three-level pattern, hooking into the build pipeline, the $(XxxDependsOn) chain-extension pattern. DO NOT USE FOR: incremental build tuning (use incremental-build), parallelization (use build-parallelism), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MSBuild property definition patterns: conditional defaults, composition/concatenation, path normalization, trailing slash handling, TFM detection helpers, and property evaluation order. Only activate in MSBuild/.NET build context. USE FOR: diagnosing and fixing MSBuild property definition issues in .props or .csproj files, reviewing and fixing shared property configuration anti-patterns, fixing DefineConstants or NoWarn being overwritten instead of appended, fixing unconditional property assignments that prevent project-level overrides, fixing unquoted conditions that fail when properties are empty, fixing hardcoded paths that break cross-platform builds, setting property defaults that can be overridden, understanding property evaluation order and last-write-wins semantics. DO NOT USE FOR: props vs targets placement (use directory-build-organization), item operations (use item-management), target structure (use target-authoring), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Catalog of MSBuild anti-patterns with detection rules and fix recipes. Only activate in MSBuild/.NET build context. USE FOR: reviewing, auditing, or cleaning up .csproj, .vbproj, .fsproj, .props, .targets, or .proj files. Each anti-pattern has a symptom, explanation, and concrete BAD→GOOD transformation. Covers Exec-instead-of-built-in-task, unquoted conditions, hardcoded paths, restating SDK defaults, scattered package versions, and more. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake, etc.), project migration to SDK-style (use msbuild-modernization).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide for MSBuild extensibility: CustomBefore/CustomAfter hooks, wildcard imports with alphabetic ordering, import gating with control properties, NuGet package build extension layout (build/buildTransitive), and the MicrosoftCommonPropsHasBeenImported guard. Only activate in MSBuild/.NET build context. USE FOR: diagnosing and fixing MSBuild import and hook patterns, reviewing and fixing extension point anti-patterns in Directory.Build files, fixing missing Exists() guards on imports that break fresh clones, fixing NuGet package hooks being silently dropped instead of appended, making build targets extensible for other projects, injecting custom logic into the build pipeline, creating NuGet packages that extend the build, conditionally disabling imports. DO NOT USE FOR: target authoring patterns (use target-authoring), props vs targets placement (use directory-build-organization), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide for diagnosing and improving MSBuild project evaluation performance. Only activate in MSBuild/.NET build context. USE FOR: builds slow before any compilation starts, high evaluation time in binlog analysis, expensive glob patterns walking large directories (node_modules, .git, bin/obj), deep import chains (>20 levels), preprocessed output >10K lines indicating heavy evaluation, property functions with file I/O ($([System.IO.File]::ReadAllText(...))), multiple evaluations per project. Covers the 5 MSBuild evaluation phases, glob optimization via DefaultItemExcludes, import chain analysis with /pp preprocessing. DO NOT USE FOR: compilation-time slowness (use build-perf-diagnostics), incremental build issues (use incremental-build), non-MSBuild build systems. INVOKES: binlog MCP server tools (evaluations, evaluation_global_properties, evaluation_properties, imports, properties); falls back to dotnet msbuild -pp:full.xml for preprocessing, /clp:PerformanceSummary.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.