nunit-console and nunit-agent to support longPathAware

[poklau]

It looks like NUnit console does not support tests with file path exceed MAX_PATH as per document here.

This should be as simple as making it long-path aware like this in app.manifest:

<application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings xmlns:ws2="http://schemas.microsoft.com/SMI/2016/WindowsSettings">
        <ws2:longPathAware>true</ws2:longPathAware>
    </windowsSettings>
</application>

[manfred-brands]

It depends. If all libraries use with oath can handle them. I don't know if .NET Framework was ever updated

[CharliePoole]

@OsirisTerje @manfred-brands @poklau
I could finish the PR by merging it into the correct branch but I don't feel confident enough about what this is doing.

If changing the manifest makes an application long-path-aware, that's great. If, as I suspect, it merely tells the runtime that we are long-path-aware, then we need to make sure that's true before changing the manifests. Can anyone shed light on this?

FWIW, I see this as similar to our Parallelizable attribute, which simply promises that the test can safely be parallelized but doesn't make it work in case it can't. :-)

[poklau]

@CharliePoole
I have a locally built binaries that using this for the last 6 months and it's been supporting long-path as expected so far.

Not sure how I can create a test to cover this.

[CharliePoole]

That's good enough for me. :-)

[CharliePoole]

Merging this into version4 failed, probably because it has gotten a bit out of date. As this is simple, I'll just redo it in both main and version4.

[CharliePoole]

@poklau Actually, the merge of your PR turns out to have failed for an unrelated reason: one of the dependencies in our myget feed no longer existed, having been automatically purged. I fixed it along with applying your changes.