Unmanaged C++ - need strong name to be referenced by C++/CLI dll with strong name?
===

I have a unmanaged C++ dll, which will be used by a managed C++/CLI wrapper .dll, which will eventually be used by a C# project.
 
C# project is strong-named, so is the wrapper .dll.  I tried doing the same for the unmanaged dll, using /KEYFILE, but doesn't seem to work.  And the wrapper is complaining:
 
    .... is a strong-name signed assembly and embedding a manifest invalidates the signature
 
Do I need to strong-name the unmanaged C++ at all?  If not, how do I resolve this issue?
