News 1

How to Debug in the .NET Portal Source Code

2016.10.04

Debugging the .NET portal source code can be something of a challenge for those who have not done this before. But it is achievable, once the relevant environments are configured to make debugging easier.

Firstly, you need to compile the source code, to create the appropriate project files (.csproj). We recommend reading this first.

After that is done, take the following steps to debug the .NET portal source code, which RevDeBug makes considerably easier:

  1. Set up the IIS Manager
  2. Establish Local Security Settings
  3. Debug in Visual Studio, with RevDeBug

1. Set up the IIS Manager

We have mentioned the IIS Manager in a previous blog, when talking about how to debug web applications in .NET. Now you need to access this program again, to create the right environment for debugging .NET portal source code.

Getting started means opening the IIS Manager in Start > Programs > Administrative Tools > Internet Services Manager.

Navigate to the virtual website called Portal. This is usually found under Web Sites\Plumtree Web Site or Web Sites\Default Web Site. Right-click Portal and select Properties And then work through the following steps to configure the IIS Manager:

  1. Change the local path point in the Virtual Directory tab to:
    6.0: SOURCE_HOME\portalui\6.0.x\ptwebui\portal\dotnet\prod\src\web
    6.1: SOURCE_HOME\portalui\6.1.x\ptwebui\portal\dotnet\prod\src\web
  2. Click the Configuration option. The Application Configuration dialog box will appear. Click Mappings.
  3. Underneath, Application Extensions will appear. Select the .aspx extension and click Edit.
  4. In Verbs, select All Verbs.
  5. Click OK.
  6. Do the same again for following extensions: .pt and .asax.
  7. Next, click the Debugging tab and select the Enable server-side script debugging box.8. Click OK to return to the portal Properties dialog box.
  8. To avoid difficulties in the next stage, click the Directory Security tab, and the Edit option, under the Authentication and access section.
  9. Select the Integrated Windows authentication tick box.
  10. Finally, click OK in the Authentication Methods dialog box and the Portal Properties dialog box.
  11. Exit the IIS Manager.

2. Establish Local Security Settings

Now you need to configure local security settings. Access them through: Start > Programs > Administrative Tools > Local Security Policy.

  1. Next, Expand Local Policies and click User Rights Assignments.
  2. In the window on the right hand side, right-click Debug Programs, and select Properties.
  3. Check if your user name is on the list (this should be the same one used for Windows Authentication). If not and there is no group that you are a member of, then click Add User or Group to join.
  4. Double click OK to close the window and exit Properties, and then Exit Local Security Settings.

3. Debug in Visual Studio, with RevDeBug

Once everything is set up, you can run the portal source code in the test environment. Enable RevDeBug to capture each line of code, to ensure you can step back into each stage of the source to isolate and fix bugs quicker.

Find out more about the benefits of reverse debugging.

Back to list
transition5