Zip Component, Email Component, Encryption Component ActiveX Control for Zip Compression .NET Components for ASP.NET
ActiveX and .NET Components for Zip Compression, Encryption, Email, XML, S/MIME, HTML Email, Character Encoding, Digital Certificates, FTP, and more ASP Email ActiveX Component

Index of Chilkat Blog Posts

March 13, 2008

Assembly’s manifest definition does not match the assembly reference


I have an application program that was build referencing previous version of CHILKATDOTNET2.DLL Recently, I have downloaded the newer version of CHILKATDOTNET2.DLL and placed in same the folder of the application program. When I execute the application the got the following error:

Could not load file or assembly ‘ChilkatDotNet2, Version=, Culture=neutral, PublicKeyToken=eb5fc1fc52ef09bd’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0×80131040)

On the other hand, if I rebuilt the application program referencing the new version of CHILKATDOTNET2.DLL, but run the program with the older version of CHILKATDOTNET2.DLL, I also got similar error.

My question is: is the difference version of CHILKATDOTNET2.DLL not backward/forward compatible? My concern is that I have more than one applications using CHILKATDOTNET2.DLL, if for some reason I need to upgrade the server machine with the new version of CHILKATDOTNET2.DLL, it seemed that the applications using it will start to fail.


The .NET runtime enforces the condition that the version of the assembly loaded at runtime must match the version of the assembly used at compile time.

Privacy Statement. Copyright 2000-2011 Chilkat Software, Inc. All rights reserved.
Send feedback to

Components for Microsoft Windows XP, 2000, 2003 Server, Vista, Windows 7, and Windows 95/98/NT4.