Expose InMemoryTransportFactory as a public API

[arontsang]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

Unit Testing AspNetCore, run unit tests without creating a socket. Which would likely make it harder to run concurrent tests on a CI server.

Describe the solution you'd like

Being able to run AspNetCore Kestrel completely in memory.

Additional context

No response

[davidfowl]

You can unit test ASP.NET Core without the in memory transport being public. Do you have an example of what you want to test?

[arontsang]

@davidfowl I am trying to write a Kestrel ConnectionHandler. Specifically, I want to write a Proxy Protocol v1 handler (Asp Lab's example only supports v2), additionally, there are no unit tests around the handlers.

…

On Sun, 27 Mar 2022 at 02:29, David Fowler ***@***.***> wrote: You can unit test ASP.NET Core without the in memory transport being public. Do you have an example of what you want to test? — Reply to this email directly, view it on GitHub <#40893 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA46MLL4ULUJYYNMUYWWGPLVB5JO7ANCNFSM5RXNOWSA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[davidfowl]

Perfect, that was the missing data here. Thanks for the clarification.

[halter73]

We've talked about using Kestrel to implement TestServer before to make certain behaviors and features more consistent between tests and real applications. #11598

We could do this and provide a way to access the raw client IDuplexPipe.

[adityamandaleeka]

Triage: this seems like something that would have very limited use cases, so it's hard to justify the effort of designing and providing the real API surface for this.

Moving to backlog. If there's an increase in demand we may consider it in the future.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.