Issue 73 in cassia: Cassia is not strong named

[cas...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 73 by j.n.webs...@gmail.com: Cassia is not strong named
http://code.google.com/p/cassia/issues/detail?id=73

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).


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[cas...@googlecode.com]

Updates:
Labels: -Type-Defect Type-Enhancement

Comment #1 on issue 73 by danports: Cassia is not strong named
http://code.google.com/p/cassia/issues/detail?id=73

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.