HOW TO: Use Visual Studio to Debug and Manage a Commerce Site That Is Not .NET-Connected (325794)

SUMMARY

This step-by-step article describes how to set up a Commerce Server 2002 site that is not .NET-connected, how to run the site as a project, and how to debug the site by using Visual Studio 6.0.

back to the top

Unpack Your Site

To unpack your Web site, follow these steps:

1. Open Commerce Server Manager.
2. Expand the Commerce Server Manager node.
3. Right-click Commerce Sites, click New, and then click UnPack Site.
4. Click to select a site that is not .NET-connected (for example, Retail).
5. Complete the unpacking process.

back to the top

Create a New Web Project

1. Start Visual Interdev 6.0.
2. On the File menu, click New Project, and then click New Web Project.
3. Give the project a name that is different from the site name that you used in the "Unpack Your Site" section.
4. Verify that Location is not set to wwwroot (you can use C:\Temp).
5. Click to select Master Mode.
6. Click to select Connect to an existing web.
7. Click to select the site that you unpacked in the "Unpack Your Site" section.
8. Click Finish.

back to the top

Turn on Debugging on the Site

1. Open Commerce Server Manager.
2. Expand the Internet Information Server (IIS) node.
3. Expand the Web site that you created in the "Create a New Web Project" section.
4. In the Web site tree, right-click the Commerce site that you created in the "Unpack Your Site" section.
5. Set Execute Permissions to Scripts Only.
6. Click Configuration.
7. On the App Debugging tab, click to select both of the check boxes under Debugging Flags (verify that these options are turned on).
8. Apply the changes.
9. Stop and then restart the Web Service. To do this, follow these steps:
   1. On the Start menu, click Run.
   2. Type IISRESET, and then press ENTER.

back to the top

Run Your Program Through Debugger

1. Start Visual Interdev, and then load your project.
2. Open Default.asp.
3. Add a breakpoint in Sub Main.
4. Click Go.
5. The program starts and then opens to the breakpoint in the Visual Interdev Debugger.

back to the top