Tornado supports DotNet 2.0 platform and users using DotNet 1.1 have to make
a special reuqest to get the 1.1 files. Note that WS2003
includes DotNet 1.1 as default while W2000 and XP-Pro has no DotNet runtime installed. Download the .msi (Full versions) and
In order to view the Java Applet effects like Charting and validation (GOLD
version only), the
not install both Sun and MS JVM.as the combination will yield unstable results.
Install ASP.NET and Tornado is as easy as it could be since the DLL "Hell" is
gone in the DotNet platform. Tornado are be shipped as .MSI and .Zip file. The user is responsible to install the ASP.NET
runtime or development framework.
- Required - Prepare either your W2K or WS2003 workstation or server with
the latest service pack. Check the latest run time system
requirements from Microsoft ->
- Required - MDAC 2.7+ or above is required for ASP.NET.
- Optional - if you are Oracle users, get the OracleClient drivers at this
This MS download links changes from time to time. Search for 'oracle_net.msi
download' in Goggle will usually get the latest link.
You must also have Oracle 8i Release 3 (8.1.7) Client or later installed in
order to use the DotNet OracleClient..
- Optional - If you are using MySQL. You should sue the latest MySqlClient
data connector ->
- Pick a virtual directory to run your ASPdb.Net (Tornado) files. Any
existing virtual directory will be ok (e.g. \localhost =c:\inetpub\wwwroot).
Download the Full version .msi file and start the install to this selected directory.
There will be a lot of files in the setup and only two files are the core
files (.dll and .idx). The rest are supporting files like css, sample db
etc. Note that you should
now have a Global.asax file, a 'Tornado' and a 'bin' directory if the install is
- The following is the directory structure of Tornado -
||\bin\Tornado.DLL resides here (Mandatory). Your Tornado id
file must be saved in this effective bin directory. You can a different effective bin
directories for different projects with a different virtual root and a
different tornado.dll file. All aspx files below the same virtual root will
look for the effective bin of that virtual root.
||Global.asax - This file MUST be in the same level as
the \bin directory. This file is required for SuperLogin operations.
This directory is
Mandatory and the name must be reserved for Tornado. All your
application .aspx files should go into this directory and below.
All Tornado Gold version
Java Applet files
All Tornado system
All Tornado System image
This virtual directory
is Mandatory and must exists and the write privilege must be set for the users of
Tornado. Suggest to have a scheduled bat file to delete all files in this
directory every day. Right click on this scratch folder and assign modify or
full control to the aspnet_wp_account.
All your Local Database
files goes here (Access, Excel, DBase, Csv, Text ..). If you are writing to
the databases in this directory, make sure you assign modify or full control
to the aspnet_wp_account.
|\Tornado\css Location of all
||Skin CSS files
||This is a very important installation test file.
Execute this file will display system and Tornado parameters. An installation
test will also be done and results displayed at the end of the file.
- The three most important files are the Tornado.DLL file, ID file and the Global.asax
file. Read the Global.asax file supplied to you. Modify the datasource to
your server and directory structure. Forget the old ASP "DSN or ODBC" for a
while. All the data connections of ASP.NET is via OleDB and DB Native Clients.
The old ODBC Data
Source is onit's way out.
- The 'Full install .msi file' does not have the latest DLL. The latst
version will be sent to you via email if your maintenance subscription is
active. Whenever there is a new release of Tornado.DLL, just replace the one in
the \bin directory. No stopping or starting of any components is required. Be
aware that when you change an aspx file, it compiles the first time it
executes and it is slow. When you replace a DLL, all the aspx files depending
on that particular DLL file will execute slow the first time.
- To make sur eyour installation is OK, execute http://localhost/Tornado/Tornadoinfo.aspx
or if your project virtual root directory is called 'project' then type
http://localhost/project/Tornado/Tornadoinfo.aspx. This test file will confirm
the entire installation including your Java capable browser. Scan the display
of this information page carefully as it covers all the essentials of your
DotNet server setup.
Send comments on this topic.
Copyright 1998-2007 ASP-db