C # in XP system down with C + + DLL times not found the specified module __c++

The environment for writing C + + DLLs is stated first: VS2013 + Win7 flagship 64-bit. The generated DLL does not have a problem with the native call, and there is no problem with the 32-bit call from the colleague Win7 flagship. However, when invoked on the client's computer, the specified module was not found when the XXX.dll was invoked, prompting the following:

If you click Details at this point, it will show up in one of the methods in your DLL. Just started thinking that the function method name was not found. But it works on other Win7 computers. To make sure of the problem again. Using the Dependency Walker software, we found that the function method name has been completely correctly guided. It is also placed in the root directory of the C # program, and it prompts you not to find the specified module. The assumption is that the environment may be different from Win7 to XP, and it should be what library files are missing from XP. Look at the dependency Walker program on the Internet you can also find out what the dependencies of the library are. After opening the discovery prompt is as follows:

According to the instructions above, locate the three files on the Win7 32-bit system and put them under the C:\WINDOWS\system32 folder. Find the same mistakes.

When searching for answers on the web, most of the references are made to modifying the compiler's settings! And according to the way they say, found or not! The back of the brain, as if there is a platform in the compiler can choose to be generated in the XP environment to run the program, remember that seems to be in the writing MFC program, not quite sure! A platform toolset was later found in the project Properties page. Replace the Visual Studio 2013 (v120) with Visual Studio 2013-windows XP (V120_XP), and copy it to the XP computer for a trial run. Discovery can, the reason is still not clear, hope to know the great God can guide. The settings are as follows:

It is sometimes possible for C # to invoke an error that attempts to load an incorrect format. We're right about that. NET project properties, right-click the project-Properties-build-the target platform is modified to (x86).