Cannot find wrapper assembly for type library VBIDE

I recently had this problem while working within Visual Studio 2008 on an invoicing program. For the project I was required to add a few references. Towards the end of the project when I was debugging I realised the Warning “Cannot find wrapper assembly for type library VBIDE”.

I am unaware at this point which of the references I added also added the VBIDE reference but it was not needed within my code.

To solve the problem make sure you have all files in view, Project > Show All Files

Then go to the solution explorer and expand the references, from there you should be able to right click VBIDE and remove the reference.

If you need the VBIDE reference and have come across this topic trying to find out how to fix the problem then your best bet is to find out exactly what references you need and only add them in, it is likely that you no longer need the VBIDE reference but another reference.

28 thoughts on “Cannot find wrapper assembly for type library VBIDE

  1. Thanks!!! Removed the reference as indicated, rebuilt the project and it fixed the warning. VS 2010; Office Automation 2007.

  2. Thanks for this tip! Fixed my issue perfectly. It appears that the VBIDE reference is valid when using .NET 2.0, but not 3.5 or 4 afaict.

  3. Thanks for the solution for (warning MSB3283: Cannot find wrapper assembly for type library “VBIDE”), it was fast and effective. I am not sure how this reference got added.

  4. THANKS.HANDLED THE ISSUE . SIMPLY SOLUTION EXPLORER,REFRENCES,REMOVE VBID , CLEAN THE PROJECT,RE RUN

  5. Pingback: Reference vbide | Imagedisc

  6. Thanks, my error randomly appeared just like you. Wasn’t sure if I should delete it, but I did and it worked :)

  7. This tips has been very helpful to me, it has really taken my burden which start from 5:25 am to 5:00 pm completely away. Thanks

  8. Thanks. I only got this problem this morning. Any reason as to how this reference appears?

  9. Thank you for posting this solution. I had the same issue, but for a VB novice like me, it was like looking for a needle in a hay stack. I have no idea how this reference got added to an existing project I was working on. I did not move from one to pc to another, or anything obvious like that. It just got added all of a sudden? Anyway, thank you for your help. I removed the reference: “Microsoft Visual Basic for Applications Extensibility 5.3″ and that solved my problem.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>