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

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 56
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 48
BlueDragon 7.1: Deploying CFML on ASP.NET and the Microsoft .NET Framework 44
several ways to make it know how to process ASP.NET pages. If IIS is not installed when .NET
is installed, these required changes are not made.
A simple way to determine if this is the problem is if you observe the extension mappings for
your web site or directory. If you find that CFM file extensions are mapped to the aspnet_isap.dll
(see sections 6.4 and 7.2.1) but there are no file extension mappings for ASP.NET pages (such as
aspx, asmx, and ascx files), .NET was installed after IIS and these and other needed settings
were not properly configured by the .NET installer.
The problem (and suggested solution, which involves running a .NET command line utility
called, aspnet_regiis.exe) is discussed in the following Microsoft Tech Notes:
After resolving this, and ensuring that an ASPX page runs (see Section
http://msdn.microsoft.com/en-us/library/k6h9cz8h(vs.71).aspx
2.1.1), try running your
CFML pages. Depending on your resolution to the problem, you may need to manually imple-
ment the mappings required for CFML pages (as discussed in section 7.2) or uninstall and reins-
tall BlueDragon and let its installer apply the needed changes.
8.1.3 CFML Pages Were Running But Have Stopped
If you have CFML pages that were running but they suddenly stop (fail to respond), the .NET
Framework or the web application in particular may have become unstable and an unexpected
error has arisen.
The most expedient solution may be to simply restart the .NET web application, as discussed in
section 7.17.1. If this problem persists, please contact us for further assistance.
8.2 Admin Console Changes Are Not Taking Effect
If you’ve made a change in the BlueDragon admin console and it doesn’t appear to be taking ef-
fect, the problem may be in your using the incorrect admin console. A common example of this
is a “datasource could not be found” error.
Recall that BlueDragon.NET offers a separate BlueDragon admin console per web site or virtual
directory or directory declared in IIS to be an application, as discussed in section 5.1.1. So if you
define a datasource in one admin console (such as that for the web site), but you execute code in
a virtual directory or a directory declared in IIS to be a web application, the datasource will not
be found. You must ensure that you configure the appropriate Admin console for your CFML
code.
The following CFML code will report the .NET web application context path and physical doc-
ument root for pages processed in the directory where the code is executed:
<cfobject action="create" type=".net"
class="System.Web.HttpRuntime" name="rt">
<cfdump var="#rt.get_AppDomainAppVirtualPath()#"><br>
<cfdump var="#rt.get_AppDomainAppPath()#"><br>
Vista de pagina 48
1 2 ... 44 45 46 47 48 49 50 51 52 53 54 55 56

Comentarios a estos manuales

Sin comentarios