Adam Rodger

The linked PR fixes the issues on Windows, but is writing unreadable chars on Linux, so not sure what's happening there.

Yeah this is a problem in the FFI rather than PactNet itself. It'll need a tracking issue

Currently .Net Framework is only supported on Windows, hence the unconditional copy in the targets file that you've found. I've marked the issue as a feature request if Mono support...

There are no plans to do this at present, no. I'm not sure how the JS one works because the Pact Spec doesn't say anything about XML support either.

The test cases may mention XML but it doesn't appear anywhere in the spec. I imagine that's why it doesn't have wider adoption, as the spec only ever mentions JSON...

@mefellows this looks like it could be an issue with the FFI

From the library perspective I'd want the FFI to return a non-zero status code so I could throw an exception like we do with a few other error cases. Then...

The current error handling from the verifier FFI is here, where any non zero response would fail the verifier run: https://github.com/pact-foundation/pact-net/blob/master/src%2FPactNet%2FVerifier%2FInteropVerifierProvider.cs#L236 If "unable to publish results" had its own error...

I've reopened but this requires an FFI change, not a PactNet change.

Thanks for the report 👍 I'll check out whether the problem is happening in PactNet itself or whether it's after we've passed to the FFI library. If it's the latter,...