Description
When opening my Azure Functions project in VS Code, I receive the warning:
The targetFramework "net8.0" in your project file does not match the targetFramework ".net" in your VS Code config.
However, when I click "Update VS Code config", it modifies my .vscode/settings.json incorrectly by altering the azureFunctions.deploySubpath value.
Specifically, it appears to incorrectly parse part of my folder name (which contains Planet.) as a framework value and injects net8.0 into the path.
This results in a broken path.
Expected Behavior
Clicking "Update VS Code config" should:
Either correctly update framework-related config (if needed), OR
Leave unrelated settings (like deploySubpath) untouched
Actual Behavior
It modifies azureFunctions.deploySubpath incorrectly.
Before clicking "Update VS Code config":
"azureFunctions.deploySubpath": "Planet.Corr.TpoFieldSync"
After clicking:
"azureFunctions.deploySubpath": "Planet8.0Corr.TpoFieldSync"
Notice how:
Planet. becomes Planet8.0
This breaks the directory path completely
Additional Context / Observations
My project correctly targets:
net8.0
The issue seems to be caused by:
A string parsing bug
The extension likely scanning for .net and replacing it incorrectly
It falsely matches part of the folder name (Planet.*) as a framework token
This happens consistently when clicking the auto-fix button
Repro Steps
Create or open a project with:
TargetFramework = net8.0
Folder name containing .something (e.g. Planet.Corr.TpoFieldSync)
Open in VS Code
Trigger the warning about mismatched targetFramework
Click "Update VS Code config"
Observe .vscode/settings.json being incorrectly modified
Impact
Breaks deployment path
Causes failed Azure Functions deployments
Misleading warning + destructive auto-fix
Environment
VS Code: (fill in from Issue Reporter)
Azure Functions Extension: (auto-filled)
OS: (auto-filled)