You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Digy (JIRA)" <ji...@apache.org> on 2008/11/15 01:54:48 UTC
[jira] Closed: (LUCENENET-20) sign the assembly with a strong name
[ https://issues.apache.org/jira/browse/LUCENENET-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Digy closed LUCENENET-20.
-------------------------
Resolution: Won't Fix
Assignee: Digy
Instead of using a compiled(dll) version of Lucene.net, compile the source code with "sing the assembly" option.
> sign the assembly with a strong name
> ------------------------------------
>
> Key: LUCENENET-20
> URL: https://issues.apache.org/jira/browse/LUCENENET-20
> 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 name
> 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.