About additional process debugging problems:
often use the "Attach to Process" in which the project to debug the project, feeling very convenient. We do projects usually published to IIS (especially B / S), a direct address bar enter the address you can run the project, you do not have to use development tools to open a project run (open database). "Attach to Process" to debug the project, but also to our commissioning work to bring some convenient, especially slightly larger project, sometimes we need to commissioning, the project will be among the many set breakpoints, for clarity understand the details of each step. Sometimes, however, we need to quickly see the results, or if you want to skip some breakpoints (there is need, I do not want to delete those breakpoints) when using the "Attach to Process" debugging more convenient.
Open the address bar, run the project, during operation, need to debug, then you can set breakpoints in VS program which, then debug it step by:
Visual Studio 2008 - "Debug" - "Attach to Process" (or "tool "-" attach to process ") to select" w3wp.exe "process.
Window Server 2003 IIS6.0 (company) the company's machine + Windows 7 have been verified. In the picture "is appended to: Workflow Code" display position "script, T-SQL, trusteeship," but in their own machines, although there is a breakpoint (breakpoint additional error process will change the state), but you can not debug . More for the "Workflow Code" can be normally debug work.
However, there are relatively similar case and additional processes, the project is through the address bar running during operation, the project wants to debug, they can not pass the "Debug - Attach to Process", directly run the project (F5) on it, the effect is the same. Just need to log on to run the project in the jump directly to the appropriate breakpoint at the same time, a pop-up page will be more logged out.
VS2008 cracked version
http://www.cnblogs.com/chenkai/archive/2009/03/06/1401121.html
vs2010 project using vs2013 compiler error can not open include file "winapifamily.h"
My old project is under vs2010 project. After recently installed vs2013, open sln solution, commissioning, operation error
C: \ Program Files (x86) \ Windows Kits \ 8.0 \ Include \ um \ winsdkver.h (21): fatal error C1083: Can not open include file: "winapifamily.h": No such file or directory
This includes Windows Kits \ 8.0 \ include things included in the project directory.
Careful thought for a moment back to a previously compiled webRTC used, this is a sdk win8, so these three can get rid of the directory containing the normal compiler project.
I went down to my folder, find the update date is the date I installed the vs2013. That time to install vs2013 covers these directories. And webRTC we are using a very old version, there may be some unknown changes. If your project has to use these libraries, it can only be resolved in terms of compatibility to think.
