Skip to content

Conversation

@pavelsavara
Copy link
Member

@pavelsavara pavelsavara commented Nov 22, 2021

My previous change writes file with <?xml version="1.0" encoding="utf-16"?> in otherwise UTF8 file.

@pavelsavara pavelsavara added the wasm WASM area label Nov 22, 2021
@pavelsavara pavelsavara requested a review from maraf November 22, 2021 11:59
@pavelsavara pavelsavara marked this pull request as ready for review November 22, 2021 14:24
@pavelsavara pavelsavara enabled auto-merge (squash) November 22, 2021 14:26
@radical
Copy link
Member

radical commented Nov 23, 2021

@pavelsavara if you build XHarness locally, then you can run runtime tests with XHARNESS_CLI_PATH=/path/to/xharness/artifacts/bin/Microsoft.DotNet.XHarness.CLI/Debug/net6.0/Microsoft.DotNet.XHarness.CLI.dll to run with your built XHarness, and catch any issues.

@pavelsavara
Copy link
Member Author

I know and I did, but I have not noticed the mismatch of xml header and actual encoding. @radical

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wasm WASM area

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants