SharePoint debugging and diagnostics series-Attach methods for different debugging objects in the Development Environment

Debugging different objects in the development environment of SharePoint sometimes requires attach to different processes. Below are some common situations:
1. Farm solution ----- w3wp. exe
2. Sandbox Solution-----PUCWorkerProcess.exe,
3. Use the sandbox Solution--SPUCWorkerProcessProxy.exe of Full-trust proxy
4. Feature receivers ---- feature cycler is automatically started by Visual Studio by default. You can change this setting in the deployment settings of Visual Studio.
4.1. activation/deactivation of feature receivers: depending on how it is activation/deactivation, You need to attaching to different processes.
• Start or stop ---- w2wp. EXE on the web interface
• Start or stop ---- powershell.exe in powershell
4.2 featureinstalled/featureuninstalling/featureupgrading of feature receivers (installation/uninstall/upgrade) ----- owstimer.exe

(In attach's owstimer.exe, note that your breakpoint may not be immediately hit, because their execution depends on the start of the timer job. When the timer job calls these feature referers, their breakpoints will be hit, so you may have to wait for a while)

Debugging different objects in the development environment of SharePoint sometimes requires attach to different processes. Below are some common situations:
1. Farm solution ----- w3wp. exe
2. Sandbox Solution-----PUCWorkerProcess.exe,
3. Use the sandbox Solution--SPUCWorkerProcessProxy.exe of Full-trust proxy
4. Feature receivers ---- feature cycler is automatically started by Visual Studio by default. You can change this setting in the deployment settings of Visual Studio.
4.1. activation/deactivation of feature receivers: depending on how it is activation/deactivation, You need to attaching to different processes.
• Start or stop ---- w2wp. EXE on the web interface
• Start or stop ---- powershell.exe in powershell
4.2 featureinstalled/featureuninstalling/featureupgrading of feature receivers (installation/uninstall/upgrade) ----- owstimer.exe

(In attach's owstimer.exe, note that your breakpoint may not be immediately hit, because their execution depends on the start of the timer job. When the timer job calls these feature referers, their breakpoints will be hit, so you may have to wait for a while)