title: .NET OpenSource projects and strong named assemblies?
body: <p>I am currently thinking about open-sourcing a project of mine and am in the process of preparing the source code and project structure to be released to the public. Now I got one question: how should I handle the signature key for my assemblies? Should I create a new key for the open-source version and publish it along with the other files to the SVN repository? Should I leave the key out and everyone who wants to compile the code should generate his own key?</p>
  
  <p>How do you handle this? I feel a little bit uncomfortable with releasing a signature key to the public.</p>