 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / Component Services / April 2007Unable to emit assembly: Referenced assembly does not have a stron
"Unable to emit assembly: Referenced assembly 'Interop.FAXCOMEXLib' does not have a strong name" I have a COM+ application built using vb.net, it has several components, all of which are native components inherited from System.EnterpriseServices.ServicedComponent, this application is signed by a strong name it is registered by regsvcs32 and its up and running fine. now I am trying to add faxing capabilities to this application using Microsoft Interop.FAXCOMEXLib.dll (fxcomex.dll) the problem is that my COM+ application doesnt build now, it fails with an error message : Unable to emit assembly: Referenced assembly 'Interop.FAXCOMEXLib' does not have a strong name i've tried the tlbimp.exe command but it fails with an error message: TlbImp error: Unable to locate input type library: 'C:\tarasol\TarasolEngine\bin \interop.faxcomex.dll\' seems its trying to locate tlb file to successfully sign the interop assemble but such tlb doesn't exist anywhere have anyone tried this before ? is there a solution to add the fxcomex.dll to a COM+ application and get it successfully built Thanx in advance, > i've tried the tlbimp.exe command but it fails with an error message: > [quoted text clipped - 7 lines] > have anyone tried this before ? is there a solution to add the fxcomex.dll > to a COM+ application and get it successfully built Is "fxcomex.dll" a COM object? If so, you'll need to generate the interop assembly yourself using tlbimp.exe and the /keyfile switch. If you just reference a COM object from the VS.NET IDE, it generates an interop wrapper, but doesn't use the /keyfile switch so it is not signed. Locate "fxcomex.dll" on your hard drive, then create the wrapper assembly with tlbimp tlbimp.exe fxcomex.dll /keyfile:mykey.snk /out:interop.faxcomex.dll Then add a reference to interop.faxcomex.dll.  SignaturePatrick Steele http://weblogs.asp.net/psteele Many thanks. that worked out fine >In article <F988EB45-424A-4845-872F-719D9525175C@microsoft.com>, FASHA@discussions.microsoft.com says... > i've tried the tlbimp.exe command but it fails with an error message: > [quoted text clipped - 7 lines] > have anyone tried this before ? is there a solution to add the fxcomex.dll > to a COM+ application and get it successfully built Is "fxcomex.dll" a COM object? If so, you'll need to generate the interop assembly yourself using tlbimp.exe and the /keyfile switch. If you just reference a COM object from the VS.NET IDE, it generates an interop wrapper, but doesn't use the /keyfile switch so it is not signed. Locate "fxcomex.dll" on your hard drive, then create the wrapper assembly with tlbimp tlbimp.exe fxcomex.dll /keyfile:mykey.snk /out:interop.faxcomex.dll Then add a reference to interop.faxcomex.dll. SignaturePatrick Steele http://weblogs.asp.net/psteele _________________________________________________ Hello!How are you? I'm a chinese student. Can you give me a faxcomex.dll? I can't find it in my OS. Regards and thanks. my email:xingtaisen@126.com my msn:xingtaisen@126.com Can you give me a faxcomex.dll? ___ Newsgroups brought to you courtesy of www.dotnetjohn.com Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.