swex
asked on
Strong Naming a third party Assembly
I have an assembly that needs to be registered in Enterprise Services. Because of this, it is strongly named. It needs to have a reference to a third party assembly that is not strongly typed. I obviously have problems compiling as is. Is there any way to strongly name a third party assembly to which I don't have the source?
-Simon
-Simon
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
no I don't know if that would work... but it sounds like a nice idea!
Did it work?
ASKER
I'll let you know for sure once I try it on the webserver, I might have to strong-name a few.
-sw
-sw
ASKER
ILDASM C:\MyPath\theirs.DLL /out C:\MyPath\theirs.IL
should really read:
ILDASM C:\MyPath\theirs.DLL /out=C:\MyPath\theirs.IL
I'm thinking about this a bit more, and I don't think it's going to work for my purposes, I have to interact with this DLL as it runs within IIS as an application, I'm curious as to the downstream DLLs this guy will require.
You answered my question perfectly though and I'm sure it will come in handy later.
Do you know what would happen if I did the following:
- compile two DLLs (a and b) and a made reference to b
- decompile a (into IL) and recompile adding a key to strongly type
- allow a.dll to lazily register in Enterprise services and make use of it