Cryptic VBIDE link in C # project

I created software a long time ago and just opened a project and when I try to compile it generates two errors regarding VBIDE:

Warning 2 Cannot find wrapper assembly for type library "VBIDE". Make sure (1) the COM component is registered correctly and (2) your target platform is the same as the COM component bit. For example, if the COM component is 32-bit, your target platform does not need to be 64-bit. SonicPhoto

... and:

Warning 3 The specified "VBIDE" component was not found.

Thing is, I never remember to add this link as my project is a sound oriented program and VBIDE is "Microsoft Visual Basic for Application Extensibility 5.3" which has nothing to do with C #, let alone my program. If I remove the link, the solution compiles and seems to work fine. I assume I am completely safe to uninstall it if it works?

Perhaps I added this link by mistake? Just wanting to say that I have an old archive of my software, and the link is there too, and none of them compile when I know that at least one of the older copies of my software would have compiled. I also have a copy on another computer, and the link is there too, but the link is not broken, so the project compiles and runs.

+6


source to share


4 answers


In Solution Explorer, Click Show All Files, Click Links, Select VBIDE, RightClick it, and Remove it.



+16


source


I know this is a necropolis post, but I had the same problem and got it resolved.

I have a visual studio code that I am trying to compile / build from source and did not have this VBIDE link. I also needed RSlinx installed for the OPCautomation directory (its industrial automation program Rockwell) and Microsoft Office, since the program generates an excel file.



Anyone who shortly after I installed office 365 visual studio suddenly got a Vbide link that they couldn't find before. Removing the Vbide reference also allowed it to compile, so I would backup the program and try to execute it first.

Greetings

+1


source


How and assumed WelcomeOverflow, it decided for me:

Microsoft Visual Basic for Applications  ->  Menu  ->  Extras  ->  Links
-> [x]  Microsoft Visual Basic for Applications Extensibility 5.3

      

+1


source


Faced the same problem. Installed Office 2007 and the problem was fixed

-2


source







All Articles