Hi all! I'm using pact verify with pact-net inside my code... I know that is possible to use the command cli to perform the verify on the provider side and I follow the examples in pact-net github. However, in what situation is it better to use cli for this verification? Or for .net the recommendation is to use by code? Thanks a lot :)

I prefer to work in code, because you can properly stub things and you get more fine grained control. The CLI will work of course, but I find it less targeted and harder to get a reliable setup

Ok... @Matt (pactflow.io / pact-js / pact-go). About the setup, you mean about the provider states... Correct? Because, at this moment we are thinking to use the CLI to give the same guideline for all languages that use pact in our company. However, I cant find any example using verify CLI for .net solution... Do you have some idea how can we make it?

Not just provider states but that is part of it. It's harder to use mocks etc when running in a black box way. Why would we provide an example for using the .NET and cli when we have a proper language? The point of the CLI is to make it available to other languages that don't have this.

Ok, I understand... I saw some examples in other languages such as python (for example) and for us, it seems easier and fittable to use the command cli in pipelines. However, I will guide the teams to try to use .directly in code. Thanks again @Matt (pactflow.io / pact-js / pact-go)

I would go with whatever works best for your team Andre - you can always change later!

Great @Matt (pactflow.io / pact-js / pact-go), thank you again for all support. Honestly, this initial onboarding with the teams has not been easy but we are trying to follow with a standardized way as much as we can.

Feel free to brain dump on that onboarding experience here, so we can share and review as a maintainer community - appreciate your persistence!

Great!! I really trust in this solution 😉