[release/7.0] Fixes not find assembly and pdb if it's not using the default path

[thaystg]

Customer Impact

Fixes #93016
When a customer is setting another path for the assets during the Blazor start the debugger is not working.

await Blazor.start({
    loadBootResource: function (type: string, name: string, defaultUri: string, integrity: string) {
        return `${defaultUri.replace("_framework", "assets/dotnet")}?${integrity}`;
    }
});

Testing

Manually tested.

Risk

Low. Only moving the try catch.

[ghost]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Fixes #93016

When a customer is setting another path for the assets during the Blazor start the debugger is not working.

await Blazor.start({
    loadBootResource: function (type: string, name: string, defaultUri: string, integrity: string) {
        return `${defaultUri.replace("_framework", "assets/dotnet")}?${integrity}`;
    }
});

Author:	thaystg
Assignees:	thaystg
Labels:	area-Debugger-mono
Milestone:	-

[dlemstra]

Wondering why ex is not passed as an argument to LogError? This might provide the user with more information?

[radical]

I think he meant https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.logging.loggerextensions.logerror?view=dotnet-plat-ext-7.0#microsoft-extensions-logging-loggerextensions-logerror(microsoft-extensions-logging-ilogger-system-exception-system-string-system-object()) . Does the error show up in VS? how?

[dlemstra]

That's what I meant. I would expect that to should up in the output of the console application that is being launched when running the debugger? Now also wondering if the e should also be passed to the logger.LogDebug method.

[radical]

ConfigureAwait(false)

[dlemstra]

And thanks for this quick fix thaystg. Happy that you could reproduce this error and find what was causing this so quickly. I am wondering if extra unit tests should be added for this?

[thaystg]

And thanks for this quick fix thaystg. Happy that you could reproduce this error and find what was causing this so quickly. I am wondering if extra unit tests should be added for this?

This is a scenario that has a different implementation for .net8, which doesn't matter the file url, I don't think we need unit tests for it.

[carlossanlop]

@thaystg has all feedback been addressed? If yes, can you please send an email to Tactics requesting approval?

[carlossanlop]

Approved by Tactics via email.