tag:support.appharbor.com,2010-11-23:/discussions/problems/195-routing-and-content-directoryAppHarbor: Discussion 2018-10-19T03:06:11Ztag:support.appharbor.com,2010-11-23:Comment/54487552011-02-19T08:08:13Z2011-02-19T08:08:13ZRouting and Content Directory<div><p>The issue is most likely that the files isn't part of the
deployed website. You need to include the files in Visual Studio
and in the property pane find the "Build Action" and select the
"Content" option to ensure that the files will be copied.</p>
<p>If you need to define a route to ignore, the proper syntax is
<code>"Content/{*pathInfo}"</code>, but you shouldn't need this
unless the <code>RouteExistingFiles</code> property is enabled.</p></div>tttag:support.appharbor.com,2010-11-23:Comment/54487552011-02-19T14:27:52Z2011-10-18T16:23:45ZRouting and Content Directory<div><p>But I am pushing the whole repository. Why would it need to be
in the project file for it to be pushed/recognized. This isn't true
in any other situations for resources like this.</p></div>Malliochtag:support.appharbor.com,2010-11-23:Comment/54487552011-02-19T15:30:21Z2011-02-19T15:30:21ZRouting and Content Directory<div><p>The content of the output directory (which is what we deploy to
the<br>
web servers) is generated by msbuild, and the content is decided
not<br>
by what is in the repository, but what is in the project file.</p>
<p>On 19/02/2011, at 06.27, "Eric Sowell"<br>
<a>tender+db2d6f4a9abc82c2e9d9d157a3ceee918ebd6948d@tenderapp.com</a><br>
wrote:</p></div>friismtag:support.appharbor.com,2010-11-23:Comment/54487552011-02-19T16:08:14Z2011-10-18T16:23:46ZRouting and Content Directory<div><p>Well that makes sense. Thanks.</p></div>Mallioch