aws / aws/aws-toolkit-visual-studio
When loading a LAMBDA project with a custom workingDirectory in launchSettings.json - the value is incorrectly changed
- Dominant language
- No language data
- Stars
- 135
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
When loading a LAMBDA project with a custom workingDirectory in launchSettings.json - the value is incorrectly changed - but ONLY if the AWS Toolkit is installed.
**To Reproduce**
1. Create a custom lambda project
2. Edit the workingDirectory value to use a different var (like $(OutputPath))
3. Save and close the project.
4. Close Visual Studio
5. Reopen Visual Studio and reopen the project
6. Open the launchSettings.json
7. The workingDirectory is set to a different value
**Expected behavior**
The workingDirectory should NOT be changed from the value set in step 2
**Development System (please complete the following information):**
- Windows Version: Windows 10
- Visual Studio Version: Visual Studio 2022
- AWS Toolkit for Visual Studio Version: Latest
Contributor guide
Research direction
Start by reproducing the behavior with a custom Lambda project and inspect launchSettings.json before and after closing and reopening Visual Studio. Trace which AWS Toolkit project-loading path changes workingDirectory, then verify that a value such as $(OutputPath) remains unchanged after reopening the project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100