
BlueDragon 7.1: Deploying CFML on ASP.NET and the Microsoft .NET Framework 40
extensions in a given application pointing to different editions of the .NET framework, which
can cause problems.
Additionally, if you select the 2.0 option (to configure files to be processed by .NET 2.0),
another new option, the Edit Configuration button, is enabled on the ASP.NET tab. This
option opens a useful visual editor for making web.config file changes. Even more powerful, it
reflects any entries that are inherited from high-level web.config files or the global
machine.config, by highlighting the entries in italics. This configuration editor option is dis-
abled if you select .NET 1.1 for the ASP.NET Version drop-down on this tab.
7.2.2 XCopy Deployment
If you would like install and configure BlueDragon.NET and your CFML application on one
machine, and then copy the code (and the BlueDragon engine) to another machine, you can do
that with just a little effort. This is often called “xcopy-style” deployment.
Of course, in order to redeploy BlueDragon and your application on another machine, you must
obtain a license for that additional deployment. Fortunately, New Atlanta has very compelling
licensing terms for developers interested in redeploying BlueDragon and their CFML applica-
tions. Please contact us for details.
The manual configuration steps in the previous section are the key to this process. If you use the
fourth (Single Virtual Directory) option of the installer, to install and configure an in-
stance of BlueDragon into a single virtual directory, that directory will contain all the compo-
nents needed to run your CFML application on any box that has the same edition of the .NET
Framework and the Visual J# runtime which were implemented on the original box.
You can then copy that single virtual directory to another server (before or after making changes
in the BlueDragon admin console).
The only manual step you will need to perform on the destination box is the configuration in IIS
of the extension mappings for CFML files. The BlueDragon installer will have done that on the
box where BlueDragon was installed, but you will need to make those changes on the destination
box.
It’s possible to automate the process of implementing those extension mappings, using any of
several mechanisms for scripting the configuration of IIS. Examples of tools and documentation
include the following:
Automating Administration for IIS 5.0
http://technet.microsoft.com/en-us/library/bb727082.aspx
IIS Programmatic Administration Reference
http://msdn.microsoft.com/en-us/library/ms524713.aspx
A Free Tool for Configuring .NET Web Applications
Comentarios a estos manuales