We're developing DNN skins, and we want to develop then in a different folder than DNN is looking for them, so they can be developed outside the DNN codebase.
Development Folder: C:\TFS\{product}\{branch}\source\Skins
Original DNN Folder, now a virtual directory in IIS: C:\DNNEvoqContent\Portals\_default\Skins
In IIS, we've set the \Portals_default\Skins folder to be a virtual directory pointing at the development skins folder. However, DNN doesn't read the virtual directory and work its way to the new skins folder; it looks for the exact path on the hard drive, which doesn't exist.
Is there a way to get DNN to use virtual directories for skin files? Note: This is only in the development environment.
