Note that there are some explanatory texts on larger screens.

plurals
  1. POCreating symbolic links for IIS7 web environments
    primarykey
    data
    text
    <p>. .</p> <p>We have a growing need where web resources (files, documents, images, etc.) need to be shared between different web environments.</p> <p>I'm looking into setting up symlinks to support this, but I don't know how to set it up. (Or would it be better to set up virtual directories? Part of my question is, what are current best practices to set this up?)</p> <p>For example purposes, assume:</p> <ul> <li>The environment is running on an IIS7 platform, and MUST be in a Windows environment.</li> <li>The shared files need to be maintained using TFS.</li> <li>The web sites occupy different sites on the same IIS instance and reside on the same physical server.</li> <li>The sites are multple web platforms -- for example, one site is ASP.NET, while another is running classic ASP.</li> <li>All sites are under the same corporate umbrella, which is why resources need to be shared.</li> <li>All sites pull data from the same SQL Server database instance.</li> </ul> <p>How would I set up a symlink to support this? Or, for that matter, are symlinks the best way to go about this?</p> <p>Thanks in advance!</p> <p><strong>Edit:</strong> Addendum to the above example: my classic ASP environment can also include ASP.NET virtual subfolders. For example, I can have my domain www.somedomain.com running in classic ASP, but have a subdirectory (www.somedomain.com/dotnetapp) running as an ASP.NET application. The virtual directory used by the ASP.NET must be able to access the same file resources as the classic ASP environment.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload