Cassia is not strong named

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Include Cassia in a strong-named project
2. Build the project

What is the expected result?
Successful build

What happens instead?
Visual Studio generates an error: 
"Assembly generation failed -- Referenced assembly 'Cassia' does not have a 
strong name"

What version of Cassia are you using (e.g. 2.0.0.60)?
2.0.0.60

On what Windows version is your code running?
Windows Server 2012 Standard, .NET Framework 4.5, Visual Studio Ultimate 2012 
Update 4

Is your code running as a Windows service, an ASP.NET application, or a
standalone application?
Standalone application

What Windows version is running on the remote server you are trying to
access (if any)?
n/a

Please provide any additional information below. If you are running into an
exception, please include a stack trace (at least the portion of it that
relates to Cassia).

Original issue reported on code.google.com by j.n.webs...@gmail.com on 12 Dec 2013 at 2:52

[GoogleCodeExporter]

I will consider this for a future release (seems like quite a debate in the 
.NET OSS world and I haven't needed a signed assembly myself), but for now you 
can work around this by building Cassia yourself and signing the assembly with 
your own key.

Original comment by danports on 16 Jan 2014 at 11:47

• Added labels: Type-Enhancement
• Removed labels: Type-Defect