The instructions in the README tell you to start the Static Web Apps CLI in the Visual Studio Code instructions, but they don't mention it in the Visual Studio 2022 instructions. Visual Studio 2022 will need the Static Web Apps CLI running, and you will need to access it on its proxy port if you try to work with authentication locally.
To get Visual Studio 2022 working with authentication locally I needed to:
Start the Static Web Apps CLI and leave it running: swa start http://localhost:5000
Access the app on port 4280 instead of 5000.
A more integrated solution was to:
Add "launchUrl": "http://localhost:4280/", to the launchSettings.json client profile.
Fix: I would like to see running the Static Web Apps CLI with Visual Studio 2022 addressed in the README or another solution implemented to get authentication working locally.
The instructions in the README tell you to start the Static Web Apps CLI in the Visual Studio Code instructions, but they don't mention it in the Visual Studio 2022 instructions. Visual Studio 2022 will need the Static Web Apps CLI running, and you will need to access it on its proxy port if you try to work with authentication locally.
To get Visual Studio 2022 working with authentication locally I needed to:
swa start http://localhost:5000
A more integrated solution was to:
"launchUrl": "http://localhost:4280/",
to the launchSettings.json client profile.swa start http://localhost:5000
in it.{ "commands": { "Tools": { "fileName": "cmd.exe", "workingDirectory": ".", "arguments": "/c StaticWebApp.cmd" } }, "-vs-binding": { "ProjectOpened": [ "Tools" ] } }
Fix: I would like to see running the Static Web Apps CLI with Visual Studio 2022 addressed in the README or another solution implemented to get authentication working locally.