Chris Maddock

Thanks Charlie. 🙂 > Seems slightly related to extension properties, which are currently readonly and used by the extension to tell the runner more specifically what it does. For example,...

@jnm2 - I think this has happened with the change to `contentFiles`. Any idea's how we might prevent this? I've had a dig, but not much luck. 😢 I think...

There's nothing in the logs to help here, unfortunately. Do you get anything additional logged when you run without `--inprocess` - other than the SocketException, of course?

You're right, there's no extra clues here. I'm afraid I'm really not sure what would cause this, perhaps others on @nunit/engine-team might have some ideas?

Nothing, it seems - see the top post. That's the bit that's confusing me! 🙂

Hi @DialLuesebrink, This wouldn't be possible as you've written it - the console needs to run against every version of the framework, rather than being locked down specifically to v3.13.1....

I have absolutely no idea why that would be - although I'm not much of an xslt user myself. Here's the code that does the transform. Any ideas? https://github.com/nunit/nunit-console/blob/master/src/NUnitEngine/nunit.engine/Services/ResultWriters/XmlTransformResultWriter.cs

Ok, this issue is caused by the fact that the XmlTransformResultWriter currently just gets the test-run XmlNode, rather than the XDocument. (Which I presume is different because it includes the...

I've thought about it. I think this needs to change. And be advertised as potentially breaking. I'll check if any of the nunit-transforms will break with this change when I...

I think the change should be made to the transforms either way - that sounds like an improvement to the transform as it is. 🙂 Charlie - I had a...