c# - How do I update a Strongly-Named DLL within an ASP.NET website to use a newer version of delay signed DLL? -


in debugging linkedintoolkit, downloaded dotnetopenauth source git. i've added reference i'm getting following error when compiling prebuilt websites come linkedintoolkit

could not load file or assembly dotnetopenauth version 3.4.7.11039. strong name signature not modified....

considering dotnetopenauth dll delay signed, how make website compile , run?

i've searched web.config , references mention of named dll. else strong name check done?

if you're compiling dotnetopenauth yourself, should either turn off delay signing completely, or change key signed 1 have private key to. don't disable strong name checking -- that's security risk.

curious why have compile own dotnetopenauth library though.


Comments

Popular posts from this blog

python - Scipy curvefit RuntimeError:Optimal parameters not found: Number of calls to function has reached maxfev = 1000 -

c# - How to add a new treeview at the selected node? -

java - netbeans "Please wait - classpath scanning in progress..." -