|
Home > Archive > BizTalk Server Orchestration > June 2005 > Strong name: Problem with third-party DLL's
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Strong name: Problem with third-party DLL's
|
|
| nweddle 2005-06-21, 5:50 pm |
| I am using two DLL's from a third party vendor. I use these DLL's to make
calls to their API. I created a C# project and set the key info on the
AssemblyInfo.cs class. When I build, I get this error:
Assembly generation failed -- Referenced assembly 'iManMPDotNet' does not
have a strong name
So I have two questions:
1. Can I run a tool against the third-party DLL's to sign them?
I tried to use the AL.exe, but I do not know what I should pass as the
module name. I have a key pair, and I have the DLL, but I don't know what my
module is.
2. How can I use third-party DLL's in BizTalk that are not signed?
Thanks!
| |
| Jon Flanders[MVP] 2005-06-21, 5:50 pm |
| You have to use ILDASM on the assembly - then run ilasm on it after -
passing in the il and a key file
ILDASM /out:asm.il asm.dll
ILASM asm.il /KEY=key.snk /DLL /OUTPUT=asm.dll
--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/
"nweddle" <nweddle@discussions.microsoft.com> wrote in message
news:FE0E43D2-C5F2-413F-89FC-5632EEF32663@microsoft.com...
>I am using two DLL's from a third party vendor. I use these DLL's to make
> calls to their API. I created a C# project and set the key info on the
> AssemblyInfo.cs class. When I build, I get this error:
>
> Assembly generation failed -- Referenced assembly 'iManMPDotNet' does not
> have a strong name
>
> So I have two questions:
> 1. Can I run a tool against the third-party DLL's to sign them?
>
> I tried to use the AL.exe, but I do not know what I should pass as the
> module name. I have a key pair, and I have the DLL, but I don't know what
> my
> module is.
>
> 2. How can I use third-party DLL's in BizTalk that are not signed?
>
> Thanks!
| |
| nweddle 2005-06-21, 5:50 pm |
| Thanks for the response Jon! Before I read your post, I used the ILMerge
utility to combine the two DLL's into a new one that is signed. When I drag
the newly created DLL into c:\windoes\assembly, it does not show up. I also
used the command line gacutil, and the utility said my DLL was successfully
added, but when I run an NUnit test to test the DLL, I get this error
System.IO.FileNotFoundException : File or assembly name worksite, or one of
its dependencies, was not found.
Why do you suppose my DLL will not show up in the GAC?
"Jon Flanders[MVP]" wrote:
> You have to use ILDASM on the assembly - then run ilasm on it after -
> passing in the il and a key file
>
> ILDASM /out:asm.il asm.dll
> ILASM asm.il /KEY=key.snk /DLL /OUTPUT=asm.dll
>
>
>
> --
> Jon Flanders
> http://www.masteringbiztalk.com/blogs/jon/
>
> "nweddle" <nweddle@discussions.microsoft.com> wrote in message
> news:FE0E43D2-C5F2-413F-89FC-5632EEF32663@microsoft.com...
>
>
>
| |
| nweddle 2005-06-21, 5:50 pm |
| Update: Ok, I got the mergered assembly to show up in the GAC now. I failed
to provide a version, so it wasn't showing up. Despite this progress, I am
still getting the error:
System.IO.FileNotFoundException : File or assembly name worksite, or one of
its dependencies, was not found.
when running my NUnit test. The ILMerge utility might be causing some issues
here, but I'm not sure.
"Jon Flanders[MVP]" wrote:
> You have to use ILDASM on the assembly - then run ilasm on it after -
> passing in the il and a key file
>
> ILDASM /out:asm.il asm.dll
> ILASM asm.il /KEY=key.snk /DLL /OUTPUT=asm.dll
>
>
>
> --
> Jon Flanders
> http://www.masteringbiztalk.com/blogs/jon/
>
> "nweddle" <nweddle@discussions.microsoft.com> wrote in message
> news:FE0E43D2-C5F2-413F-89FC-5632EEF32663@microsoft.com...
>
>
>
| |
| nweddle 2005-06-21, 5:50 pm |
| Ok, I tried your solution and was able to create one signed DLL, however,
when I tried to perform the same steps again for the second DLL, I got a
failure on this command:
ilasm iManMPDotNetExt.il /key:C:\SI\SI.snk" /dll
/output=iManMPDotNetExtStrong.dll
.....
Assembled method ElemApplyTemplates::.ctor
Assembled method ElemApplyTemplates::execute
Assembled method ElemApplyTemplates::getMode
Assembled method ElemApplyTemplates::getNodeName
Assembled method ElemApplyTemplates::getXSLToken
Assembled method ElemApplyTemplates::needToPushParams
Assembled method ElemApplyTemplates::popParams
Assembled method ElemApplyTemplates::pushParams
Assembled method ElemApplyTemplates::reMarkParams
Assembled method ElemApplyTemplates::setIsDefaultTemplate
Assembled method ElemApplyTemplates::setMode
Assembled method Font<dummy>::.cctor
Assembled method Font<dummy>::getFontName
Assembled method Font<dummy>::.ctor
Assembled method ClassLoader<dummy>::.cctor
Assembled method ClassLoader<dummy>::getSystemClassLoader
Assembled method ClassLoader<dummy>::.ctor
***** FAILURE *****
I used the same *.snk file to create each DLL. Could this be the problem?
"Jon Flanders[MVP]" wrote:
> You have to use ILDASM on the assembly - then run ilasm on it after -
> passing in the il and a key file
>
> ILDASM /out:asm.il asm.dll
> ILASM asm.il /KEY=key.snk /DLL /OUTPUT=asm.dll
>
>
>
> --
> Jon Flanders
> http://www.masteringbiztalk.com/blogs/jon/
>
> "nweddle" <nweddle@discussions.microsoft.com> wrote in message
> news:FE0E43D2-C5F2-413F-89FC-5632EEF32663@microsoft.com...
>
>
>
| |
| Jon Flanders[MVP] 2005-06-22, 5:51 pm |
| Using the same key should not cause a problem - is that the only error
message you got?
--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/
"nweddle" <nweddle@discussions.microsoft.com> wrote in message
news:5C6E35F4-5E25-4AEE-9AA1-36A03C40368B@microsoft.com...[vbcol=seagreen]
> Ok, I tried your solution and was able to create one signed DLL, however,
> when I tried to perform the same steps again for the second DLL, I got a
> failure on this command:
>
> ilasm iManMPDotNetExt.il /key:C:\SI\SI.snk" /dll
> /output=iManMPDotNetExtStrong.dll
> ....
> Assembled method ElemApplyTemplates::.ctor
> Assembled method ElemApplyTemplates::execute
> Assembled method ElemApplyTemplates::getMode
> Assembled method ElemApplyTemplates::getNodeName
> Assembled method ElemApplyTemplates::getXSLToken
> Assembled method ElemApplyTemplates::needToPushParams
> Assembled method ElemApplyTemplates::popParams
> Assembled method ElemApplyTemplates::pushParams
> Assembled method ElemApplyTemplates::reMarkParams
> Assembled method ElemApplyTemplates::setIsDefaultTemplate
> Assembled method ElemApplyTemplates::setMode
> Assembled method Font<dummy>::.cctor
> Assembled method Font<dummy>::getFontName
> Assembled method Font<dummy>::.ctor
> Assembled method ClassLoader<dummy>::.cctor
> Assembled method ClassLoader<dummy>::getSystemClassLoader
> Assembled method ClassLoader<dummy>::.ctor
>
> ***** FAILURE *****
>
> I used the same *.snk file to create each DLL. Could this be the problem?
>
> "Jon Flanders[MVP]" wrote:
>
| |
| nweddle 2005-06-22, 5:51 pm |
| Yes, that is a copy and paste of the error from the command line.
"Jon Flanders[MVP]" wrote:
> Using the same key should not cause a problem - is that the only error
> message you got?
>
> --
> Jon Flanders
> http://www.masteringbiztalk.com/blogs/jon/
>
>
|
|
|
|
|