error
"Could not load file or assembly 'DevExpress.Data.v19.1' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)"
when publish my project on ftp server in vs2019
Good ol' DX-dependency hell... Key-takeaway from your error-message is "...OR one of its dependencies". Somehow certain DX-assemblies have implict references to other DX-assemblies. Result is the exact situation you encounter: in your dev-environment everything runs fine until you deploy your app to a machine where DevExpress is NOT installed and sh** hits the fan. Check out the Devexpress Assembly Deployment Tool that comes with the Installer - it should solve your problem.
are you sure, you also published the DevExpress dlls to the ftp server and no file is missing.
Related
Our ASP.NET website uses some external assemblies like AjaxControlToolkit.dll, AjaxMin.dll, DocumentFormat.OpenXml.dll and some more.
They are registered in the References-Node. All worked fine, but after the latest windows Update, I got the following error:
Could not load file or assembly 'AjaxControlToolkit' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)
If I check the AjaxControlToolkit.dll with the tool sn.exe, it shows, the dll is valid. I have also tried to compile the AjaxControlToolkit with the source code. I have signed it with a strong name and the sn.exe has shown valid. I have tried to install ist to the global assembly cache with the gacutil.exe, but this fail although with the same problem, it has a problem with the strong name, also i have self compiled and signed and so on.
But it is not the problem, because, if i remove the AjaxControlToolkit.dll from the bin folder of the website, running in iis, then, the next dll creates the same error, the AjaxMin.dll could not be loaded.
If I remove the AjaxMin.dll, the DocumentFormatOpenXml.dll created the same error.
We are using Visual Studo 2010 and we have hosted our website in Windows Server 2008 R2.
Kind regards
I was able to resolve this by redownloading the binaries from CodePlex.
http://ajaxcontroltoolkit.codeplex.com/downloads/get/116533
First of all I publish my website in windows 7 and everything goes alright.
But when I'm trying to publish the same website in windows server 2008 r2 I got this error:
Server Error in '/MyWebsite' Application. Could not load file or
assembly 'System.Net.Http' or one of its dependencies. Strong name
signature could not be verified. The assembly may have been tampered
with, or it was delay signed but not fully signed with the correct
private key. (Exception from HRESULT: 0x80131045)
Can any body help me, please!! I looked for this error for days now and I got nothing to do.
Thanks in advance!
It seems you not copied your dll to your another website in window server 2008 r2
if you already copied .dll to your 2008 iis then ..
First check
Both are system are running in same 64bit or 32bit ?
If not then
1.Open IIS Manager
2.Select Application Pools
3.then select the pool you are using
4.go to advanced settings (at right side)
Change the flag of Enable 32-bit application false to true.
Another solution
1- check if you are referencing an assembly which in turn referencing an old version of unity. for example let's say you have an assembly called ServiceLocator.dll which needs an old version of Unity assembly, now when you reference the ServiceLocator you should provide it with the old version of Unity, and that makes the problem.
2- may be the output folder where all projects build their assemblies, has an old version of unity.
you can use FuseLogVw application to find out who is loading the old assemblies, just define a path for the log, and run your solution, then check (in FuseLogvw) the first line where the Unity assembly is loaded, double click it and see the calling assembly, and here you go.
There are many other possibilities..
I am deploying ASP.Net MVC 3 application on Windows 2008 R2 server. I published the application from Visual Studio 2010 using File System. I have two assemblies that have delay signed and have valid snk file. The deployment was done using xcopy as it is internal application.
But there were some solution related changes after some time. I renamed the two assemblies but have not changed snk files. Now after deployment, I am getting following error -
Could not load file or assembly MyApplication or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileLoadException: Could not load file or assembly My doneApplication' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)
Can somebody help me to sort this issue?
I am basically a Winforms guy and learning Web in my office. Recently I ran into same problem but got it resolved. I noticed, in my case I did not have Windows SDK for Windows 7 and .NET Framework 4 installed on my machine. Try installing this and restart system.
You need to verify your assembly using sn.exe. Open command prompt in admin mode
sn.exe -Vr publicTokenNumber
The above will verify the delay signed assembly. Sn.exe can be found in C:\Program Files\Microsoft SDKs\Windows\v6.1\bin and C:\Program Files\Microsoft SDKs\Windows\v6.1\bin\x64 path. Try to run both the exe files and verify your assembly. I have given a similar answer here. You can also refer that.
Hope it helps.
How do I publish/deploy an asp.net website to a live server (like a goDaddy server)?
I moved all the files to the remote server without dataaccess layer and business layer. Move dlls to bin folder on live server. But when I try to browse website it gives errors like:
Could not load file or assembly 'BusLayer' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.BadImageFormatException: Could not load file or assembly 'BusLayer' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
Please help me handle these errors. I am not very good at English; maybe there are a lot of mistakes in my question. Thanks in advance for help.
I assume Bus layer means business layer. I believe that your presentation layer has some dependencies on the business layer. Now since you didn't push the business layer to production (remote server), its looking for a file and not finding it and hence the error.
the fix i guess will be to move all your files to remote server and try browsing files that doesn't have database dependencies (Again, assuming you don't have a database at production)
"This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded." usually means that you have a .NET version issue. Is the BusLayer assembly on the server compiled under a newer version that the web site?
Also, does the app run locally? If so, publish all the contents of your local BIN.
I hope you made a backup of your site prior to deployment.
I just tried to copy my entire web application to a new instance of Visual Studio 2008 on another (virtual) machine.
It builds just fine, but when I try to run the applicaton I just get the message "The specified module could not be found".
Does anyone have an idea how I can find out which module this message refers to? Because there are quite a lot, and as far as I can see they're all installed.
I would suggest you delete all the temporary ASP.Net files for your project and then do a rebuild. This will ensure all the new code is recompilled and no old references remain.
Sometime simply building the solution doesn't work and you need to rebuild instead to force it to either show you the real error or get the references correct.
If your project uses COM and an interop assembly, you'll be able to build (because the assembly is there), but raise a runtime exception if the COM server is not registered on the new machine.