I'm also interested in this. Anyone have a nice solution? Thanks /Tobias

Try this: UnifiedFile file = UnifiedFile.Get("/upload/myfile.txt"); string path = Server.MapPath(file.Path);

Thanks René, but unfortunally it didn't work (for me anyway).

This depends on the file system. If this is a path located under the siteroot (as /upload does by default), it should work. If it is a versioned file system for an example, the file does not exist on disk with the name you see in the file explorer in EPiServer. To complicate things even more, the file might not exist on disk at all. It might be stored in a database, in SharePoint or somewhere else if you've created your own virtual file system. To make sure you do this 100% correct, you actually need to stream the file to disk (if FastSend cannot accept the file as a stream), and then do a MapPath on that. For the virtual file systems that store the file outside of the webroot - but on disk, you could find the root of the virtual file system beeing used, and use that with the relative path of the file, and find the physical path to the file on disk. /Steve

Hi Steve. Thank you for your answer. Do have an example on this matter? I am using the virtual file systems that store the file outside of the webroot, but on the harddisk. Could I use the GetFile on the relative path, and by that getting the physical path of the file? BR, Tore Gjerdrum

The GetFile only give you the UnifiedFile instance, which does not have that information directly (that would break the Unified File System (UFS) architecture :-) ) The underlying provider does however have this (the NativeFile) in your case. For a database provider this will (as I've said before) not work, as the file probably will never hit the server hard drive on the way to the client, everything will happen in memory. As a side effect of the architecture, and the very notion that everything is virtual, that the files being downloaded might never be stored on disk - led to a rather nasty problem. Downloading several BIG files simultaneously would consume large amounts of memory in you asp.net process as the file would be loaded into memory and then streamed to the client. To get around this, the UFS architect added an interface called IFastFileDownload, which the different file providers could implement. It has one method: string GetFullPath(); By having the full path to the file on disk, EPiServer can hand over the streaming task to IIS, which is much more efficient, and will not consume large chunks of memory. IIS will stream the file in blocks, and in contrast, will only have to allocate a small amount of memory for each block. Fortunately, this interface is exactly what you need. As your initial task is to offload the download of large files to another process, you should make sure that the ASP.NET process never needs to load these into memory. By looking for this interface, you actually accomplish both tasks (getting the physical path, and ensuring no one puts large files in non-physical file systems.) On to the code: string path = "/demo/myfolder/mytext.txt"; UnifiedFile file = UnifiedFileSystem.GetFile(path); IFastFileDownload filedownload = (IFastFileDownload)file.Provider; string physicalPath = filedownload.GetFullPath(); Response.Write("Path is: " + physicalPath + "
"); will display: Path is: C:\Inetpub\FileSystem\demo\myfolder\mytext.txt on my box. /Steve

Thanks Steve! Works perfect. /Tobias

Hi Steve. Thank you! Works great!! /Tore