User Guide

22 Chapter 2 Configuring Browsers and Servers
To resolve the URL paths, you must create a mapping for the App1 directory, as in
the following table:
Using drive mappings
Developers often debug against a remote server across an internal network. In many
cases, they use a network drive mapping.
For example, a developer might have a remote drive X mapped to a network shared
directory \\MyServer\webprojects\ where webprojects is the name of the shared
directory in the network server MyServer.
In this scenario, HomeSite+ for Dreamweaver MX might see a file as
X:\App1\index.cfm, the ColdFusion Server as C:\webprojects\App1\index.cfm, and
the browser as http://215.180.21.1/App1/index.cfm.
To resolve communication between HomeSite+ for Dreamweaver MX and the
ColdFusion Server, you must create a mapping for the App1 directory, as in the
following table:
Using UNC paths and the Network Neighborhood
Developers can debug code against remote ColdFusion Servers across an internal
network using UNC paths. They often use the Network Neighborhood to access a file
on a remote server. For example, a developer might access a file on
\\MyServer\webprojects\, where webprojects is the name of the shared directory in
the network server MyServer.
In this scenario, HomeSite+ for Dreamweaver MX might see a file as
\\MyServer\webprojects\App1\index.cfm, the ColdFusion Server as
C:\webprojects\App1\index.cfm, and the browser as http://215.180.21.1/App1/
index.cfm.
ColdFusion Server and HomeSite+ for Dreamweaver MX on same computer
HomeSite+ path C:\webprojects\App1\
ColdFusion Server path C:\webprojects\App1\
Browser/URL path http://215.180.21.1/
HomeSite+ access to a remote server using drive mappings
HomeSite+ path X:\App1\
ColdFusion Server path C:\webprojects\App1\
Browser/URL path http://215.180.21.1/App1/