lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Digy (JIRA)" <>
Subject [jira] Closed: (LUCENENET-20) sign the assembly with a strong name
Date Sat, 15 Nov 2008 00:54:48 GMT


Digy closed LUCENENET-20.

    Resolution: Won't Fix
      Assignee: Digy

Instead of using a compiled(dll) version of,  compile the source code with "sing
the assembly" option.

> sign the assembly with a strong name
> ------------------------------------
>                 Key: LUCENENET-20
>                 URL:
>             Project: Lucene.Net
>          Issue Type: New Feature
>         Environment: N/A
>            Reporter: Marco Dissel
>            Assignee: Digy
>            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
> 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.
You can reply to this email to add a comment to the issue online.

View raw message