The Server.MapPath method slightly shows down the execution of your ASP scripts, because IIS has to access some internal variables. For this reason you should try to avoid it if possible. In other words, you should code absolute physical paths in your ASP code, instead of using virtual paths that you then have to convert to a physical path using Server.MapPath.
For example, instead of the following code:
Dim fso, tsSet fso = Server.CreateObject("Scripting.FileSystemObject")Set ts = fso.OpenTextStream( Server.MapPath("/textfile.txt") )...
you should use:
Dim fso, tsSet fso = Server.CreateObject("Scripting.FileSystemObject")Set ts = fso.OpenTextStream( "c:InetPubwwwroot extfile.txt" )...
The problem, of course, is that using physical paths makes it difficult to move your site to another machine, such as when you move your local web site to the production server. A simple workaround, that avoids the overhead of using MapPath but keeps most of its flexibility, is to store the application’s root path into an Application variable, and then use it to build absolute paths. For example, you might set this variable in Global.asa:
' in the global.asa fileSub Application_OnStart() Application("RootDir") = "C:InetPubYourSiteDir"End Sub
and use it elsewhere:
' in any other ASP fileDim fso, tsSet fso = Server.CreateObject("Scripting.FileSystemObject")Set ts = fso.OpenTextStream( Application("RootDir") & " extfile.txt" )
Using this approach, you’ll have to modify only global.asa when moving to another physical location. Even better, you can retrieve the site’s root directory dynamically, so that you don’t even have to modify global.asa:
SUB Application_OnStart ' store the application's root path, whatever it is Application("RootDir") = Server.MapPath("/")END SUB