I'm working with a legacy product build environment that depends on (among other things) Microsoft Visual Studio .Net 2003. We're updating our build environment to use 64-bit machines, since our latest releases require it. But we'd like to also build the old project on the new machines.
The legacy build scripts are hard-coded to look for the command-line build tool at
C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.com. Unfortunately, on the 64-bit machines, MSVS 2003 always gets installed to
C:\Program Files (x86)\Microsoft Visual Studio .NET 2003. Since the build scripts don't know about that extra
(x86), the build fails. Updating the build scripts is not an option for this project, since only critical fixes are allowed.
I've reinstalled MSVS 2003 a couple of times, to verify that I can't just force it to install in the non-x86 path, but no luck. The WOW64 redirection always takes over and forces it to the x86 path. I don't think a simple drag-and-drop directory move is going to work either, since there are lots of references in the registry to the x86 path.
Any suggestions? Or am I stuck supporting the old build machines for another couple of years until the product reaches end-of-life?