Third Party Assembly - Strong Naming - URGENT!!!!

  • Thread starter Thread starter BillGatesFan
  • Start date Start date
B

BillGatesFan

I trying to use a third party assembly that was written in 1.1. I'm
trying to use it in 2.0.

In order to use it in my project I have to strong name it, because my
assembly is strong named.

I managed to strong name it (a.dll) finally. But I just found out that
the Third Party Assembly references another assembly (b.dll) which is
not strong named. So I went ahead and strong named that
assembly(b.dll) as well. Now my project is complaining that b.dll is
still not strong named.

I did sn -vf b.dll and it said it was strong named. I was wondering do
I have to have the source code and project to do this correctly?

I was thinking I needed the source for the project so I can reference
a strongly named b.dll inside of a.dll project. Then I would build
a.dll and strongly name a.dll again.

Do I need to do that?

Also does it matter with version of the strong name tool I use? It
seemed like after I string named it using 2.0 strong name too that I
could not add it as a reference in 1.1.

Thanks in advance
 
There's an option called Assembly Wrapper Key File in the project
properties in Visual Studio. Did you try that?
Latish
 
Back
Top