Establishing the Development Environment

Regardless of the development strategy you choose to pursue , you must install ADSI before using any of this text's code in a Windows NT environment.

Note

Windows 2000 includes the latest version of ADSI in the base build and does not require separate installation of the ADSI libraries.

Simply navigate to http://www.microsoft.com/adsi to obtain the ADSI 2.5 installation routine for your operating system and processor architecture.

Note

If you will be running your ADSI scripts from IIS Active Server Pages on Windows NT 4.0, you must also install the ADSI libraries on your Web server(s).

If you are using ActiveX Data Objects (ADO) to query the Active Directory or a native LDAP namespace, you may also want to obtain the latest Microsoft Data Access Components (MDAC) release from Microsoft at http://www.microsoft.com/data.

If you want to develop your code as COM objects, you must install Visual Basic on your development workstation. Although VB5 fully supports the creation of COM objects, VB6 offers several enhancements to the language and integration with Microsoft Transaction Server (MTS).

Note

You must use the Visual Basic Professional edition or the Enterprise edition to create COM objects. Visual Basic Learning Edition does not include the capability to compile native code, which is essential to COM server development.

To create COM components for Alpha systems, you must compile your objects using the Enterprise version of Visual Basic on an Alpha development workstation.

To implement code directly in an ASP, you simply need a text editor (such as Notepad), IIS 3.0 or higher, and ADSI installed on the Web server.

Note

For examples of each chapter's Visual Basic code segments in VBScript ASP format, refer to the Code Reference Library available in Appendix A, "VBScript Code Reference" and in electronic format from this book's Web site, http://www.newriders.com/adsi.

Top