Solved

Create a Strong Name for Assembly

Posted on 2007-11-28
5
1,272 Views
Last Modified: 2013-11-26
I am having troubles with this error:
Unable to emit assembly: Referenced assembly 'CalendarLibrary' does not have a strong name.
I wasn't getting it while debugging before, but now that I tried to Publish, I'm getting it all the time.

A little background:
I'm using a CalendarLibrary.dll that was created from another project.  I put the CalendarLibrary.dll file in then bin/release folder of my current project and I'm referencing it there.  It works fine for debugging, but when I try to publish, I get the strong name error.

I've tried using - sn -k --.snk, created a keyfille, then tried tlbimp on CalendayLibrary.dll and it came up with an error saying CalendarLibrary.dll is not a valid type library.  (Also, no commands work in the command window of Visual Studio ???, so I'm doing this from the regular cmd prompt - I put the sn.exe, tblimp.exe, keyfile, and .dll all in the bin/release folder and running cmd prompt from that folder)

I've really been trying to solve this myself though looking at other solutions, msdn, etc. and I just can't figure it out.  If you have the info, please list step by step, 'cause I must be missing something.

Thanks
0
Comment
Question by:dreinmann
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 38

Accepted Solution

by:
PaulHews earned 500 total points
ID: 20366117
As you probably now know, any project that is signed cannot be dependent on assemblies that are not strong named.

To sign your CalendarLibrary, it's probably easiest to do it within Visual Studio.

Select your CalendarLibrary project in the Project Explorer and right click and select properties.

Click the "Signing" tab.

Check "Sign the assembly" box

In the key drop down, either select a previously generated key using browse or choose "<New...>"

Use Save All to ensure changes are saved.  Rebuild the project/solution.
0
 

Author Comment

by:dreinmann
ID: 20366336
Did that...makes sense.  But it won't let me Rebuld the Project.  A new error pops up:

The "GenerateResource" task failed unexpectedly.
System.Runtime.Serialization.SerializationException: Type 'CalendarLibrary.CalendarLibrary.CalendarItem' in Assembly 'CalendarLibrary, Version=1.0.0.0, Culture=neutral, PublicKeyToken=627e0898373e8271' is not marked as serializable.
   at Microsoft.Build.Shared.ExceptionHandling.RethrowUnlessFileIO(Exception e)
   at Microsoft.Build.Tasks.ProcessResourceFiles.ProcessFile(String inFile, String outFile)
   at Microsoft.Build.Tasks.ProcessResourceFiles.Run(TaskLoggingHelper log, ITaskItem[] assemblyFilesList, ArrayList inputs, ArrayList outputs, Boolean sourcePath, String language, String namespacename, String filename, String classname, Boolean publicClass)
   at Microsoft.Build.Tasks.GenerateResource.Execute()
   at Microsoft.Build.BuildEngine.TaskEngine.ExecuteTask(ExecutionMode howToExecuteTask, Hashtable projectItemsAvailableToTask, BuildPropertyGroup projectPropertiesAvailableToTask, Boolean& taskClassWasFound)      Demo

????
0
 
LVL 38

Expert Comment

by:PaulHews
ID: 20366486
It sounds like your application is supposed to serialize the class CalendarItem for remoting or xml or some other use.  You may have to mark it as serializable:

<Serializable()> _
Public Class CalendarItem  .... etc.
0
 

Author Comment

by:dreinmann
ID: 20366745
Actually, I went back to the original C# project (I was working on the one I converted to vb.net), signed it and rebuilt.  Recreated the CalendarLibrary.dll and put it in the bin/Release folder of the project I'm working on and I was able to Rebuild it successfully and Debug as well.  
But now a new error (I think I'm getting closer though):
SignTool reported an error 'Failed to sign bin\Release\Logistics Manager.publish\\setup.exe. SignTool Error: ISignedCode::Sign returned error: 0x80880253

      The signer's certificate is not valid for signing.

SignTool Error: An error occurred while attempting to sign: bin\Release\Logistics Manager.publish\\setup.exe

'.      LogisticsManager

What now...(by the way, you've answered my first question successfully, would you like me to award this question and start a new one for this new error?)
0
 

Author Comment

by:dreinmann
ID: 20367021
Got it!!  Had to do the 'install into Trusted Root Certificate' thing.

Thanks paulhews!
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In my previous two articles we discussed Binary Serialization (http://www.experts-exchange.com/A_4362.html) and XML Serialization (http://www.experts-exchange.com/A_4425.html). In this article we will try to know more about SOAP (Simple Object Acces…
It was really hard time for me to get the understanding of Delegates in C#. I went through many websites and articles but I found them very clumsy. After going through those sites, I noted down the points in a easy way so here I am sharing that unde…
In this video, viewers are given an introduction to using the Windows 10 Snipping Tool, how to quickly locate it when it's needed and also how make it always available with a single click of a mouse button, by pinning it to the Desktop Task Bar. Int…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question