Error: Could not load file or assembly 'Microsoft.Office.Interop.Excel Version=12.0.0.0 The server, where the SSIS package was executed, runs SQL Server 2008 R2 and SSIS 2008 R2 on Windows Server 2008 R2 OS. May 11, 2012 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.0.
2020腾讯云10周年活动,优惠非常大!(领取2860元代金券),
地址:https://cloud.tencent.com/act/cps/redirect?redirect=1040
地址:https://cloud.tencent.com/act/cps/redirect?redirect=1040
Software malvern zetasizer software manual. 2020阿里云最低价产品入口,含代金券(新老用户有优惠),
入口地址:https://www.aliyun.com/minisite/goods
入口地址:https://www.aliyun.com/minisite/goods
I am trying to convert docx file in pdf and I have been suceeded to convert pdf on local.
Steps which i have followed in
visual studio 2010
is toMy web config get modified and added assembly
My .cs code for converting doc to pdf is
Error such as
is coming. How should i resolve this problem
I have also tried downloading 'Microsoft Office 2010: Primary Interop Assemblies Redistributable' from link Here but it converted my 'Version=12.0.0.0' to 'Version=14.0.0.0' when i follow steps which i have said you firstly as ' click on Add reference --> Click to COM..' Ghost 11.5 exe dos download.
c#asp.net.netpdfoffice-interop|
this questionedited Jan 1 '14 at 8:46 asked Jan 1 '14 at 8:35 Alps 11 1 1 7 I have update my answer, please now take a look there – Ramesh Rajendran Jan 1 '14 at 8:46 i have added Microsoft.Office.Interop.Word.dll intp bin folder which i have get from microsoft.com/en-in/download/confirmation.aspx?id=3508 now the error such as 'Could not load file or assembly 'Microsoft.Office.Interop.Word, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' is coming – Alps Jan 1 '14 at 8:53 You have missed the correct version, please check that – Ramesh Rajendran Jan 1 '14 at 8:54 I assume you understand that you need Office installed (and properly licensed) on server. Note that running Office applications in ASP.Net servers is not supported- support.microsoft.com/kb/257757. – Alexei Levenkov Jan 1 '14 at 8:55 1 It is a horrible idea to use Office Interop from ASP.NET or another server technology. These APIs were written for use in a desktop application, for automating Office (a suite of desktop applications). Server applications are different in many ways that make it a very, very bad idea to use Office Interop in them. It's also unsupported by Microsoft, and may violate your Office license. See Considerations for server-side Automation of Office – John Saunders May 24 '15 at 8:57 | show more comments
4 Answers
4
Copy paste the
Microsoft.Office.Interop.Word.dll
into bin folder in server.It's may be added in this path
%ProgramFiles%Microsoft Visual Studio 12.0Visual Studio Tools for OfficePIA
but i don't know is it correct : more details please see this MSDN Link else, You can download this dll : http://stackoverflow.com/a/6309218/2218635
|
Microsoft.office.interop.excel C#
this answeredited Jan 1 '14 at 8:44 answered Jan 1 '14 at 8:37 Ramesh Rajendran 10.4k 13 46 90 from where should i get? can you provide me the link? – Alps Jan 1 '14 at 8:38 1 @Alps- don't you know how to google????? You will get it there. – Ronak Bhatt Jan 1 '14 at 8:39 See my updated answer – Ramesh Rajendran Jan 1 '14 at 8:44 i have added Microsoft.Office.Interop.Word.dll intp bin folder which i have get from microsoft.com/en-in/download/confirmation.aspx?id=3508 now the error such as 'Could not load file or assembly 'Microsoft.Office.Interop.Word, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' is coming – Alps Jan 1 '14 at 8:54 i have installed 2007 Microsoft Office System Update and my version changed to version 14.0 – Alps Jan 1 '14 at 9:03 | show more commentsHave you copied DLL (Microsoft.Office.Interop.Word) to the executable path?
Buffalo linkstation install optware ipkg. you have to copy this DLL to local path else the Microsoft office must be installed on this server.
Looking into error it seems that application is not able to find the file in specified path.
By default application will find the DLL first into GAC else into local path. There can be other reason like the version is different, in such case also you will get similar error.
|
this answer answered Jan 1 '14 at 8:40 Nil23 322 1 8 i have installed 2007 Microsoft Office System Update and my version changed to version 14.0 – Alps Jan 1 '14 at 9:03 Ok so in that case you should have exact same DLL version present as your local machine to make it work. Please either install same office version or you can keep same DLL at local path and remove DLL from GAC if there any this should also work. – Nil23 Jan 1 '14 at 9:31 @Nil23 can you provide a correct version link of 12.0,as I am also not getting that link. same issue is held with me i have downloaded and it conerts them to 14.0 – Mitesh Jain Jan 8 '14 at 12:12 @Nil23 please have a look on stackoverflow.com/questions/21274953/… – Mitesh Jain Jan 22 '14 at 5:40 |
You have missed the dell version.
Please download correct version of the dll.
|
this answer answered Jan 1 '14 at 8:57 user1432245 can you provide me a correct version link of 12.0, I am not getting that link – Alps Jan 1 '14 at 9:13 please have a look on stackoverflow.com/questions/21274953/… – Mitesh Jain Jan 22 '14 at 5:41 |
Correct procedure to use Word in C# Projects is:
- Add reference to Word Interop Library(Assembly)
- Add Excel in
using
section - Now use it in your coding.
The first step will work if you have Office(Word) Installed in your PC. If not then install. Then add reference to
Microsoft.Office.Interop.Word
of the version you need.a. If list doesn't shows the desire version then you may have another vision of Office with Word installed. By The Way, you can use any.
b. If you don't find anything like
Microsoft.Office.Interop
THEN may be office not installed OR you have Office 2013 or later. For higher version you can add assembly by going into COM tab of add-reference windows and add Microsoft Word {version-no} Object Library
. This will add the same.c. If you already have
Microsoft.Office.Interop.
in References with yellow-triangle-mark THEN remove it first.After that second step will totally work:
using Word=Microsoft.Office.Interop.Word;
And finally as a third step you can create Word object by
Word.Application wApp = new Word.Application();
.|
this answer answered Jan 2 '16 at 11:58 Adarsh Rajput 967 8 21 |
Recommend:asp.net - Could not load file or assembly 'Microsoft.Office.Interop.Excel, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'which download an excel file to apply some edits then upload it again. When access the excel file to be downloaded I got this error: 'Could not load file or assembly 'Microsoft.Office.Interop.Excel, Version=15.0.0.0, Culture=neutral, Public
Recommend:asp.net - Could not load file or assembly 'Microsoft.Office.Interop.Excel, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'
which download an excel file to apply some edits then upload it again. When access the excel file to be downloaded I got this error: 'Could not load file or assembly 'Microsoft.Office.Interop.Excel, Version=15.0.0.0, Culture=neutral, Public
Microsoft Office Interop Excel Dll Version 12.0.0.0
VS 2008 / Office 2007 - Microsoft.Office.Interop.Word, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C /> I moved the project from One Computer to another. Could not load file or assembly 'Microsoft.Office.Interop.Excel, Version=14. Microsoft.Vbe.Interop.dll office.dll Microsoft.Office.Interop.Excel.dll Microsoft. How can I reference Microsoft.Office.Interop.Excel version. A reference to Microsoft.Office.Interop.Excel version 15.0.0. To download the appropriate dll.
Microsoft Office Interop Excel Example Visual Basic
Version 1 - Reviewed: March 23, 2010
Error: Could not load file or assembly Microsoft.Office.Interop.Word, Version=12.0.0.0
The error that you get about missing interop files is usually the result of Office 2007 .Net Programmability Support not being installed. The interop assemblies are not a required component of an Office 2007 install, so they may not be installed. To install, either 'Full' setup must be selected or 'Custom' setup with selecting '.NET Programmability Support' for the desired products (for TariffShark, Word .Net Programmability support is needed).
Microsoft.office.interop.excel.dll
There's also few ways to correct the problem after Office 2007 is installed:
- Ask your IT Support folks to modify/reinstall your Office install and add '.NET Programmability Support'
- Reinstall selecting the 'Full' option of the Office 2007 setup
- Download the interop assemblies from http://www.microsoft.com/downloads/details.aspx?FamilyID=59daebaa-bed4-4282-a28c-b864d8bfa513&displaylang=en and install the downloaded .exe
You may need local administrator rights on your PC in order to take the steps outlined above.
Contact
- Monday-Friday: 7am to 7pm CT
- Saturday: Closed
- Sunday: Closed
I'm using VB.NET and the .NET 3.5 framework.
I am trying to automate word and excel using their respective PIAs to get intellisense help, then (since the users don't have the PIA assemblies/DLLs installed) remove the references so that it will work as a COM object call without throwing an error.
I found this article:http://msdn.microsoft.com/en-us/library/15s06t57.aspxbut it doesn't really help me with what version of the assembly/DLL I should use. When I go to add a reference I see something like these:
then
then
Notice all of these highlighted ones all sound similar and there are multiple versions of the assembly. The link I started with suggests the name of the DLL in association to the product version (like WORD version 12 --- Microsoft.Office.Interop.Word.dll) but doesn't say what version of the PIA assembly. So how do I know which one to use?
And a better question: why is this not OBVIOUS somewhere? All I want is Microsoft to say 'hey, you want to automate a mail merge with Word 2007? Use [insert meaningful DLL name here (PIA or 'tools' assembly?)]. By the way, you can get that DLL here ['here' hyper-linked to the download I need]. Working with computers that may have 2007 or 2010 installed? Make sure you have both DLLs (if that is the case), and here is how you test for it: [insert helpful example].
(e.g. 'For Word 14 (i.e. D-link router dir 615 username password. Word 2010), use the Microsoft.Office.Interop.Word DLL version 12.0.0.0' (is this the case? I don't know.)) That should be obvious, and it does not appear to be so.
Maybe it is obvious? Is the version of the DLL the same as the version of the program? (i.e. Microsoft.Office.Interop.Word DLL version 12.0.0.0 =?= WORD version 12)
Maybe I am over-thinking this, but it is still not obvious to me. I'll be happy if you can answer the first question, but if you can explain both, that would be better.
Watki02Watki02
4 Answers
Use the class browser to see if the DLL you add exposes the functionality you want (just like you do for every other reference you ever add.
why is this not OBVIOUS somewhere?
So, you want everything you could possibly ever create with the office integration documented somewhere? That doesn't make sense!
Billy basically answered your question
Office 2010=14.x.x.x Autocad 2010 only crack 32 bit.
Office 2007=12.x.x.x
Office 2003=11.x.x.x
Office xp=10.x.x.x
Before that, there weren't any PIA's so you'd have to make your own.
DarinHDarinH
There are plenty of ways to skin the cat known as 'how do I know which object does X'.
- use the object browser and search for the methods you desire.
- Code it and then add assemblies one at a time - slow and inefficient, but it works
As for figuring out particular bits, Microsoft MSDN, Support, etc all have resources. For mail merge, for example, I found this:http://support.microsoft.com/kb/301659
It is fairly easy to follow references for the code, if mail merge is the issue.
As for the 'why is this not obvious somewhere' comment: The Word obects are fairly well documented. Perhaps not to the level you wish to automate Intellisense, but this is a fringe case, IMO. I have been programming the .NET Framework since before the 1.0 release and have yet to have a business case for what you are doing. I also don't know of anyone who has had this type of business case. Following the 80/20 rule, I am not surprised there is not a handholding exercise on this one . or even full documentation. Nilsson schmilsson 1971 rar.
Microsoft.office.interop.excel.dll Version 16 Download
It's in the documentation, e.g. DocumentClass:
Namespace: Microsoft.Office.Interop.Word
Assembly: Microsoft.Office.Interop.Word (in microsoft.office.interop.word.dll)
Assembly: Microsoft.Office.Interop.Word (in microsoft.office.interop.word.dll)
If it has any dependencies on the other assemblies then it ought to add them in itself, or it might prompt you for them at runtime to add.
I'm not sure there's a definitive guide to picking which one, but I'd go for
- the oldest version of
Microsoft.Office.Interop.Word
that includes all the functionality you need, so you're compatible with as many Word versions as possible - prefer assemblies built with the correct .NET version - I've seen problems with 1.1 assemblies against 4.0 (although not Interop assemblies) but I think generally 1.1 with 2.0 (=3.5's runtime version under the covers) should be OK.
RupRup