You must have the proper software installed to run the samples. This includes building and registering the Rules COM component. You must also configure Microsoft Internet Information Server (IIS) properly to execute Active Server Pages (ASP) files.
Software Requirements
You must have the following software installed to run this sample:
Exchange Server Machine
Microsoft Windows NT version 4.0 with Service Pack 4
Exchange Server version 5.5 with Service Pack 1
Internet Information Server Machine
Internet Information Server version 4.0 or later.
Collaboration Data Objects version 1.21 (CDO)
Outlook Web Access (OWA)
Rules COM component registered on the system.
Client
Internet Explorer version 4.0 or other version 4 browser.
Building and Registering the COM Component
Perform the following steps to build and register the Rules COM classes.
Open the Rules Visual Studio workspace file, located at
C:\Mssdk\Samples\Dbmsg\Exchange\Ruleasp\Rule.dsw.
From the Build menu, select the desired Active Configuration.
Select Build->Build Rules.dll (F7)
The COM component is automatically registered for you after the DLL has been built. No further steps are required to run the sample on the machine where you built the project. If you want to run the sample on another machine, you must register the COM component on that machine.
To register the Rule COM component on another machine, perform the following steps:
Copy Rule.dll to a directory in your path on the other machine.
Run RegSvr32 Rule.dll at a command prompt. This step registers the component (COM classes, interfaces, type library) on the computer.
Configuring IIS to Run the Sample
To run ASP samples, perform the following steps:
Start the Microsoft Management Console (MMC) and open the IIS snap-in (typically located at C:\Winnt\System32\Inetsrv\Iis.msc).
Create a new virtual directory and select an alias. Map a physical directory to the virtual directory that contains the files for the sample. These files are typically located in the
C:\Mssdk\Samples\Dbmsg\Exchange\Ruleasp directory.
Select the permissions for the virtual directory. You must allow at least script access to the virtual directory.
Set Directory Security, Anonymous Access and Authentication Control to include either Basic authentication or NT challenge/response.
Select the Documents property page, click Enable Default Document, click Add, and then add Logon.asp to the list. When users access http://machine/RuleASP, they are guided to the logon page.
View the properties for the new virtual directory. Verify that an application with your selected alias is listed under the Application Settings section of the property page. Select Configuration and look in the Application Mappings section to verify that files with the .asp and .asa extensions map to the dynamic link library Asp.dll.