Re-Building Each Tier
<blockquote>
  <p><strong>Possible Duplicate:</strong><br>
  <a href="http://stackoverflow.com/questions/4518692/asp-net-project-dependency-issue-building-each-tier-seperately">Asp.net project dependency issue (Building each tier seperately)</a>  </p>
</blockquote>



<p>Project1 = Asp.net pages project (presentation Layer)</p>

<p>Project2 = Data Access Layer</p>

<p>when Project1 is hosted and running smooth, if i have to add few PRIVATE methods into the Project2 and call these methods within some of the PUBLIC methods that i know are being called by Project1, should the changes apply that i made in Project2?</p>

<p>I did the above, but the new methods were not called. (I think Project1 is still pointing to the old assemblies of Project2)</p>

<p>I am sure if i rebuild the Project1, the changes will work.</p>

<p>But if i have to rebuild Project1 after every change i make in Project2, what is the point of having the separate tier Architecture? I thought the good thing about separate tiers is that one can do as many changes in 1 layer, without rebuilding the other layers ... is that a wrong perception?</p>
