MACROMEDIA COLFUSION MX 7-CFML Guía de usuario descargar pdf (Pagina 40)

BlueDragon 7.1: Deploying CFML on ASP.NET and the Microsoft .NET Framework 35

7 Other Configuration Issues

Following are discussions of various configuration issues related to deploying CFML on .NET.

7.1 Restarting .NET and .NET Web Applications

As discussed in previous sections, your CFML applications become native .NET applications, at

least from the perspective of IIS and .NET.

It may be desirable to restart a given .NET web application, or the entire .NET Framework, such

as after making certain kinds of coding changes or when trying to resolve a problem. Addition-

ally, there are times when the .NET Framework itself may restart itself or a given web applica-

tion. This section discusses both automatic and manual restarting of .NET and .NET web appli-

cations. (Technically, in .NET you stop—or, unload—the application. Then the first request for

an ASP.NET or CFML page will restart—or, reload—the application.)

It’s also important to know the implications of application restarts on your CFML and ASP.NET

code, particularly regarding session variables, as discussed further in section 7.1.3.

7.1.1 Manually Restarting .NET Web Applications

There are several ways to manually restart a .NET web application.

7.1.1.1 Restarting All .NET Web Applications

If you prefer to stop/restart all .NET web applications at once, one option is to simply restart IIS.

From the IIS interface, you can right-click on a computer name, choose All Tasks, then

choose Restart IIS. (You can also simply restart one of the IIS-related services in the Win-

dows Services panel, such as World Wide Web Publishing, which will restart IIS.)

Just be aware that if you want or need to restart just one particular .NET web application, there is

an option for that, as discussed in the next section. Still, if you have only one .NET application

on a site, restarting IIS may be more expedient.

Keep in mind that .NET has many automatic means by which it may restart a given web applica-

tion (discussed later in section 7.1.2). For instance, if any change is made to the central

web.config file, all .NET web applications on the server will be stopped (and restarted on the

next first request).

7.1.1.2 Restarting a Single .NET Web Application

Rather than restart all of IIS, it is often desirable to restart just a given web application. IIS cur-

rently provides no means to stop/restart just one .NET web application. The option provided in

IIS to “stop” a web site only affects the processing of IIS, and not the underlying .NET applica-

tion(s).

The simplest way to manually cause restart of a single .NET web application is to run either a

CFML or ASP.NET page that executes a particular method in the .NET system class which stops

the web app. Here’s an example of one way to call such a method as an ASPX page:

1 2 ... 35 36 37 38 39 40 41 42 43 44 45 ... 55 56

Sin comentarios

MACROMEDIA COLFUSION MX 7-CFML Guía de usuario Pagina 40