`dotnet test` fails when native assets are required and multiple RuntimeIdentifiers are set

[conniey]

There are several related questions/issues to this (ie. #1017), so this might be more of a guidance question.

Our ApiPort tests use ilasm to compile IL files and verify that our MetadataReader is working correctly. (ex. Microsoft.Fx.Portability.MetadataReader.Tests.csproj.

It currently only works on .NET 4.6, but we want to be able to run this test on Linux as well to make sure our MetadataReader works on all platforms.

What is the solution here?

When I set: <RuntimeIdentifiers>win7-x86;linux-x64</RuntimeIdentifiers>, all tests when running against both .NET 4.6 and .NETCoreApp2.1 because ildasm cannot be located (since it is not copied to the OuputDirectory).

[livarcocc]

I am not sure I follow how this is an issue of the tooling platform. ildasm is not available cross-plat, as far as I am aware, which means that that part of your build will not work cross-plat. What would you expect the tooling to do here to help your scenario?

[conniey]

I apologise for the typo, I meant ilasm. Looking at the targets file, it appears like there are versions that run on Linux?

[livarcocc]

I am not sure what targets you are referring to. I don't believe we have those targets in the SDK itself.

[conniey]

IL.targets Line 11 is what i'm referring to.

I guess the behaviour is confusing. If I use:

<TargetFramework>net46</TargetFramework>
<RuntimeIdentifier>win7-x86</RuntimeIdentifier>

and run dotnet test, my tests pass because ilasm.exe is output in the folder under bin/Debug/net46/win7-x86. However, if I replace it with:

<TargetFramework>netcoreapp2.1</TargetFramework>
<RuntimeIdentifier>osx-x64</RuntimeIdentifier>

when I run dotnet test, the tests fail because ilasm is not in the output folder under bin/Debug/netcoreapp2.1/osx-x64. I have to run dotnet publish --framework netcoreapp2.1 before the native assets get copied to the output folder and I can see ilasm in there. At that point, I'm not sure how to leverage dotnet test.

[livarcocc]

I would file an issue on buildtools for this. I don't think this has anything to do with the SDK or the CLI.

It is possible that the package you are using to bring ilasm does not have assets for netcoreapp and only for .net framework.

[conniey]

ilasm runs on my Mac when I run dotnet publish --framework netcoreapp2.1.

I'll file it there. Thanks