Http://blog.chinaunix.net/uid-576762-id-2733741.html in the morning when opening a Web page Asp.net error message: found the name of "infragistics. webui. ultrawebgrid. excelexport. the Assembly list definition in v3.1 does not match the Assembly reference. Infragistics. webui. ultrawebgrid. excelexport. v3.1 is a third-party control used in our program. This is also the first time I encountered such a problem. But I do not know what the real cause is and how to solve it. In the morning, I found the relevant information and solved the "error. Since the "assembly list" does not match the "Assembly reference. Let's take a look at the "assembly list ". What is assembly manifest )? We know that in. net. A program is packaged as a program set. Typically, an .exe file or a. dll file is an assembly. An Assembly generally contains the following parts: both the producer and. dll contain this content. See http://msdn2.microsoft.com/zh-cn/library/zst29sk2 (vs.80) for details ). in the Assembly set, the Assembly List (manifest) is very important. In short, it contains the files and contents of the assembly to be referenced by an assembly. In fact, this is what Microsoft says about "self-Explanation ". You can use the ildasm tool that comes with visual studio2003 to view this list: 1. Open ildasm, which is generally located in the \ SDK \ V1.1 \ bin \ directory of vs2003 installation directory. 2. Open ildasm and select File> open to add the Assembly you want to view. 3. Double-click "Manifest". The following content is displayed: the manifest is the program list. As shown in the red line, the Assembly needs to be referenced to the external file infragistics. webui. ultrawebgrid. excelexport. v3.1, also identifies the version number and key. Now, we know what an assembly list is and how to view an assembly list. Next we will look at what is Assembly reference. What is an assembly reference? All programmers in vs2003 know that when we use a third-party control or a DLL written by someone else, all I have to do is reference it. The action of referencing an assembly is divided into two steps: first, add the referenced assembly to the reference in the project. Second, when the source file is introduced into another namespace, we can use the classes, methods, resources, and other functions provided by the third-party control. For example, after "system. Data. sqlclient" is introduced, we can connect to and operate databases through the classes provided by the system. Data. sqlclient. Now you know what an assembly list is and what an Assembly reference is ". The problem is also quite clear. The version number of the third-party control referenced by the Program (which is caused by the path on my side) does not match the version number required for the final generated assembly list. .Netclr( (((((( .. Net searches by path. If the loaded version is inconsistent with the version in the program list, an error similar to "mismatch between the Assembly list definition and Assembly reference" will occur.
(Conversion) the Assembly list definition does not match the Assembly reference-Analysis and Solution
