The program "% csidl_program_files %/XX/xx.exe" cannot be started ". If an error occurs, it usually indicates that the installation is corrupted (Code 0x8007007e ).

No compilation error during DLL debugging in vs2005

However, when debugging is started, the following message is displayed:

------------------------------

The program "% CSIDL_PROGRAM_FILES %/XX/XX.exe" cannot be started ".

If an error occurs, it usually indicates that the installation is corrupted (Code 0x8007007e ).

If the problem persists, use "add or delete programs" in "Control Panel"

Fix Visual Studio installation.

------------------------------

After searching, we found that the cause of this situation is:

The DLL file to be called does not exist.

Solution:

Copy all the DLL files to be called to the WinCE device.

Directory of the EXE file being debugged

(/Program Files/exe file name ).

For example:/Program Files/XX

------------------------------

Zhu minglei

 

This article from the CSDN blog, reproduced please indicate the source: http://blog.csdn.net/joyzml/archive/2010/01/11/5176018.aspx#1369151

 

I am very depressed about this evil problem.

Later, I rebuilt the dynamic library project. During the deployment, several dll files not generated by my project were copied to the current directory, so they could be run or even debugged.

I don't understand why I have to re-build it. However, the original project, compilation and deployment, cannot copy these dll files to the device.

 

Next, I made an experiment to copy these files to the/windows directory, and deleted the dll files under the project directory of the device,

It can still run successfully.

 

After observation, the program that can run and debug smoothly was deployed with the following content:

 

1> ------ started Deployment: Project: ConnMgrDll, configuration: Debug Windows Mobile 6 Professional SDK (ARMV4I )------
1> D:/Program Files/Microsoft Visual Studio 9.0/VC/ce/dll/ARMV4I/msvcr90.dll
1> D:/Program Files/Microsoft Visual Studio 9.0/VC/ce/dll/ARMV4I/atl90.dll
1> D:/Program Files/Microsoft Visual Studio 9.0/VC/ce/dll/ARMV4I/msvcr90d. dll
(1) D:/Program Files/Microsoft Visual Studio 9.0/VC/ce/dll/ARMV4I/MFC90UD. dll
1> e:/ConnMgrDll/Windows Mobile 6 Professional SDK (ARMV4I)/Debug/ConnMgrDll. dll
=========== Deployment: 1 successful deployment, 0 failed deployment, and 0 skipped deployment ==========

If debugging cannot be started smoothly, the deployment is as follows:

2> ------ started Deployment: Project: CEHttpDll, configuration: Debug Windows Mobile 6 Professional SDK (ARMV4I )------
2> e:/ppcDll/Mobile protocol DLL and test/CEHttpDll/Windows Mobile 6 Professional SDK (ARMV4I)/Debug/CEHttpDll. dll
============ Generate: 1 success, 0 failed, 0 latest, skipped 0 ==========
=========== Deployment: 1 successful deployment, 0 failed deployment, and 0 skipped deployment ==========

Taking a closer look at the several excess dll files, they all came with vs2008:

1> D:/Program Files/Microsoft Visual Studio 9.0/VC/ce/dll/ARMV4I/msvcr90.dll
1> D:/Program Files/Microsoft Visual Studio 9.0/VC/ce/dll/ARMV4I/atl90.dll
1> D:/Program Files/Microsoft Visual Studio 9.0/VC/ce/dll/ARMV4I/msvcr90d. dll
(1) D:/Program Files/Microsoft Visual Studio 9.0/VC/ce/dll/ARMV4I/MFC90UD. dll