Lib cannot be used in .NET7 projects about mockhttp HOT 3 CLOSED

Libraries compiled for .net 6 can be used in .net 7. I'll typically only target newer .net versions if there's a feature that's not available in earlier versions.

In the latest release I targetted:

• .net 5 because it added support for synchronous HttpClient methods that couldn't be mocked otherwise
• .net 6 because .net 5 has a limited support life

As for the issue you're experiencing, it's not entirely clear what the problem is or how you are using MockHttp - you show TCP tracing logs but the entire point of MockHttp is to stub requests without the need for actual network traffic.

Could you create a small, self-contained, project with a failing unit test so I can better understand the issue?

from mockhttp.

Hi,
I will attempt to provide the project you're requesting.
Logs I provided are the verbose output of vs2022 default test runner (Logging level: Trace (Includes Platform logs)). I tried to find some differences between v6 and v7. Tests are running in full autonomy and don't require network traffic.

from mockhttp.

I've validated .NET 7 compatibility by running the MockHttp unit tests while consuming the 7.0.0 NuGet package (rather than the local source project) and it all ran fine, so I don't think there should be any issues with .NET 7.

I'm going to close this ticket for now, but feel free to re-open it if you put together a minimal repro.

from mockhttp.