Why do you want to write this article, because it is too worried, I believe that more people are also distressed, I don't know how to debug, now I will give a bright road for the hardships.
If you just want to debug, it is not detailed to debugging each line code, it is very simple, you can change the IIS to cache the ISAPI application, change it to No, IIS will not load to memory, Instead, each time it is temporarily loaded, so you can cover it directly after modifying the DLL, and no need to restart IIS, it is very convenient.
Of course, if you want to track the code level, then it is a bit complicated.
The steps are as follows: 1, IIS directory (root directory, virtual directory) Running level change to low (default as middle) 2, change the running user of the IIS directory to superuser run 3, change local security settings - user rights assignment - Operating system operation, select Super User 4, open your VC ISAPI project, select the process submenu item, then select INetInfo.exe 5, select the setup menu item for the project menu, check if you have you in additional DLL in debug tab The ISAPI DLL to be debugged, if not add, then save, re-step 4 6, if everything is normal, open your source file, see if you can set a breakpoint, if you can't check the step 7, issue an IE request , VC should be able to intercept this request for the current DLL operation 8, debugging
My environment is XP2 VC6 SP4
