Asp.net项目依赖问题（大厦每层单独） [英] Asp.net project dependency issue (Building each tier seperately)

问题描述

PROJECT1 = Asp.net页面项目（presentation层）

Project1 = Asp.net pages project (presentation Layer)

Project2的=数据访问层

Project2 = Data Access Layer

当PROJECT1托管和平稳运行，如果我要在一些我知道被称为PROJECT1的公共方法添加一些私有方法到Project2的，并调用这些方法，应该修改应用，我做Project2中？

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，什么是具有独立的三层结构的意义呢？我想过单独层的好处是，我们可以做很多的变化在1层，无需重新构建其他层......是一种错误的认识？

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?

推荐答案

您不必重建它。您可以将新的DLL项目2只复制到Web应用程序\ bin目录中，它会工作，如果接口一直没有改变。一个构建PROJECT1将冗余重建PROJECT1并产生相同的结果，并且还包括项目2的最新版本，这就是为什么它的作品了。

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项目依赖问题（大厦每层单独）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！