The following sequence:
 
1) load a strong-named assembly containing some utility classes and methods.
2) add some additional classes and methods.
3) write the assembly with a new strong name key pair loaded from embedded 
resource
- used snk -k to produce the SNK file, then added as embedded resource to 
project
- used the following code to write the assembly:
    byte[] snk = GetEmbeddedResource("sample.snk");
    assembly.Write("sample.dll",new WriterParameters{ StrongNameKeyPair=snk 
});
4) verifiy the assembly using "snk -vf sample.dll"
    reports that the file is valid
5) drag the assembly into the GAC folder
   ===> the given assembly name or codebase 'sample.dll', was invalid
 
Notes:
1) I'm able to load sample.dll into both ILSpy and Reflector without 
problems.
 
Questions:
1) How do I determine what the GAC is complaining about?
2) Is there another setting or method to avoid the problem?
3) Is this a known bug or something new?
 

-- 
--
mono-cecil

Reply via email to