MACROMEDIA COLDFUSION STUDIO 4.5-USING COLDFUSION STUDIO Use Manual page 48

48
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 user may 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 such a scenario, a file that appears to Studio as
X:\App1\index.cfm
Might be viewed by the server as
C:\webprojects\App1\index.cfm
The browser might view it using the URL path
http://215.180.21.1/App1/index.cfm
In order to resolve the communication between ColdFusion Studio and the server, you
need to create a mapping for the App1 directory as follows:
Studio access to a remote server using drive mappings
Studio path
Server path
Browser/URL path
Using UNC paths/Network Neighborhood
Developers can debug code against remote ColdFusion servers across an internal
network. 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 such a scenario, a file that appears to Studio as
\\myserver\webprojects\App1\index.cfm
Might be viewed by the ColdFusion server as
c:\webprojects\App1\index.cfm
The browser might view it using the URL path
http://215.180.21.1/App1/index.cfm
X:\App1\
C:\webprojects\App1\
http://215.180.21.1/App1/