Assembly References

[Trevor Hardwick]

Hi

I have an application that tries to load another assembly. When it tries I
get the following error message:

"Additional information: The located assembly's manifest definition with
name [Assembly Name] does not match the assembly reference."

Can anyone think of any obvious reasons why this error is occurring. I've
used ildasm.exe to check the manifest but can't see any obvious problems.

Regards

Trevor Hardwick

 

[Felix Wang]

You are referencing to a strong-named assembly and that assembly has been
rebuilt.

 

[Felix Wang]

Too elaborate a little bit more:

If you are using VS.Net to develop that strong-named assembly, everytime it
is rebuilt, its version get incremented (by default). If you have another
application referencing the assembly outside VS.Net, the application will
detect that the assembly does not match the record in its manifest.

--
Regards,

Felix Wang

You are referencing to a strong-named assembly and that assembly has been
rebuilt.

--
Regards,

Felix Wang

Hi

I have an application that tries to load another assembly. When it

tries

I
get the following error message:

"Additional information: The located assembly's manifest definition with
name [Assembly Name] does not match the assembly reference."

Can anyone think of any obvious reasons why this error is occurring. I've
used ildasm.exe to check the manifest but can't see any obvious problems.

Regards

Trevor Hardwick

 

[Trevor Hardwick]

We have the files under source control. The build tree was deleted then
recreated from the files in source control. I don't see how the version
numbers can change. The build works on all mchines except one.

Regards

Trevor Hardwick

Too elaborate a little bit more:

If you are using VS.Net to develop that strong-named assembly, everytime it
is rebuilt, its version get incremented (by default). If you have another
application referencing the assembly outside VS.Net, the application will
detect that the assembly does not match the record in its manifest.

--
Regards,

Felix Wang

You are referencing to a strong-named assembly and that assembly has been
rebuilt.

--
Regards,

Felix Wang

Hi

I have an application that tries to load another assembly. When it

tries

I
get the following error message:

"Additional information: The located assembly's manifest definition with
name [Assembly Name] does not match the assembly reference."

Can anyone think of any obvious reasons why this error is occurring. I've
used ildasm.exe to check the manifest but can't see any obvious problems.

Regards

Trevor Hardwick

 

[Felix Wang]

Let's look into the GAC of that particular machine and see whether we have
another version of the assembly in the GAC.

--
Regards,

Felix Wang

We have the files under source control. The build tree was deleted then
recreated from the files in source control. I don't see how the version
numbers can change. The build works on all mchines except one.

Regards

Trevor Hardwick

Too elaborate a little bit more:

If you are using VS.Net to develop that strong-named assembly, everytime it
is rebuilt, its version get incremented (by default). If you have another
application referencing the assembly outside VS.Net, the application will
detect that the assembly does not match the record in its manifest.

--
Regards,

Felix Wang

You are referencing to a strong-named assembly and that assembly has been
rebuilt.

--
Regards,

Felix Wang

Hi

I have an application that tries to load another assembly. When it tries
I
get the following error message:

"Additional information: The located assembly's manifest definition with
name [Assembly Name] does not match the assembly reference."

Can anyone think of any obvious reasons why this error is occurring. I've
used ildasm.exe to check the manifest but can't see any obvious problems.

Regards

Trevor Hardwick

 

[GuruJim]

I have the exact same problem, I am using a strong named assembly. And
the problem only occurs on a single xp machine out of around 50
tested. I have checked the GAC and the same versions are in there.

Moving the files between machines they work elsewhere.

A rebuild does not help.

I have also tried reinstalling the framework.

This is an interop library, I have tried adding a reference to it in
VB6 on the troubled machine. As soon as it tries to create the object
it fails with the manifest error