Why did I need a strong name?

  • Thread starter Thread starter jm
  • Start date Start date
J

jm

I was attempting to use SHDOCVW.dll in my C# program. I added the COM
reference to it and it created the Interop.SHDocvw.dll for the Runtime
Callable Wrapper as expected. However, it said that "strong name" was
false.

What I did was go create a new strong name by:

sn -k mykeyfile.snk

This created the .snk file and I copied this to the files where my
solution file was. Now, when I went back to the Interop.SHDocvw.dll
and looked at its properties it said "strong name" true.

I do not understand what just happened. I knew it would work from
experience, but I really don't know *why* it worked. I was hoping
someone could help explain it to me.

I thought the strong name was just for shared assemblies that all .NET
programs would be able to use. I wasn't doing that, I thought.

Thank you for your time.
 
I thought this was fairly common. No?


jm said:
I was attempting to use SHDOCVW.dll in my C# program. I added the COM
reference to it and it created the Interop.SHDocvw.dll for the Runtime
Callable Wrapper as expected. However, it said that "strong name" was
false.

What I did was go create a new strong name by:

sn -k mykeyfile.snk

This created the .snk file and I copied this to the files where my
solution file was. Now, when I went back to the Interop.SHDocvw.dll
and looked at its properties it said "strong name" true.

I do not understand what just happened. I knew it would work from
experience, but I really don't know *why* it worked. I was hoping
someone could help explain it to me.

I thought the strong name was just for shared assemblies that all .NET
programs would be able to use. I wasn't doing that, I thought.

Thank you for your time.
Click to expand...
 
Back
Top