Version Used: 2.8.0-beta2-62711-03
Steps to Reproduce:
We are trying to get the latest version of Roslyn consumed by corefx so that we can start using the compiler server for non-Windows builds. The problem seems to be that after updating to the latest version, we can't force the compiler to NOT strong-name sign the assemblies. In corefx we need this since we run some post-compilation tools on the dll and we manually sign the binaries after that. Here are the parameters we are passing in to the CSC task:
Expected Behavior: output assembly shouldn't be strong-name signed
Actual Behavior: assembly is strong name signed causing a build error when we try to sign it manually after running our tools.
This is currently blocking the adoption of roslyn into corefx so it would be appreciated if addressed soon. cc: @agocke @jaredpar
Version Used: 2.8.0-beta2-62711-03
Steps to Reproduce:
We are trying to get the latest version of Roslyn consumed by corefx so that we can start using the compiler server for non-Windows builds. The problem seems to be that after updating to the latest version, we can't force the compiler to NOT strong-name sign the assemblies. In corefx we need this since we run some post-compilation tools on the dll and we manually sign the binaries after that. Here are the parameters we are passing in to the CSC task:
Expected Behavior: output assembly shouldn't be strong-name signed
Actual Behavior: assembly is strong name signed causing a build error when we try to sign it manually after running our tools.
This is currently blocking the adoption of roslyn into corefx so it would be appreciated if addressed soon. cc: @agocke @jaredpar