Microsoft Office Interop Excel Dll Version 12.0.0.0
If you are open to switching APIs, you can use a third party solution that is superior to the MS Office Interop in nearly every way.It is a fully managed.NET component rather than a COM object and it allows you to read/write/manipulate Excel files whether the client has Office installed or not. The trial version is fully functional, except for the restriction of only being able to read or write 120 rows. The full version is relatively inexpensive, and they do sell the sourcecode so compilation within a single EXE is a possibility. My is that my Dot.Net app references the Office 12.0 object library so that it can manipulate email in the user's Inbox. My customer has asked that the app be compatible with Office XP & 2003, but I do not have those installed on my development box and thus I have no Office object library for them.Is it possible to find out which file(s) make up the Office XP & Office 2003 object libraries so that I can add a reference to them in my app?
My app currently has a reference to the Office 2007 onject library (V12.0). Thank Matt, but when installing the 2003 PIA it states that you need to have Office 2003 installed, so I'm back to square one. Looking at my current project, which has a reference to Office 12.0 object library, it is referencing the file:C:WindowsassemblyGACOffice12.0.0.071e9bce111e9429cOffice.dllI suppose I need to find the 2003 version. I'm not sure if you guys understand what I'm trying to do. I have run my app in a Win environment with Outlook 2007 and it works fine.
I then loaded the app in a Win environment with Outlook 2003 installed and it failed with the error. Exception Text.System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Office.Interop.Outlook, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.File name: 'Microsoft.Office.Interop.Outlook, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'at rnsTrayNotification.cMailRoutines.ProcessInboxSo I changed the MS Office Interop reference to V11.0 and ran it on my Office 2003 system and still got this error. Exception Text.System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Office.Interop.Outlook, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.File name: 'Microsoft.Office.Interop.Outlook, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'at rnsTrayNotification.cMailRoutines.ProcessInboxI assume then that I need a reference to the MS Office 11.0 Object library to get it to run with Outlook 2003, but I do not have that file on my development system. When I set a reference to the MS Office Object library, I also assume that the file is not included but simply the reference to the file, which thus needs to be on the target system to allow the exe to run.So can I get the MS Office Object Library V11.0 from the Office 2003 CD and install it onto my development PC in order to set a reference to it? I tried your suggestion Greg and got the error:See the end of this message for details on invokingjust-in-time (JIT) debugging instead of this dialog box.
Exception Text.System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Office.Interop.Outlook, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. Julian,I meant using VS 2008 (VB 9). You have VS 2005 (VB 8): Microsoft.VisualBasic Assembly Version: 8.0.0.0I'm not sure if VS 2005 has that PIA included.I can suggest one more trick: Late Binding.1.
Set reference to Interop you have in your system. For example: Imports Microsoft.Office.Interop.Excel2. Write code based on this component: Dim xlApp As New Microsoft.Office.Interop.Excel.Application3. Fully test and debug your application on your machine.4. Remove reference (Imports.)5.
Microsoft.office.interop.excel.dll
Replace Dim xlApp. With: Dim xlApp as Object= CreateObject('Excel.Application')6.
Compile and install on any machine having at least Office 97: it will create xlApp object of the type it can find.Hope this helps.Greg. The error message you've posted reads you're using VS2005 (VB8):Microsoft.VisualBasicAssembly Version: 8.0.0.0Win32 Version: 8.0.50727.42 (RTM.0)2. To answer your questions: I think you're right. If you have both Office Interops v11 and v12 just refer to v11 and make sure it's included in the deployment package.
Microsoft.office.interop.excel 2007
I use Click Once installation, and it includes all references automatically.I use Late Binding (as I explained in my previous post) and don't care about Office version on a target machine.Greg.
VS 2008 / Office 2007 -I moved the project from One Computer to another which has Office 2003. As i dont have Office 2007 installed on this Computer, This Computer throws exception for dll - Version 12.0.0.0How should i fix this Dll interop issue?Error: Error 2 Could not load file or assembly 'Microsoft.Office.Interop. Word, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e 9429c' or one of its dependencies. The system cannot find the file specified.