Error signing output with public key from file 'x.snk' -- Assembly signing not supported

I am moving a .net full project to .net standard 2.0 with a.netcore 2.0 unit test projects. They both use a snk to strongly sign the binaries.

<SignAssembly>True</SignAssembly><AssemblyOriginatorKeyFile>wol.snk</AssemblyOriginatorKeyFile>

When building the .net standard 2.0 project, i get:

CSC : error CS7027: Error signing output with public key from file 'wol.snk' -- Assembly signing not supported. [.../Source/proj/projA/projA.csproj]

Any idea?

Environment data

dotnet --info output:

.NET Command Line Tools (2.0.0-preview1-005977)

Product Information:
 Version:            2.0.0-preview1-005977
 Commit SHA-1 hash:  414cab8a0b

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.12
 OS Platform: Darwin
 RID:         osx.10.12-x64
 Base Path:   /usr/local/share/dotnet/sdk/2.0.0-preview1-005977/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0-preview1-002111-00
  Build    : 1ff021936263d492539399688f46fd3827169983

[nguerrera]

@Jonathan34 Excellent question. There are consequences. Public signing is like delay signing: only the public key is needed and the binary is not actually signed with the private key. The only difference is a bit in the PE that allows most scenarios to run without registering for skip verification. However, since the binary is not actually fully signed, it cannot be installed to the GAC, cannot be used with shadow copying, and cannot be loaded in a partial trust context on full framework.

See https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/public-signing.md

There are plans to support full signing on non-Windows (dotnet/roslyn#8210), but the work has not been completed.

[RehanSaeed]

Since https://github.com/dotnet/roslyn/issues/8210 is now completed, I assume this works now?