Fix logging config and output redirection in DebugProxy

[captainsafia]

• Set base path to current directory for ConfigurationBuilder in DebugProxyHost
• Redirect output from DebugProxy to console
• Enable verbose and protocol logs in MonoProxy

Here's are examples of output from the DebugProxy when running the StandaloneApp with the following blazor-debugproxysettings.json in the project root.

{
  "Logging": {
    "LogLevel": {
      "Default": "Debug"
    }
  }
}

Addresses #22134

[SteveSandersonMS]

Looks great!

In the case of a hosted project, should the config go in the client project or the server one? I guess it’s the server because there could be any number of client projects but only one instance of the debugging middleware. Is that right?

[SteveSandersonMS]

Oh also, is it worth patching MonoProxy.cs to enable output for verbose log entries? We can get this fixed in the upstream repo (Mono) later but that may take longer than doing it ourselves in the aspnet repo.

[captainsafia]

I guess it’s the server because there could be any number of client projects but only one instance of the debugging middleware. Is that right?

Yes, for a server project it would go under the root of MyProject.Server.

Oh also, is it worth patching MonoProxy.cs to enable output for verbose log entries? We can get this fixed in the upstream repo (Mono) later but that may take longer than doing it ourselves in the aspnet repo.

Done. I went ahead and enabled protocol logs as well.

[mkArtakMSFT]

@pranavkm there seems to be some Pipeline Configuration Error here:

Pipeline configuration error:
Could not retrieve file content for /.azure/pipelines/helix-matrix.yml from repository self hosted on https://github.com/ using commit c426d2a0b5aa326ead307286ee3fce38e01f24e6. GitHub reported the error, "Internal Server Error"

Was there an intentional change to break this?

[pranavkm]

Internal Server Error sounds like an issue with GitHub. We also haven't been using helix in the 3.1 / blazor-wasm branch.

[captainsafia]

@pranavkm @mkArtakMSFT I think we can sensibly ignore this one. It showed up on Friday when GitHub was having a service degradation. That build doesn't seem to be a part of the checks that we do on blazor-wasm. I think it was incorrectly added while GitHub was being wonky and is stuck in that state now.

Are folks cool with merging this?

[pranavkm]

Are folks cool with merging this?

Sure, let's get this in.