The application requires that assembly Microsoft.Vbe.Interop Version 14.0.0.0 be installed in the GAC

I have scoured the internet.

I wrote a simple Winforms application that has worked perfectly for 2 years.  I just made some updates and I am getting the "Application requires that assembly Microsoft.Vbe.Interop Version 14.0.0.0 be installed in the GAC"  

The remote PCs....do not have Office on them.  I am using a access database, but they did not have access.  I have not upgraded anything on my machine and still using the same version as I did when I wrote the original code.  

I wrote the app in VS2005.  I did upgrade to VS 2010 and that is where I got the problem.  I went back to old machine and try to make the simple bug changes on 2005 and republish and still get the error on the remote machines.

I have looked at quite a few things...but can't figure this out.
bobnieldsAsked:
Who is Participating?
 
Jacques Bourgeois (James Burger)Connect With a Mentor PresidentCommented:
The Microsoft.Vbe.Interop is installed on users computers when they install Office.

With older versions of Visual Studio, such as 2005, it was required on the user computer. Since you do not have the right to redistribute it, users needed to have Office installed.

In newer versions of Visual Studio (starting in 2010), you can embed the portions of the interop that you use into your application itself. This way it does not need to be installed on the user's computer.

However, when you migrate an application from an older version of Visual Studio to a newer one, the switch to the new mechanism is not made, so you still need the interop on the user's computers.

In order to correct the situation, go to your References window, click on each of the references for Office and Office applications, and while the reference in selected, look a the Properties window and set the Embed Interop Types properties to True.
0
 
BembiCEOCommented:
I have the feeling, that your old application installed an assembly and while you installed VS 2010, the reference for your application is updated to a newer version. Now you try to run the solution and the client can not find the newer assembyly in the GAL.

So either you have to change your code back to the old assembly (the reference to the assembly in the source code), which was used before and which is possibly installed on the clients, or your have to distribute the new assembly to your clients.
0
 
bobnieldsAuthor Commented:
However, I did not install VS2010 on one of my machines.  It still has just VS2005.   I agree with what you are saying on a newer machine.  But I thought just to get through this, I would go back to my old machine and just create a new published load there.  But I still got the message.  And that definitely confused me.
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
BembiCEOCommented:
Would lead me to roaming profiles? VS usually puts everything into the profile by default. So if your project is stored there, you may have overwritten some settings in the project by VS 2010-

But nevertheless just check inside your project, to which assemblies you reference there and then check, if these referenced assemblies are present on your clients.
0
 
bobnieldsAuthor Commented:
Thanks I will try.

The odd thing is that this worked forever.  It just now does not work.  

The client computers never had office installed on them and they still don't.
0
 
Jacques Bourgeois (James Burger)PresidentCommented:
Another thing, while rereading. You are dealing with Access.

Is it possible that you changed the compilation target to 64-bit? This causes problems with a lot of stuff, and Access is one of these. You should usually target x86 when dealing with Access.
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.