Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Today I had a problem with some routing in my ASP.NET MVC 3 application (with Visual Studio 2010).
So I thought I install the ASP.NET RouteDebugger and fix my route problem.
After I get the package through NuGet my project doesn’t build anymore:
referenced assembly ' RouteDebug' does not have a strong name
I could download the source of the RouteDebugger and build (and strongly sign) it myself, but that’s not the purpose of NuGet isnt’ it 😉
Anyone else had this problem and maybe fixed it?
Well, the problem is not really related to NuGet. You cannot reference unsigned assembly from a signed assembly. And because the
RouteDebug.dllas contained in the NuGet package is not strongly signed you won’t be able to use it if your application is strongly signed. So you basically have two possibilities to choose from: