next up previous contents index
Next: 1.3 Setting up the Up: 1 System Setup Previous: 1.1 Getting the XASP

1.2 Platform Requirements

The platform which the software requires is as follows:

  1. NT Server 4.
  2. NT Option Pack.
  3. SQL Server or other full-feature RDBMS. In principle, any ODBC accessible database should work equivalently, but we will assume you are using SQL Server 6.5.
  4. NT Service Pack 4 or 5. I believe 5 is the last service pack for NT 4.
  5. Visual Studio 6. There are at least 2 service packs to this. This package assumes use of the VisualInterdev component, and I believe installation of VisualBasic may be necessary for all libraries needed for the AnyFront utility to be present.
  6. Office Suite (97). I have the the developers edition and the ODE tools installed, but I don't believe this is necessary. The AnyFront utility is distributed as a .MDE file and requires Access '97. I was unable to get the MS distribution mechanism that was supposed to create a distributable package to work, but the .MDE app works in any system with all items above installed. So far as I know, Access 97 is the only component in this list which can't be replaced by a later version.
  7. ActiveState Perl. Current version at this writing was 522. It is freely available from the link on the download page.

Three actual bundled MS are the ones used in the XASP development environment: Back Office Server 4, Visual Studio 6, and Office 97 Professional edition.

After installing the above you should also install the XASP Libraries, which the self-extracting download zip will do automatically by running regsvr32.

A production environment may of course put different components on different machines, and an individual machine will not need to have all of the above. I recommend you do have all of the above on a development machine however. An exception is the database, which can easily be on a seperate server. I've found that the hallmark of a correct installation is the relatively seldom observed ability to run the VisualInterdev debugger.



juan@acm.org