This message was deleted.
# wiremock-dotnet
s
This message was deleted.
o
I would rather create a single module that has two container definitions and some shared utility classes and interfaces where we can start generalizing the things
We don't have to commit to binary compatibility in the beginning, and I think this approach could provide us with an excellent boilerplate. With some luck and effort we could even end up in the compatibility layer that could be later detached into a separate library so that WireMock.NET could include it