Tornado supports all DotNet platforms. Note that WS2003 defaults to DotNet 1.1 while W2000 and XP-Pro has no DotNet installed.  Download the .msi (Full versions) and support files accordingly.

In order to view the Java Applet effects like Charting and validation, the browser must be Java enabled in either Microsoft or Sum flavor but not both. Do 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.

1. Required - Prepare either your W2K workstation or server with SP2+, XP Professional or Windows 2003 server. Check the latest run time system requirements from Microsoft -> http://msdn.microsoft.com/netframework/downloads/howtoget.asp
2. Required - MDAC 2.7+ is required for ASP.NET.
3. Optional - if you are Oracle users, get the OracleClient drivers at this link -
   http://www.microsoft.com/downloads/details.aspx?FamilyId=4F55D429-17DC-45EA-BFB3-076D1C052524&displaylang=en
   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..
4. Optional - If you are using MySQL. In addition to using the ODBC.Net driver check out this url for a .Net MySQL provider -> http://www.einfodesigns.com/default.aspx.
5. Pick a virtual directory to run your ASPdb.Net (Tornado) files. Any existing virtual directory will be ok (e.g. \localhost =c:\inetpub\wwwroot). Unzip the tornado zip files to this selected directory. Note that you should now have a Global.asax file, a Tornado and a bin directory if the unzip is correct.
6. Activate your browser and type 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.
7. The following is the directory structure of Tornado -

Directories	Files
\bin	\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.
\Tornado	This directory is Mandatory and the name must be reserved for Tornado. All your application .aspx files should go into this directory and below.
\Tornado\Jars	All Tornado Gold version Java Applet files
\Tornado\Templates	All Tornado system template files.
\Tornado\Images-Net	All Tornado System image files
\Tornado\Scratch	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.
\Tornado\DB	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
\Tornado\TornadoInfo.aspx	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.

8. The two most important files are the Tornado.DLL 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 the old ODBC Data Source is not applicable any more. Using the UDL file is another alternative but is highly NOT recommended. So, for a while use the Global.asax file to address your datasource. Of course, as always, you can input directory into the dbDSN property.
9. 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.

---

Send comments on this topic.
Copyright 1998-2007 ASP-db