>No, that won't work - only for the build. At runtime, the file and path have to exist and it is a different location depending on 32bit or 64bit. the only real solution is for the 3rd party provider of the .net dll to build one to run on 64bit so it can go in the same location as it does on 32 bit - in \Program Files not \Program Files(x86).
>
>Checking on the progid stuff from Rick's recommendation earlier but not sure we want every 3rd party com dll registered on the build server...

I'm not sure why this would be a problem. If things are installed in Program Files aren't you installing these components anyway through some installer mechanism? Won't that automatically register these COM components?

If this is a build server there shouldn't be any problem with things being registered on this server anyway. If you're worried about security wouldn't you be way more worried about security in your production environment where the components HAVE to be registered or else the whole COM interop mechanism won't work.


+++ Rick ---