Solved

Strong Name error building assembly

Posted on 2004-04-29
10
1,083 Views
Last Modified: 2012-06-27
I generated a strong name key file using the sn.exe tool, and assigned the key file to my VB.NET assembly.  But when I build the assembly I receive an error saying "Unable to emit assembly: Referenced assembly 'Interop.FooBar' does not have a strong name".  FooBar is a vendor COM component.  How can I get past this error?

0
Comment
Question by:d532335
[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
  • 4
  • 3
10 Comments
 
LVL 5

Expert Comment

by:tgannetts
ID: 10949725
The Interop assembly the IDE generates for the COM component is not strongly named. You need to generate an Interop assembly with a strong name:

You can use the tlbimp.exe utility to generate a strongly-named Interop assembly from the Foobar dll using a strong name key file you have generated:

From the Visual Studio command line prompt:

tlbimp FooBar.dll /keyfile:FooBar.snk /out:interop.foobar.dll /namespace:foobar

This should create a strongly-named interop assembly which you can reference instead of the one the IDE generates for you. This should get rid of your problem.

Hope this helps

Tom
0
 

Author Comment

by:d532335
ID: 10951324
When I used the tlbimp on the dll it gave me an error saying that it wasn't a valid type library.  I instead used the tlb file.  This appeared to work, but I received several errors all similar to the following


TlbImp warning: At least one of the arguments for '_IOraBindVariable.GetPersistentPointer' can not be marshaled by the runtime marshaler.  Such arguments will therefore be passed as a pointer and may require unsafe code to manipulate.


I am in the process of testing.  Thought I would get your opinion.
0
 

Author Comment

by:d532335
ID: 10977210
I have an ocx that I add as a reference, which creates an interop dll under the obj directory.  No problem up to now because I can run the tlbimp that you suggested.  But when I goto the Customize toolbox and add the same control so that I can drop it on my form, it creates another dll under the obj directory called AxInterop.XXX.dll.  Therfore now I have two Interop dlls created from the same ocx.  One is called AxInterop.xxx.dll and the other is called Interop.xxx.dll.  How do I give both of these a strong name?
0
Creating Instructional Tutorials  

For Any Use & On Any Platform

Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.

 

Author Comment

by:d532335
ID: 10977217
Since I have asked multiple question on this thread, I was going to increase the point value, which use to be obvious.  How do you add points to a question now?
0
 
LVL 96

Expert Comment

by:Bob Learned
ID: 11123175
Are you still having a problem with this?

Bob
0
 

Author Comment

by:d532335
ID: 11127079
Yes I never received any postings on my follow-up issue
0
 
LVL 96

Accepted Solution

by:
Bob Learned earned 500 total points
ID: 11127101
You only need the one interoperability library.  When you created the AxInterop library, it was similar to using tlbimp.  You should probably keep the AxInterop reference.

Bob
0
 
LVL 96

Expert Comment

by:Bob Learned
ID: 11177025
Did this help you?

Bob
0

Featured Post

Salesforce Made Easy to Use

On-screen guidance at the moment of need enables you & your employees to focus on the core, you can now boost your adoption rates swiftly and simply with one easy tool.

Question has a verified solution.

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

This tutorial demonstrates one way to create an application that runs without any Forms but still has a GUI presence via an Icon in the System Tray. The magic lies in Inheriting from the ApplicationContext Class and passing that to Application.Ru…
Calculating holidays and working days is a function that is often needed yet it is not one found within the Framework. This article presents one approach to building a working-day calculator for use in .NET.
Add bar graphs to Access queries using Unicode block characters. Graphs appear on every record in the color you want. Give life to numbers. Hopes this gives you ideas on visualizing your data in new ways ~ Create a calculated field in a query: …
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…

728 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