How To Debug Remotely Using Visual InterDev on a Server with Site Server Personalization and Membership Configured (263658)

MORE INFORMATION

Set up the Windows NT File System

1. Create a new folder named DebugWeb (c:\DebugWeb) to hold the content for the Web site.
2. If both computers are on the same domain, make your domain account an administrator on both the client and the server.
3. Log on with that account to both the client and the server.
4. If both computers are not on the same domain:
   
   Create a new local Windows NT User account named DebugUser with the password "1Password1". This account should exist on each computer. Make sure to set the Password never expires option. Add this account to the local Administrators group. Log on with this account on the server.
   
   Create a new local account on the client computer that duplicates the account that you created on the server. Make sure that this account also has the same password and administrator rights, and that it is set to never expire. Log on to the client computer with this account.

Create a New Web Site on the Server

1. On the server computer, open the Internet Services Manager, and create a new Web site on port 8085 named "Debug".
2. Type the path to the C:\DebugWeb folder, which you created previously.
3. Allow anonymous access to the site and "Read" and "Run Scripts" permissions.

Configure Server Extensions for This New Web Site

1. In Internet Services Manager, right-click Debug (the newly created Web site).
2. Click All Tasks from the pop-up menu, and then click Configure Server Extensions.
3. You can use all the defaults, but select No, I'll do it later for mail configuration.

Create a New Membership Instance

1. Under the Personalization and Membership node of the Site Server Microsoft Management Console (MMC), right-click the server name, and then click New. Select Membership Server Instance.
2. For step 1, select Custom configuration; in step 2, click AUO and LDAP; in step 3, click Create a new Membership Directory; and in step 4, click Membership Authentication.
3. Select a directory name ("PMUsers") and password ("password").
4. Select the database that you have set up for Site Server Personalization and Membership (Microsoft SQL Server preferred), connect, and finish the wizard.
5. You should see this new mapping under the server name in the Personalization and Membership node of the Site Server Microsoft Management Console (MMC). Right-click the new mapping, and rename it VIDTest.

Create Site Server Groups and Users

1. In the Site Server MMC, right-click Membership Directory Manager, and then click Properties.
2. Type the server name and port of the LDAP instance, and then click OK.
3. Click Log in Anonymously, and then click OK.
4. In Membership Directory Manager, right-click ou=Groups, point to New, click Group, and then add a group named WebDev.
5. In Membership Directory Manager, right-click ou=Members, point to New, click User, and then add a user named ViDev.
6. Right-click the newly created user, and then click Properties.
7. On the Attributes tab, click Add Attribute, and then click user-password. Under the value, type the password (you can use "password").
8. On the Groups tab, click Add, and add the WebDev group.

On the Client Computer, Use Visual InterDev to Create a New Web Site on the Server Computer

1. From the Windows Start menu, point to Programs, and start Visual InterDev.
2. From the File menu, click New Project.
3. On the New tab, click the New Web Project icon.
4. Note the name and physical location for the new project that you are creating, and then click Open.
5. In the drop-down list box, set the name of the server to the name of the new Web site that you created previously. For this example, it is "ServerName:8085".
6. Leave the working mode check box set to Master mode, and click Next.
7. Select the option to Connect to an existing Web application, select <Root Web>, and then click Finish.
8. From the Project menu, click Web Project, and then click Web Permissions.
9. Under Groups, add in the Site Server group that contains your logon information with administrator privileges, which is Site_PMUsers_WebDev in this example.
10. Close InterDev and click Save All.

Configure the New Web Site

1. In the Site Server MMC, under IIS, right-click the new Web site, Debug. Point to All Tasks, and then select Membership Server Mapping.
2. Map it to VIDTest.
3. Right-click the Web site again, and then click Properties. Under Membership Authentication, select only Allow Anonymous and Other Password Authentication/Clear Text.
4. In the Web site Properties, on the Home Directory tab, click Configuration. On the App Debugging tab, select both debugging flags.
5. Also on the Home Directory tab, set Application Protection to High (Isolated).(Execute should be Scripts only.)
6. Click OK.

Set up DCOM

1. From the Windows Start menu, point to Settings, click Control Panel, and start the Add/Remove Programs utility. Make sure that Visual InterDev Server and Remote Machine Debugger both appear. If they do not, install the Visual InterDev Server Components from Visual Studio CD-ROM 2 or Visual InterDev CD-ROM 1 by running Setup.exe from the Vid_ss folder. For additional information on what is installed by the Visual InterDev Server Components, click the article number below to view the article in the Microsoft Knowledge Base:

   248016 INFO: What Is Installed with the Visual InterDev Server Components

   You can install the Remote Machine Debugger by running Setup.exe under Scrpt_ss on disc 2 of Visual Studio or disc 1 of Visual InterDev.
2. From the Windows Start menu, click Run, type dcomcnfg, and then click OK.
3. On the Applications tab, click Catalog Class, and then click Properties.
4. On the Security tab, select the options Use Custom access permissions and Use custom launch permissions, and add the following users by clicking the Edit button. These users should have "allow access" permissions in both the access and launch permissions:

   Administrator Administrators Interactive System your domain account DebugUser account (if you created one in step 1D)

5. On the Identity tab, click the interactive user.
6. Click OK.
7. Repeat these steps with the Machine Debug Manager entry on the Applications tab.
8. Click OK to close the Distributed COM Configuration Properties dialog box.

Configure the Microsoft Transaction Server Component

1. From the Windows Start menu, point to Programs, point to Administrative Tools, and then click Component Services.
2. Click to expand the Computers, My Computer, and COM+ Applications nodes. Right-click the corresponding package. For example, IIS-{Debug//Root}.
3. On the Identity tab, click This User, and change the user to either your domain account or the DebugUser account (depending on whether your computers are on the same domain or not).
4. Click OK, and reboot the server so that the DCOM changes take effect.

Manually Debug in Visual InterDev

1. Open Visual InterDev on the client, and open the DebugWeb project.
2. When you are prompted to log on, log on with your Site Server credentials. For example:

   USER: ViDev
   PWD: password

3. Add an Active Server Pages (ASP) page (Page1.asp), and insert this code:

   <%
   Response.Write "HELLO"
   %>
   					

4. Save the file. Right-click the file in Visual InterDev, and then click View in browser.
5. Keep the Internet Explorer window open.
6. In Visual InterDev, click Processes from the Debug menu.
7. Type the computer name of the server, and then press ENTER.
8. Select Dllhost.exe, and then click Attach. (If errors appear at this time, double check your permissions.)
9. In the running documents window, under ASP, double-click Page1.asp. (If this window is not visible, click Debug windows from the View menu, and then click Running Documents.
10. Set a breakpoint in the document.
11. In the browser, click Refresh. It should stop at the breakpoint.