Pact Foundation

var config = new PactConfig
{
    PactDir = @"c:\contractDemoNew\pacts",
    Outputters = new[]
    {
        new XunitOutput(output)
    },
    DefaultJsonSettings = new JsonSerializerOptions
    {
        PropertyNamingPolicy = JsonNamingPolicy.CamelCase,
        PropertyNameCaseInsensitive = true,
        Converters = { new JsonStringEnumConverter() }
    },
    LogLevel = PactLogLevel.Debug
};

Hey <@U07BS9F7J95> , this is better suited for <#C9UTHV2AD|> I guess.

And no, I don’t think you can. It doesn’t really matter, because publishing the contract is better suited to be a step that is separated from running tests.

To make things easier, there’s <https://github.com/pact-foundation/pact_broker-client|https://github.com/pact-foundation/pact_broker-client> for local and CI use

Hi <@U01FVES2ECA>: I have a <app://dd/dashboard/images/local/details?tag=latest&amp;name=dius%2Fpact-broker|radius/pact-broker> running on the local machine (Docker). I can push the pact with the API . I am using Pact NET 4X. and Do I need to setup <https://github.com/pact-foundation/pact_broker-client|pact_broker-client> as well?  with Pact-Net 2X there was a way to publish it like :
var pactPublisher = new PactPublisher("http://&lt;YOUR_BROKER&gt;.<http://pactflow.io|pactflow.io>",
 new PactUriOptions("&lt;TOKEN&gt;"));
 pactPublisher.PublishToBroker("/pact/to/pacts/dir",
Environment.GetEnvironmentVariable("GIT_COMMIT"));

Is this not available or can be done by <https://github.com/pact-foundation/pact_broker-client|pact_broker-client> only?

I don’t know. I wasn’t aware that this class existed in older versions. If it’s not there in Pact .Net 4.x the change logs will probably tell you if and why it was removed.

I’ve not seen any examples using `PactPublisher` that I can remember.

We recommend using the pact CLI tools for this job.

We made a decision a few years ago to not support all of the CLI functions in each language because it's just added maintenance work