The issue occurs when adding the refrence, VS stops working and closes or restarts, sometime it can recover but the refrence isnt there.
I think I found the issue, I removed the refrence closed Visual studio and cleared out all bin directories under the project. I also had to clear out the directories under the obj folder as well, there was a copy of the interop in there as well. Becuase of the way that VS2010 and Framework 2.0 has issues with primary output when you have a deployment package associated with this I had to manually include the interop DLL, this cause it to be checked into TFS. So every time I tried to add a refrence it was finding a copy somewhere in a cache folder. I had to remove the refrence check it in and clear all the directorys listed above again. If you use the 4.0 framwork, it handles interops differently and just imbeses this in the classes dll instead.
With some further testing if I am using a 64 bit OS I can add a refrence to the x64 version of VB but the x86 one cause issues. In the same vaine, if I am on a 32 bit OS, I can add the x86 refrence without issue.
If FW 4 is suppored then the interop can be added to the assebly directly. Below are details to some of the issues I faced with the interop and delpoyments and why I included the interop directly. The setup projects dont detect the interop and include it in the package corretly, even with the copy locally.
http://social.msdn.microsoft.com/For...1-531b8e6ecef0
http://go4answers.webhost4life.com/E...ted-33389.aspx
http://go4answers.webhost4life.com/E...ct-124427.aspx