title: How to Keep Ace from Looking for Themes and Modes in Current Directory?
body: <p>I've been working on an MVC web application that uses the Ace in-browser code editor provided by Cloud9.  The ace.js script and a script that sets up ace's editor are both in a ScriptBundle together on my BundleConfig.  The bundle is being loaded perfectly fine.  On my local server, with debug set to true in the web.config, the script worked perfectly fine.  However, after launching to a live server with debug set to false in the web.config, several errors appeared.</p>
  
  <p>After fixing a few minor glitches, there remain two errors that I can't seem to understand the cause of.  These two errors seem very similar, as they are both 404 not found errors for Ace's chrome theme and Ace's HTML mode scripts.  In the script that sets up the editor, they are called as follows:</p>
  
  <pre><code>editor.setTheme("ace/theme/chrome");
  editor.getSession().setMode("ace/mode/html");
  </code></pre>
  
  <p>On my local computer, with debugging set to true, the theme and the mode are set perfectly fine, and everything works as planned.  However, as I've said, on a live server with debugging set to false, therefore minifying all of the scripts in my ScriptBundles, I get a 404 error for both the theme and the mode.</p>
  
  <p>When I pull up the JavaScript Console in Google Chrome, I am told of the two 404 errors.  The funny thing about the 404 errors, is that they are linking to the current directory of the page I'm viewing, then followed by "theme-chrome.js" and "mode-html.js" respectively.  They were never in that directory, and still aren't.</p>
  
  <p>So my question is why do the scripts begin to look in the current directory for their files after being minified?  What can I do to fix this issue so that I can keep them minified, in bundles, and have them work?  Or is there a way?</p>
  
  <p>Thank you for your help ahead of time.</p>