Changing path of existing dll reference

[jason31337]

I have an app that references a TeamFoundationServer dll. I added the reference when I created the app and everything works fine. But I am trying to handle the case where they do not have their install directory structure set up like mine. So I get their install directory from the registry, change my currentworkingdirectory to the privateassemblies folder where this dll should be located in hopes that it will be smart enough to pick up the dll there and the reference will work.

Unfortunately this isn't the case. Now if I copy the dll to the folder where the exe is, everything is dandy. Does anyone know a way to change the path of the reference on the fly to match any users install configuration?

Thanks.

[RedSon]

I would try to do a directory search for it, but it might be easier to just throw up a dialog that says to the user, please give me the path to where this .dll is and then I can continue.

[jason31337]

I did a directory search and found the file, but since the reference has a path already associated with it (from when I added the reference originally) it doesn't seem to want to search anywhere else, even after changing the CWD to where the DLL is located.

I would try to do a directory search for it, but it might be easier to just throw up a dialog that says to the user, please give me the path to where this .dll is and then I can continue.