Skip to content

Conversation

@thaystg
Copy link
Member

@thaystg thaystg commented Oct 14, 2020

When it's using embedded PDBs it will not have pdb files, but it is still possible to debug, removing the check of existence of PDB files.

Addresses #26877

@thaystg thaystg requested a review from captainsafia October 14, 2020 19:16
@thaystg thaystg requested review from a team and SteveSandersonMS as code owners October 14, 2020 19:16
@ghost ghost added the area-blazor Includes: Blazor, Razor Components label Oct 14, 2020
@thaystg thaystg changed the title Fix debug using embedded PDBs. [wasm][debugger] Fix debug using embedded PDBs. Oct 14, 2020

export function hasDebuggingEnabled() {
return hasReferencedPdbs && currentBrowserIsChrome;
return currentBrowserIsChrome;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah! I see why this would be the root cause of the user reported issue.

However, this is check is too liberal now and we'll end up running with debugging enabled if the user is running a publish app (which doesn't add any PDBs to the blazor.boot.json).

We'll probably need a more conservative check that accounts for the environment the app is running in and other properties in the boot.json.

I can make these modifications on top of your PR.

Thanks for looking at this!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @captainsafia

@captainsafia
Copy link
Member

Closing in favor of #27107

Let me know what you think @thaystg!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-blazor Includes: Blazor, Razor Components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants