Quote Originally Posted by jmsrickland
Well, the only thing I can think of as to how to get those DLLs into the system's directory is to use DOS. However, you said you are on Vista and I don't have a clue about using DOS with Vista. But if you could use DOS then you would have to have those DLLs on either a CD or a diskette. You would then make a copy of the original DLLs and place the copies in another directory (just in case you need to get them back) then shut down your PC and bring it back up again in the DOS mode and using DOS erase the original DLLs from the system's directory and then copy the new DLLs from your external media (CD/Diskette or whatever) into the system's directory. Then reboot back to Windows. The risk involved is, even if you can do this, is the impact of the new DLLs on other existing applications that run good on the original DLLs. It may have an adverse effect.

I am surprised however that you were not able to reference the new DLLs that you added to the Reference list. Make sure that your remove the old reference to the DLLs from your VB program (Ie, remove the WebBrowser control from your project) so that you are in essense starting over again. Then after adding the reference to the new DLLs in the project directory to the VB's compoments list re-add that onto your VB project. I don't understand why you should have a problem. I have done this many time even having two references to the same component on the list but in different locations has always worked for me (on Windows XP). I would try to work it out to reference the components in their new location before I would attempt to replace them in the system's directory. I just got to believe that it can be done but again I can't comment on wheather it will work on Vista or not.

well this ...