You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are running into an issue using Cassette with asset bundles located in a Virtual Directory set up in IIS (We have Cassette up and running without Virtual Directories btw and it works great!).
Here is an example of our current setup. Each site directory is set up as IIS application as normal.
Site location on disk: c:/sitefiles/sitename
CMS admin portal location on disk: c:/sitefiles/sharedfiles/adminportal
The CMS admin portal is setup in the IIS as a virtual directory for each site. sitename.com/adminportal
-or- c:/sitefiles/sitename/adminportal
So a Cassette reference in /adminportal/Login/Default.aspx looks like this
Files and bundles outside the Virtual Directory work fine.
Bundles.Reference("/js/sampleScript.js");
So when I copy the admin files directly into the site directory everything works fine. But when outside of the site files and setup as a virtual directory it no longer works.
Obviously we could duplicate the admin portal on each site, but that really puts a kink in our upgrading system.
Just looking to see if anyone else has had this problem. I've found a few that look similar-ish, but not quite.
#138 (perhaps the same issue, but not well explained, hopefully I've done a little bit better of a job... :) #209 #234
The text was updated successfully, but these errors were encountered:
Cassette doesn't work with ASP.NET's "virtual files". It only looks at the physical file system.
In the past, when wanting to share some common bundles between multiple sites, I've created symbolic links (via mklink in cmd) to the common bundle directory. This way they appear to Cassette as just another directory in the file system.
We are running into an issue using Cassette with asset bundles located in a Virtual Directory set up in IIS (We have Cassette up and running without Virtual Directories btw and it works great!).
Here is an example of our current setup. Each site directory is set up as IIS application as normal.
Site location on disk: c:/sitefiles/sitename
CMS admin portal location on disk: c:/sitefiles/sharedfiles/adminportal
The CMS admin portal is setup in the IIS as a virtual directory for each site.
sitename.com/adminportal
-or-
c:/sitefiles/sitename/adminportal
So a Cassette reference in /adminportal/Login/Default.aspx looks like this
Therefore when Cassette references the bundle we are getting the following error.
Files and bundles outside the Virtual Directory work fine.
So when I copy the admin files directly into the site directory everything works fine. But when outside of the site files and setup as a virtual directory it no longer works.
Obviously we could duplicate the admin portal on each site, but that really puts a kink in our upgrading system.
Just looking to see if anyone else has had this problem. I've found a few that look similar-ish, but not quite.
#138 (perhaps the same issue, but not well explained, hopefully I've done a little bit better of a job... :)
#209
#234
The text was updated successfully, but these errors were encountered: