Revert .NET 10 custom code support for v5.959 hotfix

[lambrianmsft]

What & Why

Reverts .NET 10 custom code project support from the v5.959 hotfix line and keeps the restored unit coverage in the same PR so this can merge directly into hotfix/v5.959.

Why:

• Issue VS Code: Deployed logic app fails to open in the portal with prolonged loading and no content displayed. #9144 reports Azure-deployed Logic Apps workflows not loading after SQL + NuGet deployment.
• VSIX 5.273.0 is reported as known-good, and the strongest regression boundary is the .NET 10 custom code support change.
• The hotfix should restore the previous .NET 8 codeless NuGet conversion defaults while preserving later hotfix-era conflict resolutions.
• Restored/adapted tests keep the coverage gate strict instead of weakening PR coverage policy.
• PR coverage CI hit Node heap OOM while running the full VS Code extension unit suite with Istanbul coverage, so the coverage workflow now gives that step a larger Node heap without changing thresholds or exclusions.

Affected areas:

• apps/vs-code-designer: custom code function/project steps, code project base, codeful workflow creation, workflow switchToDotnetProject, debug/custom-code/dotnet/codeless utility tests, and reverted .NET 8 defaults/templates.
• apps/vs-code-react: create workspace .NET framework step tests and reverted .NET 8 framework UI behavior.
• .github/workflows/pr-coverage.yml: CI-only Node heap increase for the coverage test step to avoid VS Code extension coverage OOM.

Supersedes #9169, which was closed so this PR can carry both the revert and coverage fix directly into hotfix/v5.959.

Fixes #9144

Type of Change

• fix

Impact of Change

Users

• Restores prior .NET 8-based custom-code/codeless NuGet conversion behavior for the v5.959 hotfix line.
• Intended to unblock SQL + NuGet deployed Logic Apps workflows that fail to load in Azure Portal.

Developers

• Restores and adapts unit tests removed by the revert so changed-file coverage remains enforced.
• Keeps the hotfix branch reviewable as one PR: production revert plus corresponding coverage restoration.
• Makes the PR coverage workflow more stable for the existing full VS Code extension unit coverage run.

System

• Reverts .NET 10 workflow/template/default behavior back to the previously supported .NET 8 hotfix behavior.
• No coverage-threshold changes, coverage exclusions, runtime dependencies, or product runtime changes from the CI heap adjustment.

Risk Level

• Low

Risk notes:

• Low risk because this is a targeted hotfix revert to previously shipped behavior plus tests.
• The product change is scoped to VS Code custom-code/codeless NuGet conversion and workspace framework selection paths.
• The CI change only increases Node heap for the PR coverage test step and does not weaken validation.

Test Plan

• Updated/restored unit tests for the affected VS Code designer and VS Code React flows.
• Ran pnpm install --frozen-lockfile during the hotfix setup.
• Ran pnpm exec biome check --write <changed test files>.
• Ran targeted apps/vs-code-designer Vitest coverage: 12 files, 192 tests passed.
• Ran targeted apps/vs-code-react Vitest coverage: 2 files, 25 tests passed.
• Verified final changed-file coverage table: all target files are >= 80%.
• Ran pnpm run build:extension during the revert validation.
• PR Coverage Check rerun after CI heap adjustment.

Screenshots / Videos

Not applicable - VS Code hotfix revert, unit coverage restoration, and CI coverage stability update; no new UI surface.

Contributors

N/A

[github-actions]

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

• Current: Revert .NET 10 custom code support for v5.959 hotfix
• Issue: None — title is clear and indicates this is a revert/hotfix PR.
• Recommendation: Keep as-is. Optionally you can add the issue number in the title (e.g., Revert .NET 10 custom code support for v5.959 hotfix (fixes #9144)) to make the linkage more visible in lists.

---

✅ Commit Type

• Properly selected (fix).
• Note: Only one type selected which is correct for this change.

---

✅ Risk Level

• Risk label risk:low is present and matches the PR body selection.

---

✅ What & Why

• Current: The PR body clearly explains that it reverts .NET 10 custom code support from the v5.959 hotfix line, restores tests/coverage, and increases Node heap for CI coverage step to avoid OOM.
• Issue: None — the rationale is well-documented and links to the root issue (VS Code: Deployed logic app fails to open in the portal with prolonged loading and no content displayed. #9144) are present in the body.
• Recommendation: None required.

---

✅ Impact of Change

• The Impact section is thorough and scoped (Users, Developers, System).
• Recommendation: None required.

---

✅ Test Plan

• The Test Plan is detailed and lists unit test runs, precise test counts, and build steps. It indicates test restoration and validation steps.
• Note: For non-revert PRs we would verify changed-file tests in the diff; since this is a revert PR the guidance allows immediate pass. Ensure CI succeeds on the final PR Coverage Check rerun after the CI heap adjustment step.

---

⚠️ Contributors

• Current: N/A in the PR body.
• Assessment: Optional but recommended. If others (PMs, designers, reviewers) contributed, consider adding them to the Contributors section for visibility/credit.

---

⚠️ Screenshots/Videos

• Current: Not applicable — this is a revert and unit/CI change with no UI surface changes.
• Assessment: Acceptable to leave blank.

---

Summary Table

Section	Status	Recommendation
Title	✅	Keep as-is; optionally include #9144 in title for visibility.
Commit Type	✅	No change needed.
Risk Level	✅	Label and body match (low).
What & Why	✅	No change needed.
Impact of Change	✅	No change needed.
Test Plan	✅	Ensure CI PR Coverage Check passes after heap adjustment.
Contributors	⚠️	Optional: add credits if applicable.
Screenshots/Videos	⚠️	Not applicable.

---

Final message
This PR is a revert; per the revert policy it is eligible to be approved immediately. The PR body and labels are well-formed and the declared risk (low) matches the label present on the PR. I recommend merging once the repo CI (including the PR Coverage Check rerun) completes successfully.

Suggested small improvements (optional):

• Add the issue number in the PR title for easier discovery (e.g., append (fixes #9144)).
• If anyone else contributed, add them to the Contributors section for credit.

Thank you — this PR can be merged after CI passes.

---

Last updated: Fri, 15 May 2026 02:57:45 GMT