|You can specify the location of strongly named assemblies in an application configuration file. I think doing so creates a maintenance nightmare but if you want to try it here are the details.
Add a application configuration file to the project and add the following
The location of the assembly is hard coded which is less than ideal and a slight improvement is possible by specifying a relative path in the codeBase href attribute. If application base directory is D:\MetraTech\RMP\BIN then this should be correct.
If the ClientProxies.dll relies upon other assemblies within ..\Extensions\Account\Bin then a dependentAssembly element must be added for each one otherwise the assembly loader will only look in the GAC or the application base directory.
Good luck and remember that all the xml is case sensitive. If you enter PublicKeyToken instead of publicKeyToken then the loader won't complain and will just quietly ignore the whole dependentAssembly element.