Need Strongly-Named version of DotNetNuke (DNN); do I need to recompile source files due to internal references? <p>I am in the process of Strongly Naming a system which uses DotNetNuke (DNN). Our own assemblies are now signed with a key file from within VS2013 and I have used the ildasm/ilasm method of strongly naming the DNN dlls with the same key file to keep things simple for now. But I am still seeing errors like</p> <pre><code>The type 'DotNetNuke.Entities.Users.UserInfo' is defined in an assembly that is not referenced. You must add a reference to assembly 'DotNetNuke, Version=7.2.0.607, Culture=neutral, PublicKeyToken=null'. </code></pre> <p>which suggests ('PublicKeyToken=null') that some reference to DotNetNuke dll is not looking at the new, strongly named version. I'm sure I've updated all references within our code so I'm wondering whether this due to an internal reference within the DNN code itself. In that case do I need to recompile the DNN source with references changed to the Strongly Named assemblies?</p> <p>If you have deployed a DNN site using strongly-named dlls please let me know what you had to do to make it work, thanks a lot.</p>