Skip to content

[FlowLedger] Disable JIT tiering on Aspire service resources for debugger#16

Merged
JerrettDavis merged 1 commit into
masterfrom
fix/aspire-debugger-jit-vars
Jun 16, 2026
Merged

[FlowLedger] Disable JIT tiering on Aspire service resources for debugger#16
JerrettDavis merged 1 commit into
masterfrom
fix/aspire-debugger-jit-vars

Conversation

@JerrettDavis

Copy link
Copy Markdown
Owner

Sets DOTNET_TieredCompilation=0, DOTNET_ReadyToRun=0, DOTNET_TieredPGO=0 on all .NET project resources via ExecutionContext.IsRunMode guard.

Fixes CORDBG_E_IL_VAR_NOT_AVAILABLE (0x80131304) when debugging with Rider through Aspire — the CLR debugger cannot read locals/variables in ReadyToRun/tiered-compiled code. The IsRunMode guard ensures these vars are never injected during dotnet publish or CI.

…gger

Sets DOTNET_TieredCompilation=0, DOTNET_ReadyToRun=0, DOTNET_TieredPGO=0
on .NET project resources when ExecutionContext.IsRunMode is true.
Prevents CORDBG_E_IL_VAR_NOT_AVAILABLE (0x80131304) when debugging with
Rider/Aspire — the CLR debugger cannot read locals in R2R/tiered code.
Guard ensures the vars are never set during publish or CI.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@JerrettDavis JerrettDavis merged commit b5eab17 into master Jun 16, 2026
13 checks passed
@JerrettDavis JerrettDavis deleted the fix/aspire-debugger-jit-vars branch June 16, 2026 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant