Why doesnt this asp.net Web Application Project compile on change to config?
<p>In a seperate question, yesterday, I was trying to figure out why I had issues with source code pulled from a working site on a server.</p>

<p>The server contains a fully functional website / database (.Net 2).</p>

<p>When I pulled the code down to my Box it wouldnt run. After some head scratching, and liberal use of Reflector on the dll, it became obvious that the source code I had didnt match what was in the bin fodler dlls.</p>

<p>I then noticed that I had Designer.cs files, which means it is a web application project as opposed to a website.</p>

<p>I then created a subdomain on the server, copied the code there and it all worked. So then I changed the web.config file, expecting that to force a recompile and show the same behaviour as I get locally. Only it didnt.</p>

<p>Removing the app.dll's from the bin folder caused an error, but again didnt make the applciation recompile / regenerate dll's.</p>

<p>So I think I have hit a gap in my knowledge. I can change an aspx file and see the change on the site. So I assume that all the code behind was compiled offline, and then uploaded, but the aspx files are still being served as usual html. </p>

<p>So, is this standard behaviour for a web based application as opposed to a website, and if so, is there any way I can make it rebuild on the server to prove to my client that the latest code base isnt on the server and this will be a much bigger job than he is expecting?</p>
