When we are compiling the SharePoint Solution, it deploys to the SharePoint server and we are going to attaching the process (worker Process) to debug it. The process used to debug the solution depends on the setting of the Solution property (Solution property is nothing but type of the Deployment either you are going to deploying the sandbox solution or form solution).
Farm Solutions
· While using the Form solution, which is hosted in the IIS worker process (W3WP.exe), run code that can affect the whole farm.
· If you are deploying the Form Solution, you should be having administrator permissions until unless you can’t deploy, you are run code.
· If you want debug you are code you need to attaches the worker process, how do I know my worker process id (in our SharePoint Farm we have no of web applications, each web application having the separate worker process and id.)
· To know you are worker process id. From you are server go to Start-àrun-àtype cmd -àfrom the command Prompt type the command “cd windows” -à”cd System32” -à”cd inetsrv” à from here onwards execute the command -à“Appcmd list wp” we will get the list of the Application Pools name as well worker process ids.
· Or else go to directly Start-à RunàType the command “inetmgr” --->you will directly landing to the IIS server-->from here under the IIS Section you can see the “Worker Process” click on that, when you click on that you can able to see the Worker Processes like Application Pool Name , Process Id , State etc..
Sandbox Solutions
· While using the Sandboxed solutions, which are hosted in the SharePoint User Code Solution Worker Process (SPUCWorkerProcess.exe)
· While deploy the sandboxed solution run code that can only affect the site Collection of the Solution. Because sandboxed solutions do not run in the IIS Worker process (neither the IIS application pool nor the IIS Server). To deploy this solution no need to have farm level administrator Permissions if it is site collection administrator is enought
· To debug you are sandboxed solutions attachés the SPUCWorkerProcess process that is theSPUserCodeV4 service in SharePoint automatically triggers. It is not necessary for theSPUCWorkerProcess process to recycle to load the latest version of the solution.
No comments:
Post a Comment