Disable VS Code extension auto-restore by default#16658
Conversation
Changes the default value of the `aspire.enableAutoRestore` setting from `true` to `false` so the VS Code extension no longer runs `aspire restore` automatically. Users who want auto-restore can opt in via the setting. Fixes microsoft#16338 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 16658Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 16658" |
There was a problem hiding this comment.
Pull request overview
This PR changes the Aspire VS Code extension’s default behavior so it no longer automatically runs aspire restore on workspace open or when aspire.config.json changes, requiring users to explicitly opt in via the aspire.enableAutoRestore setting. This aligns the runtime default in code with the contributed configuration default, and mitigates restore/locked-file conflicts like those reported in #16338.
Changes:
- Flip the default fallback value for
getEnableAutoRestore()fromtruetofalse. - Update the VS Code contributed setting
aspire.enableAutoRestoredefault fromtruetofalse.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| extension/src/utils/settings.ts | Changes the code-level default fallback for enableAutoRestore to false. |
| extension/package.json | Updates the VS Code setting contribution default for aspire.enableAutoRestore to false. |
|
/backport to release/13.3 |
|
Started backporting to |
Description
Changes the default value of the
aspire.enableAutoRestoreVS Code extension setting fromtruetofalse. The extension will no longer automatically runaspire restorewhen the workspace opens or whenaspire.config.jsonchanges. Users who want this behavior can opt in via the setting.Fixes #16338
Checklist