-
Notifications
You must be signed in to change notification settings - Fork 54
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
[Debugging] Breakpoint is only hit on the first load #307
Comments
That would probably be an issue with Blazor itself, I don't think there's anything that can be done about this within Bolero. That being said, there must be something specific to your situation, as I've definitely been able to break into my |
Do we need to create an issue in ASP.NET Core repo? |
@dim-37 confirmed the issue on his PC |
@Tarmil you miss "dotnetRunMessages": true,
"inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}", in @Tarmil will you accept a PR that generates {
"iisSettings": {
"windowsAuthentication": false,
"anonymousAuthentication": true,
"iisExpress": {
"applicationUrl": "http://localhost:18346",
"sslPort": 44372
}
},
"profiles": {
"HelloBolero.Server": {
"commandName": "Project",
"dotnetRunMessages": true,
"launchBrowser": true,
"inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}",
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
},
"applicationUrl": "https://localhost:4463;http://localhost:4466"
},
"IIS Express": {
"commandName": "IISExpress",
"launchBrowser": true,
"inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}",
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
}
}
}
} |
@Tarmil do you approve such PR? |
Sorry for the delayed response, but sure, go ahead and submit it! |
I created a project from the template and put breakpoints into
update
But only the breakpoint on line 100 is hit and only once.
Is it possible to fix this and make breakpoints always hittable?
The text was updated successfully, but these errors were encountered: