how to solve --- COULD NOT LOAD FILE OR ASSEMBLY "MICROSOFT.OFFICE.INTEROP.WORD" in visual basic 2013

Hello Experts,
I keep getting this message on computers of one particular LAN,
Everywhere else it Works just fine.
tried all I had, nothing Works.
What can I do.
Regards,
RGuillermoProject ManagerAsked:
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.

Lokesh B RDeveloperCommented:
Hi,

You should have this DLL in your bin folder.

Microsoft.Office.Interop.Word.dll
0
RGuillermoProject ManagerAuthor Commented:
Hi Lokesh B R,
I just compiled again the App and the bin folder does not have that library
Where can I find it ?
Or how to make visual basic put it?
Thanl you,
0
Lokesh B RDeveloperCommented:
Hi,

Ok, did you add reference to Microsoft.Office.Core in References?
0
The Ultimate Tool Kit for Technolgy Solution Provi

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 for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

RGuillermoProject ManagerAuthor Commented:
Went to "Add references" cant find that exact name ´Microsoft.office.core' but do have the following options

in COM tab:
Microsoft.office 11.0 object library
Microsoft.office 15.0 Access database engine
Microsoft.office 15.0 object library
Microsoft.office euro converter...
Microsoft.office InfoPath
Microsoft.Office list 15.0

can you mention the steps to add it please ?
0
Lokesh B RDeveloperCommented:
Hi,

Add this reference

Microsoft.office 14.0 object library

can you post the complete error details.
0
RGuillermoProject ManagerAuthor Commented:
Hi,
I will use the only one I have; "Microsoft.office 15.0 object library

Attached you wil see a jpg of the error message.
error-message.jpg
0
RGuillermoProject ManagerAuthor Commented:
it says a reference to Microsoft.Office.core is already in place,
but Icant see it anywhere....
0
RGuillermoProject ManagerAuthor Commented:
My source code has this line,
Imports Word = Microsoft.Office.Interop.Word
0
Lokesh B RDeveloperCommented:
Hi,

Copy the necessary dlls from GAC.

1. Start Menu -> Run and paste the following command

%windir%\Microsoft.NET\assembly

2. Copy the necessary dlls and paste it in your bin.

3. redeploy and check
0
Éric MoreauSenior .Net ConsultantCommented:
Is Word/Office installed on that PC. It has to be installed on any PC you will be trying to run the application. The interops are just not enough.
0
RGuillermoProject ManagerAuthor Commented:
Yes ms office is installed in the remote pc
and copied all posible dll from %windir%\Microsoft.NET\assembly but cant solve it
All ideas are welcome
appreciate the support until now ,,, made me review stuff I was not thinking about...
0
Éric MoreauSenior .Net ConsultantCommented:
>>Yes ms office is installed in the remote pc

Same version you have on your development PC? You cannot reference version 15 if they have 14 (or other)
0
CodeCruiserCommented:
Have you downloaded and installed the correct version of Interop assemblies on the remote PC?

For Office 2010, you can download these from here

https://www.microsoft.com/en-gb/download/details.aspx?id=3508
0
Jacques Bourgeois (James Burger)PresidentCommented:
Ideally, you should install the interop from the Office installer, at least on the development computer.

Not sure for more recent versions, but on previous versions, the components for .NET were an option in the Office installer. You might try to trigger a Change for Office in the Programs section of the Control Panel, and select the option that lets you add or remove components. Make sure that the .NET components are selected. You will thus be assured that the version of the interops that you need for your version of Office will be available.

Run a Windows Update after the installation to update the interop is needed.

If you compile in Visual Studio 2013, you do not have to distribute the interop files with your application. In the reference Window, when you click on a COM dll such as the Office dlls, you can set the Embed Interop Types to True. This incorporates the interop Inside of you own application so that you do not have to install it on the user's computer. This is activated by default, but might be set to False if the application was created in an older versions of Visual Studio or if it was changed by mistake.
0

Experts Exchange Solution brought to you by

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
RGuillermoProject ManagerAuthor Commented:
Thank you!!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.