Note that there are some explanatory texts on larger screens.

plurals
  1. POSharing Assets folder between front end and backend of ASP.NET MVC solution
    primarykey
    data
    text
    <p>I've recently been put in charge of finishing a project that one of our former developers began building.</p> <p>Basically what I'm trying to do is set up a path to a shared assets folder that will contain images to be shared and accessed via both the front and back ends which sit on the same domain.</p> <p>The back end has the functionality to upload images to this shared folder to be displayed on the front end.</p> <p>There are multiple environments - localhost , staging and the live site itself.</p> <p>The previous dev created a Paths class to handle this however it seemed to duplicate the assets from the backend to the front end.</p> <p>So the path I want to set is for the assets root directory which would be;</p> <ul> <li>localhost/sitename.com.au/Assets</li> <li>staging.sitename.com.au/Assets</li> <li>sitename.com.au/Assets</li> </ul> <p>The problem is that if I use the ~/Assets it stays on the subdomain level and I need it to go up a level to the site root (see below)</p> <p>Here's the current url structures:</p> <p><strong>LOCAL DEV</strong></p> <ul> <li>localhost/sitename.com.au/Front-End Solution</li> <li>localhost/sitename.com.au/System.Administration Solution</li> </ul> <p><strong>STAGING (TEST SERVER)</strong></p> <ul> <li>staging.subdomain.sitename.com.au</li> <li>staging.admin.sitename.com.au</li> </ul> <p><strong>LIVE</strong></p> <ul> <li>subdomain.sitename.com.au</li> <li>admin.sitename.com.au</li> </ul> <p>I'm only relatively new to this so any help is appreciated.</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.
    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