My Visual Studio 2010
solution references a third party proprietary DLL.
When I try to compile the solution the error message reads:
Unable to emit assembly: Referenced assembly 'NameOfAssembly.DLL' does not have a strong name
Is the only solution to this issue to sign the third party DLL with my own key?
That's criminal negligence by anybody that creates assemblies used by others, given how trivial it is to give an assembly a strong name while building it. Doing it afterwards is quite painful, you have to decompile the assembly with ildasm.exe and put it back together with ilasm.exe, now using the /key option.
If you have a working relationship with the owner then send them a nastygram. If you don't then you probably should question the quality of the assembly, this is a major oversight and shows evidence that few people actually use the assembly.