Rakafkaven
asked on
"The dependency... could not be found", but it's RIGHT THERE.
I have a .NET solution that displays the following in the Task List: "The dependency 'Microsoft.Vbe.Interop' could not be found". The dependency is apparently inherent in one of my references: Microsoft.Office.Interop.E xcel. This fits with the msdn reference ( http://msdn2.microsoft.com/en-us/library/15s06t57.aspx ) which claims that the Microsoft.Vbe.Interop.dll is added automatically when using one of the Office primary interops. Unfortunately, I got my Microsoft.Office.Interop.E xcel.dll from the project directory, and there's nary a Microsoft.Vbe.Interop.dll to be found there or on my drive.
The same msdn page I reference above mentions a Microsoft.Vbe.Interop.dll in the 'Available Assemblies' associated with the Microsoft Visual Basic for Applications Extensibility 5.3 component. I added a reference to that COM object, which creates a reference labeled Interop.VBIDE and one labeled VBIDE. The 'Name' property for VBIDE is Microsoft.Vbe.Interop, and the path is C:\WINNT\assembly\GAC\Micr osoft.Vbe. Interop\11 .0.0.0__71 e9bce111e9 429c\Micro soft.Vbe.I nterop.dll .
This seems like it ought to work, but it doesn't. If I add or remove the VBIDE reference(s), nothing changes. I still see "The dependency 'Microsoft.Vbe.Interop' could not be found", and I still can't successfully build.
Any suggestions would be appreciated.
The same msdn page I reference above mentions a Microsoft.Vbe.Interop.dll in the 'Available Assemblies' associated with the Microsoft Visual Basic for Applications Extensibility 5.3 component. I added a reference to that COM object, which creates a reference labeled Interop.VBIDE and one labeled VBIDE. The 'Name' property for VBIDE is Microsoft.Vbe.Interop, and the path is C:\WINNT\assembly\GAC\Micr
This seems like it ought to work, but it doesn't. If I add or remove the VBIDE reference(s), nothing changes. I still see "The dependency 'Microsoft.Vbe.Interop' could not be found", and I still can't successfully build.
Any suggestions would be appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You're welcome!
ASKER
2.) ...putting the extracted .dll into the same directory as the Microsoft.Office.Interop.E