Issue with adding Excel COM reference in VS 2005 using Office 2003

I have an application that was created using office 2003 and the Microsoft.Office.Interop.Excel.dll.  Everything has worked great for a year or so with the portion of the app that writes to Excel.  My pc was recently upgraded to Office 2010...so I had to remove the old and add the new references for Excel...again...no issues.  The problem was though, the app runs from Citrix, and since it has Office 2003, I needed to change them back...fine...no worries right?

Well, I made the changes on a pc with Office 2003, ran the app locally...everything worked.  Placed the app on the server and the Excel portion blows up.  It appears that when I added the Office 2K3 reference back in, it is now using Interop.Excel.dll...a different dll then what it was using before.

Now, I can just replace that other dll with the one it is currently using, but I want to know why it is using Interop.Excel.dll as opposed to Microsoft.Office.Interop.Excel.  I have tried this on a few pc's with Office 2K3 and I get the same result.
LVL 12
rgn2121Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
Éric MoreauSenior .Net ConsultantCommented:
because you are targeting a different version, you have 2 options here:
-switch to late binding (do not add a reference and use GetObject to create your instance)
-use a 3rd party application like http://www.aspose.com/categories/.net-components/aspose.cells-for-.net/default.aspx
0
 
rgn2121Author Commented:
I am targeting Office 2003...only Office 2003.  The last time I add the reference it used Microsoft.Office.Interop.Excel.dll.  Now it uses Interop.Excel.dll...both for Office 2K3 (Office 11)
0
 
Éric MoreauSenior .Net ConsultantCommented:
you are targeting Office 2003 but you have something different installed on your PC!
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
rgn2121Author Commented:
I have 2K3 on the PC's that I am developing on today...I have tried 2 office 2k3 pc's as stated above...
0
 
HairbrushCommented:
Microsoft.Office.Interop.Excel.dll is a "Primary Interop Assembly" (PIA) which is the "official" interop assembly as distributed by Microsoft.  It is strongly named and installed in the GAC. The intention is that this assembly is used by all applications that need to call the Excel API.  (IF you have multiple versions of Office then you may have more than one Microsoft.Office.Interop.Excel.dll in your GAC as they will have different signatures - the version number will be different)

Your Interop.Excel.dll sounds like it has been generated by creating a reference directly to the Excel.exe COM object.  Microsoft recommends against referencing the Office applications in this way.  See the third article below.

Sounds like you do not have the Office 2003 PIAs on the server.  You can check by looking in the GAC.

http://msdn.microsoft.com/en-us/library/aax7sdch.aspx
http://msdn.microsoft.com/en-us/library/kh3965hw(VS.80).aspx
http://msdn.microsoft.com/en-us/library/dww0e04a(VS.80).aspx

Hope this helps.
0

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
 
rgn2121Author Commented:
Thanks Hairbrush...I was adding my references the way link 3 described, but it kept choosing the Interop.Excel.dll.  One pc had the Office 2003 PIA's installed the other did not.  I installed them on the pc that needed them and it selected the correct dll.  I found out that from another developer in my dept that he has to do this almost every time there is an office update...I just didn't know it since it had been so long since I have been in this application.

Thanks for the links...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.