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.

Comments

Permalink

Thanks, this was of great help to me.

Permalink

thanks

Permalink

Thanks, this was very good....

Permalink

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

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.

Permalink

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.

Permalink

Thanks! You helped me a lot!

Permalink

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

Permalink

Thank you very much!! This trouble was driving me mad!!

[...] Cannot find wrapper assembly for type library VBIDE | Dev BlogJun 5, 2009 … 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 … [...]

Permalink

Thanks! Instant relieve!

Permalink

This was of great help to me. Thanks

Permalink

THAX ALOT......

Permalink

Thanks a lot u saved my day

Permalink

Glad to help.

Permalink

Thanks for the help

Permalink

Thanks. You save my day.

Permalink

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

Permalink

Thanks, you just saved my day!

Permalink

Thanks - it helps very quickly - appreciated.

Permalink

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

Permalink

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

Permalink

Thanks,..... Maann you are a Geniusssss !! <3 <3

Permalink

Also worked for me... THANKS!!!

Permalink

Thanks!!!! I have been having this issue for 2 days!

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.

Permalink

Thanks a LOOOOOOOOOOOT

Permalink

Thank you!

Permalink

Thank You Its Very Help full

Add new comment

Plain text

  • No HTML tags allowed.
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.