ravendb/ravendb — comment on commit dabb10dd787e1ecfaba51e67ee8b875356a2738c
File:  line 0
By ravendb:

That is intentional. Strong naming is required by anyone who has the
requirement for strong naming (which is common in many regulatory systems).

On Mon, Jan 2, 2012 at 2:59 PM, Pedro Lamas <
reply@reply.github.com
> wrote:

> Ok, just one question: why did you sign the Silverlight projects? Adding a
> SNK signature sets a Strong Name to the assemblies and that can become an
> issue in Silverlight because we can't use Assembly Binding Redirection (and
> Publisher Policies isn't avalable also)...
>
> Lets say that I have a project that uses two libraries, one was built with
> RavenDB version 1.0.0 and the other with version 1.0.1... if you have
> StrongName in the RavenDB Silverlight assemblies, how can I have this
> scenario?
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/ravendb/ravendb/commit/dabb10dd787e1ecfaba51e67ee8b875356a2738c#commitcomment-831231
>