There's
nothing specific to our server in the way in which you use Active
Server Pages. It's just a matter of creating the files and sending
them up to the server. All accounts have Active Server Pages enabled.
Also,
make sure to check the The "Best" ASP
Resource in the World (that's their title). They have a good
collection of step-by-step tutorials on a number of introductory
and advanced topics.
15
Seconds has regular articles on advanced scripting techniques,
focusing on ASP and related items.
Cold Fusion
ColdFusion is included in the Win Pro, Win Commerce & Win Ultra accounts
and is available to other account types as an additional service.
If you haven't yet, check out the
Macromedia products page which includes links to their developer resources,
including the full online documentation for Cold Fusion and some great
resources that are active and prove quite handy in getting a jump on things.
We
have installed a wide selection of Custom
Tags for use in your Cold Fusion pages.
For the complete list of properties and methods, see ObjectReference
Please note that as a security precuation, the following features of
ASPUpload are disabled on our servers: ACL, Directory Listing, File Copy,
Register Server, and Remove Directory.
All perl scripts must have a ".pl" extension. Eg. perlscript.pl will
work where perlscript.cgi will not.
CGI.pm
This perl 5 library uses objects to create Web fill-out forms on the fly
and to parse their contents. It provides a simple interface for parsing
and interpreting query strings passed to CGI scripts. However, it also
offers a rich set of functions for creating fill-out forms. Instead of
remembering the syntax for HTML form elements, you just make a series
of perl function calls. An important fringe benefit of this is that the
value of the previous query is used to initialize the form, so that the
state of the form is preserved from invocation to invocation. [More...]
There are some basic style considerations to be made when creating CGI
scripts in Perl to run on Windows. Please check the
PerlIIS homepages first if you are having problems receiving the proper
behavior from your scripts.
SSI is included in all our Windows 2003 account types. Due to the method
in which SSI is coded into Microsoft Internet Information Server (IIS)
however, no EXEC includes are allowed and will generate errors.
All SSI pages must end with the extension ".shtml", ".shtm", or ".stm"
in order to be handled correctly.
If you're in need of more information, there is a Server
Side Tutorial we've found that may be a good place to start learning
more about them. This tutorial does include information on exec style
SSI's as it's about SSI in general, and not aimed at Windows 2003 specifically.
