"Scot Brennecke"<ScotB@spamhater.MVPs.org> wrote in message
news:uJZSGUQZKHA.740@TK2MSFTNGP04.phx.gbl...
Do you really mean that your MFC80D and MSVCR80D DLLs are under x86,
ia64, and amd64 folders? They should not be under such folder names.
They should be under long folder names such as the one you listed for
GDIPlus.
If you have a correct installation of Visual Studio 2005 on that
machine, you shouldn't need to install the VCRedist.
The WINVER should not have anything to do with where it looks for the
dependencies.
Since the issue is related to a failure of registering an OCX, try
running the Process Monitor tool, and examining the file and registry
attempts of regsvr32 to see if any failures seem to correlate to the
registration failure.
When I was compiling on Windows 2000, I had turned off the "Generate
Manifest" setting in the Linker settings for the project. Moving the source
and project files to an XP machine and compiling without a manifest left the
ocx without enough information to find the dlls that regsvr32 needed to
register ocx file. Saying "Yes" to generate manifest fixed the issue and
now the custom build step succeeds.
ProcessMonitor was very useful in helping me figure this out. Thank you for
the suggestion.
BTW - the DLLs were in folders with long folder names. I was only trying to
point out that I had x86, ia64 and amd64 versions of the MFC and CRT dlls.
Thank you for your help.
J
You're welcome.
the WinSxS model is supported. Win2000 was the last OS version to not