MSBuild Weekly Report — 2026-04-07

[github-actions[bot]]

Report Generated: 2026-04-07
Time Window: Past 14 days (2026-03-24 to 2026-04-07)

Quick Stats

• New unassigned issues: 1
• Older unassigned issues with recent activity: 6
• Active pull requests: 45

---

Section 1 — New Unassigned Issues (created in the past 14 days)

#	Author	Title	Category	Age (days)	Labels	Possible Reason	Suggested Next Steps
#13487	baronfel	MSBuild ITaskItem/TaskItem should be able to report an IElementLocation or similar to aid diagnostics	Feature Request	4	Area: Debuggability, User Experience, untriaged	ITaskItem instances passed to tasks don't carry location information, making diagnostic reporting imprecise when tracing problems with malformed items (e.g., PackageVersion, PackageReferences).	Needs triage; consider adding Location property to ITaskItem interface; needs design discussion for API surface; good candidate for team discussion on implementation approach.

---

Section 2 — Older Unassigned Issues with Recent Activity (created > 14 days ago, comment in past 14 days)

#	Author	Title	Category	Created	Latest Comment Summary	Possible Reason	Suggested Next Steps
#13441	YuliiaKovalova	Refactor ToolTask output synchronization to use System.Threading.Channels	Refactoring	2026-03-23	No recent comments (labeled event on 2026-03-24)	ToolTask uses complex lock/queue + ManualResetEvent pattern for stdout/stderr synchronization. Modernizing to System.Threading.Channels would improve maintainability and reduce concurrency complexity. Suggested in PR #13351.	Already triaged and in backlog; needs volunteer to implement; ensure regression tests (timeouts, hangs) pass; may need hybrid approach if full async becomes invasive.
#13403	Youssef1313	Fix importance check for target-skipped messages	Bug	2026-03-17	Youssef1313 reported they had to comment out asserts in integration tests, reducing regression detection confidence. Discussion about impact.	Regression from PR #12431 that was closed. Importance check for target-skipped messages is broken, affecting test reliability.	Reopen PR #12431 or create new fix; affects downstream test infrastructure; Priority:2 label indicates importance; needs team review and merge.
#13373	AR-May	Tests that use TaskEnvironmentHelper should test tasks with both environments	Documentation	2026-03-12	No recent comments (labeled event on 2026-03-24)	Tests using TaskEnvironmentHelper.CreateForTest() only test multiprocess environment, leaving gaps in multithreaded behavior validation.	Update existing tests to cover both MP and MT environments; ensure output correctness by moving current directory to temp path for MT tests; candidate for good-first-issue.
#13203	rainersigwald	Crash loading task with unresolved .NET property type from ExtensionEngine.dll	Bug	2026-02-04	No recent comments (label assignment on 2026-04-01)	MSBuild crashes (NullReferenceException in ReflectableTaskPropertyInfo) when loading tasks with properties of types from missing dependency assemblies (e.g., VSSDK tasks missing ExtensionEngine.dll). Exception handling leaves null in list.	Priority:2 and internal-team-onboarding label; needs null-check fix in TaskFactoryWrapper.PopulatePropertyInfo(); gracefully skip unresolvable property types; add regression test; repro requires Canary VS.
#10416	AR-May	[Feature Request]: Make Exec task support new progress messages	Feature Request	2024-07-19	selcukgural noted that aspnetcore PR #62273 surfaces OpenAPI paths via Message Importance=high, but Terminal Logger doesn't show high-importance messages at default verbosity, awaiting this fix.	Exec task doesn't support new progress messages API (#10415). Users want CustomProgressRegularExpression similar to error/warning regex parameters.	Needs design discussion; related to Terminal Logger verbosity handling; upstream dependency for aspnetcore improvements; candidate for team discussion on API design.
#4077	samsnowy	Can't attach custom build logger to Visual Studio for MSBuild	Question	2019-01-15	Community discussion about workarounds and VS integration (latest relevant comment in past 14 days unclear from label activity)	No documented way to attach custom MSBuild loggers to Visual Studio builds; users resort to hacks like overriding Build target.	Milestone: Discussion; needs VS team input; consider adding documentation or VS integration feature; long-standing community request; may need cross-team coordination with Visual Studio.

---

Section 3 — Open Pull Requests Triage (opened, or with commits/comments in past 14 days)

#	Title	Author	Action Needed By	Status Summary	Age (days)	Reviewers
#13497	Fix race condition in LoggingService.ProcessLoggingEvent after shutdo…	SimaTian	Team	Needs review; fixes NullReferenceException in LoggingService after shutdown.	<1	None assigned
#13496	Add PATs rotation to agentic workflow(s)	JanKrivanek	Team	Needs review; adds PAT rotation to avoid rate-limiting in agentic workflows.	<1	None assigned
#13495	Migrate GetReferenceAssemblyPaths task to TaskEnvironment API	OvesN	Team	Needs review; part of TaskEnvironment API migration effort.	<1	None assigned
#13493	Fix cross-AppDomain TaskItem modifier cache regression	DustinCampbell	Team	Needs review; fixes ~200MB allocation regression in VS .NET Framework scenarios.	1	None assigned
#13492	Remove duplicate @ prefix from issueAuthor in GitOps	akoeplinger	Team	Needs review; small fix to GitOps workflow.	1	None assigned
#13491	Fix copy-paste error in SdkResult equality check	Copilot	Team	Needs review; bug fix in SdkResult.	1	None assigned
#13489	Stabilize ToolTaskThatTimeoutAndRetry test	rainersigwald	Team	Needs review; test stabilization.	1	None assigned
#13488	issues/790 - Refactor error handeling to be more streamline	cubabuco	Team	Needs review; error handling refactor.	1	None assigned
#13486	Reenable Microsoft.CodeAnalysis.PublicApiAnalyzers	rainersigwald	Team	Needs review; re-enables public API analyzer.	4	None assigned
#13482	Migrate to xunit.v3	Youssef1313	Team	Needs review; major test framework migration.	6	None assigned
#13480	Fix TerminalLogger assert failure for metaproj files and cached project eval ID	OvesN	Team	Needs review; TerminalLogger bug fix.	6	None assigned
#13479	Copy task: make ERROR_ACCESS_DENIED fail-fast Windows-only to fix non-Windows retry resilience	Copilot	Team	Needs review; cross-platform Copy task fix.	6	None assigned
#13477	Fix race condition in WriteLinesToFile transactional mode (#13323)	huulinhnguyen-dev	Team	Needs review; race condition fix.	6	None assigned
#13475	Avoid allocations in GetHashCode implementations	DustinCampbell	Team	Needs review; performance optimization.	7	None assigned
#13474	Do not overwrite GetCopyToOutputDirectoryItemsDependsOn, just add new…	snechaev	Team	Needs review; build targets refactor.	7	None assigned
#13472	Bump main to 18.7, add vs18.6 to merge flow	MichalPavlik	Team	Needs review; version bump and merge flow update.	7	None assigned
#13469	Localized file check-in by OneLocBuild Task	dotnet-bot	Team	Automated localization PR; needs merge.	7	None assigned
#13467	Localized file check-in by OneLocBuild Task	dotnet-bot	Team	Automated localization PR; needs merge.	7	None assigned
#13458	Fix unresolved P2P references losing Configuration in solution builds	jimpark	Team	Needs review; P2P reference bug fix for solution builds.	11	None assigned
#13457	Migrate SGen task to Task environment API	OvesN	Team	Needs review; TaskEnvironment API migration.	11	None assigned
#13442	Add static fields guidance to /mt spec	AR-May	Team	Needs review; documentation update for /mt spec.	15	None assigned
#13437	Localized file check-in by OneLocBuild Task	dotnet-bot	Team	Automated localization PR; updated 2026-04-02.	15	None assigned
#13435	[main] Update dependencies from dotnet/roslyn	dotnet-maestro[bot]	Team	Automated dependency update; updated 2026-04-06.	15	None assigned
#13434	[main] Update dependencies from dotnet/arcade	dotnet-maestro[bot]	Team	Automated dependency update; updated 2026-04-06.	15	None assigned
#13433	[vs18.0] Update dependencies from dotnet/arcade	dotnet-maestro[bot]	Team	Automated dependency update; updated 2026-04-06.	15	None assigned
#13432	[main] Update dependencies from nuget/nuget.client	dotnet-maestro[bot]	Team	Automated dependency update; updated 2026-04-06.	15	None assigned
#13429	Exit worker nodes on Ctrl+C / Restart Manager shutdown (#12776)	sachinsharma3191	Team	Needs review; last updated 2026-03-24.	17	None assigned
#13428	Use Microsoft.IO.Redist in Framework FileUtilities/NativeMethods on net472 (#13078)	sachinsharma3191	Team	Needs review; updated 2026-04-06.	17	None assigned
#13427	Move core ProjectReferenceTargets from Managed-only to Common targets	dfederm	Team	Needs review; updated 2026-04-07; moves ProjectReferenceTargets protocol to all project types.	17	None assigned
#13426	Performance optimizations for EscapingUtilities	DustinCampbell	Team	Needs review; last updated 2026-04-01.	18	None assigned
#13424	Migrate AspNetCompiler to TaskEnvironment API	OvesN	Team	Needs review; last updated 2026-03-30.	18	None assigned
#13423	Migrate ToolTask and Al task to TaskEnvironment API	OvesN	Team	Needs review; updated 2026-04-02; core TaskEnvironment migration.	18	None assigned
#13411	[automated] Merge branch 'vs18.5' => 'main'	github-actions[bot]	Team	Automated branch merge; updated 2026-03-31.	20	None assigned
#13360	Update SDK pins to 10.0.300-preview.26159.114	Copilot	Team	Needs review; updated 2026-04-06; SDK version update.	28	None assigned
#13350	Stage 3: Forward BuildProjectFile* callbacks from OOP TaskHost to worker node	JanProvaznik	Team	Needs review; updated 2026-04-02; Stage 3 of OOP work.	29	None assigned
#13342	[vs18.3] Update dependencies from dotnet/arcade	dotnet-maestro[bot]	Team	Automated dependency update; updated 2026-04-06.	29	None assigned
#13319	Enlighten RAR task	AR-May	Team	Needs review; last updated 2026-03-26; RAR task enhancements.	35	None assigned
#13227	[vs17.12] Update dependencies from dotnet/arcade	dotnet-maestro[bot]	Team	Automated dependency update; updated 2026-04-06.	57	None assigned
#13226	[vs17.14] Update dependencies from dotnet/arcade	dotnet-maestro[bot]	Team	Automated dependency update; updated 2026-04-06.	57	None assigned
#13215	Migrate MSBuild tests from xUnit v2 to xUnit v3	Copilot	Team	Needs review; updated 2026-04-02; test framework migration (duplicate of #13482?).	60	None assigned
#13214	Exclude documentation and .github from CI triggers	Copilot	Team	Needs review; updated 2026-04-06; CI optimization.	60	None assigned
#13058	Fix ASP.NET WebSite projects to copy netstandard.dll facade when required	JanProvaznik	Team	Needs review; updated 2026-04-07; ASP.NET WebSite project fix.	78	None assigned
#12946	Fill holes in BuildEventContext construction and evaluation ID propagation	baronfel	Team	Needs review; updated 2026-04-01; BuildEventContext improvements.	113	None assigned
#12655	Make SdkResolver-provided environment variables take precedence over ambient environment	Copilot	Team	Needs review; updated 2026-04-06; SdkResolver environment variable precedence.	173	None assigned
#12587	separate the tracking parts of TL into a reusable base, so that TL becomes a 'renderer'	baronfel	Team	Needs review; updated 2026-04-06; TerminalLogger refactoring.	188	None assigned

---

🔍 Issues Flagged for Deeper Investigation

#	Title	Category	Reason for Investigation
#13403	Fix importance check for target-skipped messages	Bug	Regression affecting test infrastructure; importance check broken; Priority:2.
#13203	Crash loading task with unresolved .NET property type from ExtensionEngine.dll	Bug	NullReferenceException crash when loading tasks with missing dependency assemblies; Priority:2.

---

🧪 Investigation Results

Investigation results will be added here as they complete.

AI generated by MSBuild Weekly Activity Report

• expires on Apr 14, 2026, 12:08 PM UTC

[github-actions[bot]]

🔍 Investigation: Issue #13403 — Fix importance check for target-skipped messages

Upstream: dotnet/msbuild#13403
Classification: Bug / Regression (confidence: 0.95)
Reproduction: ⚠️ Inconclusive (environment limitations prevented full reproduction)

Summary

This is a logic error in a comparison operator introduced by PR #12226 that causes target-skipped messages to be logged incorrectly. The bug stems from a misunderstanding of the MessageImportance enum's numeric ordering: High=0, Normal=1, Low=2 (lower numeric value = higher importance), but the code uses > when it should use <=.

Root Cause Analysis

The Bug: In src/Build/BackEnd/Components/RequestBuilder/TargetEntry.cs (line ~370), the code checks:

if (projectLoggingContext.LoggingService.MinimumRequiredMessageImportance > MessageImportance.Low &&
    !projectLoggingContext.LoggingService.OnlyLogCriticalEvents)

Why This Is Wrong:

• MessageImportance enum values: High=0, Normal=1, Low=2
• MessageImportance.Low has the highest numeric value (2)
• The condition X > MessageImportance.Low can never be true for any valid MessageImportance value
• This causes the subsequent code block (which expands condition strings for logging) to never execute

The Fix (from PR #12431):
PR #12431 proposed a proper fix by:

1. Reversing the comparison logic using an extension method IsAtLeast()
2. The method correctly implements: importance <= requiredImportance (since lower numeric values = higher importance)
3. Moving MessageImportance to its own file for clarity

Impact:

• Target-skipped messages with false conditions are not properly expanded/logged
• Integration tests in downstream projects (like microsoft/testfx) had to disable assertions
• Reduced confidence in build log output for diagnostic purposes

Why PR #12431 Was Closed:
According to @rainersigwald's comment, "VS would consider it a regression so we need a deeper solution." The fix itself appears correct but may have downstream compatibility concerns with Visual Studio that require additional investigation.

Reproduction Details

Attempted Reproduction:
Created a minimal .NET project with:

• A target with a false condition: Condition="'$(NonExistentProperty)' == 'ExpectedValue'"
• Build with diagnostic verbosity to observe target-skip logging

Environment Issue:
Encountered permission restrictions preventing dotnet command execution in the test environment. However, the bug is clearly visible in the source code and the logic error is straightforward to verify through static analysis.

Code Evidence:
The buggy line still exists in the current main branch:

src/Build/BackEnd/Components/RequestBuilder/TargetEntry.cs:
  if (projectLoggingContext.LoggingService.MinimumRequiredMessageImportance > MessageImportance.Low && ...)

Suggested Next Steps

1. Reopen and merge PR #12431 (or create a new PR with the same fix) — the technical solution is correct
2. Investigate VS compatibility concerns — Work with Visual Studio team to understand what "regression" was detected and whether it's a legitimate concern or a false positive
3. Add unit tests — Ensure the comparison logic is covered by tests that verify messages are logged at appropriate verbosity levels
4. Consider enum refactoring — The numeric ordering of MessageImportance (lower=higher) is counterintuitive; consider using explicit integer values or adding code comments to prevent future confusion
5. Audit similar comparisons — Search the codebase for other instances of > MessageImportance.Low or similar patterns that may have the same bug

Priority Justification:

• Labeled as Priority:2 and Area: Performance
• Affects build logging and diagnostic capabilities
• Low immediate impact (integration test workarounds exist) but reduces overall system reliability
• Clean fix already exists, just needs resolution of VS compatibility concerns

---

Automated investigation by MSBuild Weekly Report workflow

Generated by MSBuild Issue Investigation — Worker Agent

[github-actions[bot]]

🔍 Investigation: Issue #13203 — Crash loading task with unresolved .NET property type from ExtensionEngine.dll

Upstream: dotnet/msbuild#13203
Classification: Bug (confidence: 0.95)
Reproduction: ⚠️ Inconclusive (environment constraints prevented full reproduction attempt)

Summary

MSBuild crashes with a NullReferenceException when loading a task that has a property with a type defined in a missing dependency assembly. The crash occurs in ReflectableTaskPropertyInfo constructor during task property inspection. Instead of gracefully handling the missing type, exception-handling logic leaves a null value in the property list, causing a subsequent crash when MSBuild attempts to check for required attributes.

Root Cause Analysis

Based on stack trace and source code analysis:

Crash Location: Microsoft.Build.Execution.ReflectableTaskPropertyInfo..ctor(TaskPropertyInfo taskPropertyInfo, Type taskType)

Affected Component: Task loading and reflection system in MSBuild's task execution host

Likely Root Cause:

1. When PopulatePropertyInfo() in TaskFactoryWrapper.cs (line 280) creates ReflectableTaskPropertyInfo objects for non-IGeneratedTask tasks, it wraps each TaskPropertyInfo to enable reflection-based property access
2. If a task property has a type from a missing dependency DLL (e.g., PkgDefManagementFlags from ExtensionEngine.dll), the reflection operation to resolve the property type fails
3. The exception handling doesn't properly skip or mark the failed property - instead it leaves a null in the property collection
4. Later, when GetNamesOfPropertiesWithRequiredAttribute() iterates the properties to check for [Required] attributes, it encounters the null reference and crashes

Evidence from source code:

• TaskFactoryWrapper.cs:280 - Creates ReflectableTaskPropertyInfo without visible null-checking
• The stack trace shows failure path: PopulatePropertyInfo → LazyInitValue → GetNamesOfPropertiesWithRequiredAttribute → SetTaskParameters
• The exception message explicitly states "exception-handling logic leaves a null in a list"

Impact: Any custom MSBuild task with properties referencing types from non-deployed assemblies will cause MSBuild to crash rather than gracefully report an error.

Reproduction Details

Unable to complete full reproduction due to environment execution constraints.

Reproduction Requirements:

• Visual Studio Canary channel build (issue mentions internal bug requiring Canary VS)
• VSSDK package Microsoft.VisualStudio.Sdk.BuildTasks.17.0.dll (canary version)
• Scenario where Microsoft.VisualStudio.ExtensionEngine.dll is not present alongside the task assembly

Minimal reproduction approach (not executed):

1. Create a custom MSBuild task with a property of type defined in a separate assembly
2. Reference the task assembly without deploying the type dependency
3. Build a project that loads (but doesn't necessarily use) the task
4. Expected: MSBuild crashes with NullReferenceException in ReflectableTaskPropertyInfo

Suggested Next Steps

1. Fix the null handling - Add null-checking in PopulatePropertyInfo() or ReflectableTaskPropertyInfo constructor to gracefully skip properties with unresolvable types
2. Improve error messaging - When a property type can't be loaded, log a clear warning identifying the property name, task, and missing dependency rather than crashing
3. Add defensive coding - Ensure GetNamesOfPropertiesWithRequiredAttribute() and related methods handle nulls in property collections
4. Add regression test - Create a unit test with a mock task having an unresolvable property type to prevent future regressions
5. Consider broader fix - Review all task property reflection code paths for similar null-handling issues

Priority: This is labeled Priority:2 and affects the VSSDK team. Given it's a crash (not graceful error), it should be prioritized for the next release.

---

Automated investigation by MSBuild Weekly Report workflow

Generated by MSBuild Issue Investigation — Worker Agent

[github-actions[bot]]

🧪 Investigation Results Summary

Summary: Investigated 2 issue(s) — 0 reproduced, 0 not reproduced, 2 inconclusive

#	Title	Classification	Reproduced?	Summary	Details
#13403	Fix importance check for target-skipped messages	Bug / Regression	⚠️ Inconclusive	Logic error in comparison operator causes target-skipped messages to be logged incorrectly. The bug stems from misunderstanding MessageImportance enum ordering where the condition can never be true.	View details
#13203	Crash loading task with unresolved .NET property type from ExtensionEngine.dll	Bug	⚠️ Inconclusive	MSBuild crashes with NullReferenceException when loading a task with a property type from a missing dependency assembly. Exception handling leaves null in property list causing crash instead of graceful error.	View details

---

Investigation summary generated automatically. See individual comments above for full details.

Generated by MSBuild Investigation Summary

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-04-14T12:08:34.611Z.

Closed by Workflow