When loading a LAMBDA project with a custom workingDirectory in launchSettings.json - the value is incorrectly changed

[Paul-Langille-Alludo-Com]

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

[awschristou]

Hi @Paul-Langille-Alludo-Com , thank you for reaching out.

I am able to reproduce this behavior. Right now, I don't know if this is deliberate or accidental behavior by the Toolkit. As a workaround, you can create your own entry in launchSettings.json file, calling it something other than "Mock Lambda Test Tool". This way you can debug using your own custom profile values, and you can use the "Mock Lambda Test Tool" as a reference in order to set it up.