Just curious, but is it normal policy to distribute a key file with source code? Lucene.Net is a library in source code form. When I compile it for use in my apps, I just use my own key.
What's to keep someone from making changes to the source and then still signing it as George / Lucene.Net? Or, worse, use the key file to sign other assemblies/applications? If Lucene.Net was a DLL to download precompiled, I would understand wanting it signed. Just wondering what everyone thought... -----Original Message----- From: Marco Dissel (JIRA) [mailto:[EMAIL PROTECTED] Sent: Thursday, October 05, 2006 3:26 PM To: [email protected] Subject: [jira] Created: (LUCENENET-20) sign the assembly with a strong name sign the assembly with a strong name ------------------------------------ Key: LUCENENET-20 URL: http://issues.apache.org/jira/browse/LUCENENET-20 Project: Lucene.Net Issue Type: New Feature Environment: N/A Reporter: Marco Dissel Priority: Trivial I want to give my assemblies a strong name, but they have a reference to the Lucene assembly. And you can't give an assembly a strong name if it has references to assemblies with no strong name I assume more users have the same problem.... use sn -k <keyfile.snk> AssemblyInfo.cs: using System.Reflection; [assembly: AssemblyDelaySign(false)] [assembly: AssemblyKeyFile("<keyfiled.snk>")] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
