Strong name dll - how to troubleshoot?

Question

I have followed instruction from other posts and from http://msdn.microsoft.com/en-us/library/xwb8f617.aspx to give strong name to my dll, which is a native (unmanaged) C++ dll. However when it is still not strong named when I try to verify:

>sn.exe -v myStuff.dll
=> myStuff.dll does not represent a strongly named assembly

I add my .snk file to the project and added the file to Properties->Linker->Advanced->KeyFile.

How should I troubleshoot?

Ok I have found that the /KEYFILE linker option is simply not taking effect. On another C++/CLI project, /KEYFILE is being used and .dll is signed properly. Why is the flag not used by the linker in my unmanaged project? — M W

fishfood fishfood · Accepted Answer · 2012-07-18T23:54:15

I thought I just read a question like this a moment ago. Someone had (rightly) stated that strong names are not applicable to native dlls.

I do hope you solve your issue, but in attempting to strongly name your native dll, you're barking up the wrong tree.

Strong name dll - how to troubleshoot?

1 Answers