问题描述
Project1 = Asp.net页面项目(表示层)
Project1 = Asp.net pages project (presentation Layer)
Project2 =数据访问层
Project2 = Data Access Layer
当承载Project1并使其运行顺利时，如果我必须在Project2中进行更改，那么如果我必须在Project2中添加一些PRIVATE方法并在我知道被Project1调用的某些PUBLIC方法中调用这些方法，?
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?
我做了上面的事情，但是没有调用新方法.(我认为Project1仍指向Project2的旧程序集)
I did the above, but the new methods were not called. (I think Project1 is still pointing to the old assemblies of Project2)
我确定如果重建Project1，更改将起作用.
I am sure if i rebuild the Project1, the changes will work.
但是，如果我在Project2中进行每次更改后都必须重建Project1，那么拥有单独的层体系结构又有什么意义呢?我认为关于单独的层的好处是，一个层可以在一层中进行尽可能多的更改，而无需重建其他层……这是错误的看法吗?
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?
推荐答案
您无需重建它.您可以将新的project2 dll复制到web app \ bin目录，并且如果界面未更改，它将可以使用.一个project1的构建将冗余地重建project1并产生相同的结果，并且还包括最新版本的project2，这也是它起作用的原因.
You don't HAVE to rebuild it. You can just copy the new project2 dll to the web app\bin directory and it will work if the interface hasn't changed. A build of project1 will redundantly rebuild project1 and produce the same result, and also include the latest version of project2, that's why it works, too.
这篇关于Asp.net项目依赖关系问题(分别构建每个层)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！