HowTo:Get Started with RADF?
From DocR21
| ||
Contents |
Prerequisites
The following table provides a list of prerequisites for RADF.
Note: Some of the listed components are optional and are not mandatory for working with RADF.
| Product | Version | Location | Required |
|---|---|---|---|
| Visual Studio 2008 | SP1 | Contact your IT Dept | YES |
| .NET Framework | 3.5 SP1 | Microsoft Web site | YES |
| ACIS | R20 SP1 | Spatial Download Web site | YES |
| HOOPS | 18.0 | Spatial Download Web site | YES |
| InterOp | R20 SP1 | Spatial Download Web site | Optional |
| Advanced Covering | R20 SP1 | Spatial Download Web site | Optional |
| Defeaturing | R20 SP1 | Spatial Download Web site | Optional |
| 3D Mesh | R20 SP1 | Spatial Download Web site | Optional |
| Kinematics | R20 SP1 | On Request | Optional |
| GA Bridge | R20 SP1 | On Request | Optional |
Obtaining RADF Source Code
Download the RADF source code using either of the following options:
- ZIP Packages
- The PRODUCTION version of RADF is available as a ZIP package. This package can be downloaded from the Spatial Downloads Web site.
- Subversion Server
- The Subversion server provides access to the CURRENT version of the RADF source code.
Note: This version contains the latest features that are updated periodically by Spatial Developers.
Note: This version is not fully-tested. Hence, it may be less stable as compared with the PRODUCTION version of the RADF source code.
Refer to HowTo:Get RADF Source Code from Spatial's Subversion Server? for instructions on obtaining RADF source code from Spatial's Subversion server.
Editing Batch Files
SpaDotNET
The SpaDotNET Solution includes two batch files. These files are available under the SpaDotNET folder.
- SetEnvSpaDotNET.bat
- This file is responsible for setting up the environment variables for SpaDotNET based upon input arguments. This file works out-of-the-box for any computer and any configuration; it does not require any further modifications by the application developer.
- StartSpaDotNET.bat
- This file supplies the input arguments to SetEnvSpaDotNET.bat.
- The list of input arguments is as follows:
| Parameter | Description | Expected Value |
|---|---|---|
| param1 | Operating System | 32 or 64 |
| param2 | Configuration | DEBUG or RELEASE |
| param3 | RADF Home Directory | Example: C:\RADF |
| param4 | ACIS Path (A3DT) | Example: C:\Progra~1\SPATIAL\acisR20 |
| param5 | ACIS Configuration (ARCH) | Example: NT_VC9_DLLD |
| param6 | HOOPS Path (HOOPS_INSTALL_DIR) | Example: C:\Progra~1\HOOPS-1800_VS_NET_2008 |
| param7 | HOOPS Configuration (HOOPS_ARCH) | Example: nt_i386_vc90d |
| param8 | InterOp Path (X3DT) | Example: C:\Progra~1\SPATIAL\iopR20 |
Note: If default path names were used during the installation of required components, then no modifications are required to StartSpaDotNET.bat.
Note: If custom path names were chosen during the installation of required components (such as ACIS and HOOPS), then StartSpaDotNET.bat must be edited.
RADFApp
The RADFApp Solution includes two batch files. They are located in the RADF Folder.
- SetEnvRADFApp.bat
- This file is responsible for setting up the environment variables for RADFApp based upon input arguments. This file works out-of-the-box for any computer and any configuration; it does not require any further modifications by the application developer.
- StartRADFApp.bat
- This file supplies the input arguments to SetEnvRADFApp.bat.
Note: The list of input arguments is the same as the list for SpaDotNET.
Note: If default path names were used during the installation of required components, then you do not need to modify StartRADFApp.bat.
Note: If custom path names were chosen during the installation of required components (such as ACIS and HOOPS), then StartRADFApp.bat must be edited.
Obtaining Licenses
Note: For application developers with full-access privileges to the Source Code repository, the licenses are automatically included. No modification and/or additional work is required. This section can be skipped by application developers having full-access privileges.
Refer to HowTo:Setup the required Licenses for RADF? for instructions on how to set up the required licenses for RADF.
Building and Running RADF
The RADFApp Solution has dependencies on the SpaDotNET Solution. Hence, SpaDotNET must be built before building the RADFApp Solution.
To build and run RADFApp, follows these steps:
- Browse to the SpaDotNET sub-folder in Windows Explorer.
- Double-click StartSpaDotNET.bat. This opens the SpaDotNET Solution in Visual Studio.
- Build the SpaDotNET Solution. The Solution should build without any errors.
- Note: If the InterOp and/or Kinematics components are not installed, their associated projects will not build. These projects are optional. The rest of the libraries are independent and will work fine.
- Browse to the RADF folder in Windows Explorer.
- Double-click StartRADFApp.bat. This opens the RADFApp Solution in Visual Studio.
- Note: While opening the RADFApp solution, an error message may pop up. This error message is a notification that certain plug-in projects are missing. These projects are optional. The rest of the application will work fine without these projects.
- Build the RADFApp Solution. The Solution should build without any errors.
- Run Project RADFApp. The RADF Application Window appears on the screen.
Note: You may close the Visual Studio Window for SpaDotNET after building the SpaDotNET Solution. Keeping it open is optional.
