If the Symbol is not loaded is necessary the following step:Īdd the project BIN directory to the directory list and press OKġ1) Add your breakpoints, and its done. Note: The option "Show processes in all sessions" need to be selectedĩ) Access to Modules (and wait for the press, because it takes a while)ġ0) Load the PDB file (select your extension, and the espace used in step 5) NET, the last field is filled (.NET Compiler Tool Options) with the option DEBUG, if is with RELEASE change it to DEBUG:Įxample: /nologo /verbosity:minimal /target:Rebuild /property:Configuration=DebugĢ) Open the project in Microsoft Visual Studio and edit BUILD properties for the following options:ģ) Build the project and publish the extension (Ensure that the PDB file is included in our Extension, if not select it, right click and choose Include in the project)Ĥ) Republish the espace that uses the extension (if is a action that is used in other espaces, they need to be republish too)ĥ) Open the page and activate the option that calls the extension (this is very important because it is this action that causes the module to be created on the server)Ħ) Access the server locally to record the extent of the project (using the Integration Studio or simply copying from another machine there)ħ) Open the Microsoft Visual Studio with Run as Administrator (important) and open the extension project(visual studio)Ĩ) Now we go to attach to Process IIS(w3wp.exe)
The first method i will explain is through IIS AttachĢ) Microsoft Visual Studio installed in the serverġ) In the Integration Studio, select Options (EDIT->OPTIONS) check if in the TAB.
#VISUAL STUDIO REMOTE DEBUGGING IIS HOW TO#
One of these days, I needed again to debug an extension and was not able to do it, so looked again how to debug an extension. To debug an extension is possible through IIS Attach, create a new project and debug through the new project or also through the log (ServiceCenter).
0 kommentar(er)
