By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,979 Members | 1,452 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,979 IT Pros & Developers. It's quick & easy.

Manifest definition "InterOp.Excel" does not match assembly reference.

P: n/a
CA
I am having a problem getting a pointer to an existing running Excel
process on a client machine.

Here are some details:
1) I have tested out the code on the development machine and it works
fine. (Excel XP)
2) The code works fine on a machine in our offices with Excel 2000.
3) On the client machine (with Excel 2000), the code does not work.

I wrote some diagnostic tests to further try and see what was going on
and I got the following error message:

The located assembly's manifest definition with name InterOp.Excel
does not match the assembly reference.

I used the Excel8.olb (Excel 97?) type library to build the
application, so I am assuming that it would work for all versions of
Excel beyond Excel97 ?

Can anyone help me in this matter? Thanks in advance.

Chris
Nov 16 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi Chris,

It seems that there is another assembly with the same name in the .net
fusion probind path.

I think you may try to take a look at the KB Article below.

PRB: "FileLoadException" Error Message When the .NET Runtime Searches for
Assemblies by Using the Probing Tag of the Application Configuration File
(821626)
http://support.microsoft.com/default...B;EN-US;821626

http://blogs.msdn.com/junfeng/archiv.../25/95826.aspx
Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

Nov 16 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.