fix(dotnet-perf): fix dialer bug affecting benchmark runs

[K-21]

Fix #829

Originally in Test Plans as #831

It extends the changes introduced #829

The original PR resolved a critical issue in the .NET performance benchmarking suite: although the listener multiaddr was correctly stored and fetched from Redis, it was never passed properly into the dialer logic, resulting in dialing attempts without any target address and causing benchmark failures (null/empty multiaddr exceptions).

In addition to preserving that fix, this extended description explains the scope of changes and why they matter:

Background & Root Cause

In the .NET performance benchmarks, the benchmarking flow includes:

• Storing the listener multiaddr (network address of the service) in a shared store (Redis).
• Retrieving that multiaddr when initiating a dialer (client) process.
• Dialing the listener from the benchmark runner to measure performance.

However, while the multiaddr was being stored and fetched correctly, it was not passed into the dialer initialization — leading to a failure at runtime where the dialing attempt had no valid multiaddr to connect to. Because the benchmark logic depended on this connection attempt succeeding, the entire benchmark run would throw exceptions and fail prematurely.

Enhacements

1. Correct multiaddr handling

• Properly validate the multiaddr retrieved from Redis before attempting a connection.
• Ensure that the valid multiaddr is correctly passed into the dialer initialization logic.
• Guarantees that no dial call occurs when the multiaddr is null or empty (protects against runtime exceptions).

2. Improved Dialer Initialization

• Updated initialization logic in Program.cs to include explicit checks and assignments.
• Ensures that the dialer receives the correct multiaddr up front, preventing misconfiguration and making the behavior deterministic.

3. Additional Safeguards and Resiliency

• Added defensive checks to fail early if the multiaddr format is invalid (e.g., not a valid libp2p multiaddr).
• Enhanced error output to make benchmark logs more useful when diagnosing failures (e.g., clear reasons for failed initialization).Updated initialization logic in Program.cs to include explicit checks and assignments.

[K-21]

@flcl42 @seetadev @dhuseby
This builds onhttps://github.com/libp2p/test-plans/pull/829 and addresses the dialer multiaddr issue — please review.

[dhuseby]

LGTM. I ran the perf test local with ./run.sh --impl-ignore !dotnet --force-image-rebuild --yes and it worked flawlessly. Thank you!