visual studio .net general: Recently installed VS 2005 on Vista with the SP 1 for Vista. Took existing
product and built in Vista. Runs in Vista, but no longer runs in XP (some
error message about not being configured properly). The attempts have only
been made on the development machines. The program consists of one EXE and
several COM DLLs.

Also, since the Vista and XP OS's are installed on the same machine (dual
boot), the VS 2005 is installed in the same location. As a result, rebuilding
the app even in XP yields the same problem.

On a side note, the original build (XP build) yielded UAC messages when
running the software. However, when built with new Vista version, these
message no longer are present (yes, I am an administrator and UAC is ON).

Any help would be appreciated. Thus far, I've found some mention of

I ran dependency walker (from Vista dev machine) and it said MFC80 and
MSVCR80 were missing. However, InstallShield shows them as merge modules,
accessible, and selected. (The app runs fine in Vista)

The embedded manifest looks correct as displayed in the MS help
"Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies".

I get this error when running on XP after being built in Vista.
"Error: The Side-by-Side configuration information in "PROGRAM.EXE" contains
errors. This application has failed to start because the application
configuration is incorrect. Reinstalling the application may fix this problem

-- I ran dependency walker (from Vista dev machine) and it said MFC80
and MSVCR80 were missing --

I had the same problem too even after I resolved my problem by shipping
the right redistributable.

I really wonder whether your EXE or DLL requires other redistributable,
such as MSXML, .NET Framework runtime, etc, which are installed by
VS2005 by default. In fact, if you change the settings of your projects
to link MFC statically, your application should just run fine any where
if the problem is strictly MFC problem only.

Also, check to make sure you are not linking to debug .lib files or
having DEBUG macros in preprocessor, which requires DEBUG version of the
DLL to work.

-- ... the VS 2005 is installed in the same location ... --

I found the above claim from another thread. I just want to make sure
you are not installing VS 2005 into exactly the same drive and same path
on both XP and Vista (ran twice). That could be a big problem.

Hope this can help.



[quoted text, click to view]