>Failure adding assembly to the cache: Strong name signature could not be verified. Was the >assembly built delay-signed? ... >Can anyone suggest a good reference for gacutil.exe, or explain what's going on?
It turns out there is a workaround for this. I'm not sure the System.Windows.Forms assembly will function under Rotor but I was incorrect in stating that you couldn't make this happen. Jan pointed out that the sn utility allows you to completely re-sign an assembly which removes both the public and private keys and replaces them with the new ones. So the following process would allow you to install the System.Windows.Forms.dll in the Rotor GAC. Make a copy of System.Windows.Forms.dll somewhere. This is one-way process because you don't have the Microsoft private key so you can't restore the file to the original key signing. Use the following command to completely re-sign the assembly with the Rotor key pair: sn -R System.Windows.Forms.dll <yourpath>\sscli\clr\bin\RotorKeyPair.snk Now you can install this modified but fully signed assembly in the Rotor GAC: gacutil /i System.Windows.Forms.dll Loading .NET assemblies into Rotor has a high probability of failure since the Rotor execution environment doesn't support critical functionality like COM interop which will most likely cause major problems. John This posting is provided "AS IS" with no warranties, and confers no rights.
