-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SWA CLI and Visual Studio debugger does not connect in Visual Studio 17.8.6 #801
Comments
I confirmed this behavior is also present in Visual Studio 17.9. |
Just an update, this issue is still present in Visual Studio 17.9.7 when following the steps above. However, the good news is that this problem does not happen when running the SWA CLI within docker (with a Windows 11 host). I launch the docker container using the command:
and once it is started, I start SWA within the docker container using the command:
Using this I was able to run Visual Studio 17.9.7, with the nuget packages fully updated in the solution. |
Before filing this issue, please ensure you're using the latest CLI by running
swa --version
and comparing to the latest version on npm.Are you accessing the CLI from the default port
:4280
?:4280
ℹ️ NOTE: Make sure to enable debug logs when running any
swa
commands using--verbose=silly
Describe the bug
A clear and concise description of what the bug is.
The swa cli and Visual Studio debugger no longer connect to the Blazor static web app under Visual Studio 17.8.6.
Under Visual Studio 17.8.5 the swa cli will correctly launch and attach to the browser (in my case Microsoft Edge), however under Visual Studio 17.8.6 the browser launches however the swa cli fails to connect with a 'Failed to launch debug adapter' error (see screenshot below).
Note: When running with --verbose=silly the last message is
[swa] Connected to tcp:localhost:5000 successfully
with no further debug messages.To Reproduce
Steps to reproduce the behavior:
"launchUrl": "http://localhost:4280"
and changing applicationUrl to be"applicationUrl": "http://localhost:5000"
.The full launchSettings.json should look like:
{
"iisSettings": {
"windowsAuthentication": false,
"anonymousAuthentication": true,
"iisExpress": {
"applicationUrl": "http://localhost:42316",
"sslPort": 44363
}
},
"profiles": {
"BlazorBasic": {
"commandName": "Project",
"dotnetRunMessages": true,
"launchBrowser": true,
"launchUrl": "http://localhost:4280",
"inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}",
"applicationUrl": "http://localhost:5000",
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
}
},
"IIS Express": {
"commandName": "IISExpress",
"launchBrowser": true,
"inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}",
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
}
}
}
}
3. Start the swa cli with the command
swa start http://localhost:5000
.4. Launch the application in Visual Studio with debugging using the BlazorBasic profile.
Expected behavior
A clear and concise description of what you expected to happen.
The swa cli and Visual Studio debugger should connect and launch the Blazor static web app correctly as it did with Visual Studio 17.8.5.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: