bobnields
asked on
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.
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.
ASKER
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.
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
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.
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.
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.
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.