Last post Dec 22, 2010 10:49 AM by aliEinstein
Dec 22, 2010 08:23 AM|aliEinstein|LINK
Project1 = Asp.net pages project (presentation Layer)
Project2 = Data Access Layer
when Project1 is hosted and running smooth, if i have to add few PRIVATE methods into the Project2 and call these methods wihin some of the PUBLIC methods that i know are being called by Project1, should the cahanges apply that i made in Project2?
I did the above, but the new methods were not called. (I think Project1 is still pointing to the old assemblies of Project2)
I am sure if i reubild the Project1, the changes will work.
But if i have to rebuild Project1 after every change i make in Project2, what is the point of having the seperate tier Architecture? I thought the good thing aboutseprate tiers is that one can do as many changes in 1 layer, without rebuilding the other layers
... is that a wrong preception?
Dec 22, 2010 10:17 AM|rareddy|LINK
In Visual Studio you should build your entire solution, and not just Project 2.
When you roll out the compiled version, you'll copy all of the DLLs that changed to your application.
Dec 22, 2010 10:49 AM|aliEinstein|LINK
I dont want to rbuild and deploy Peoject1 every time. (actuallyu in my example i wrote Project 1, its actually 6 Projects presentation projects, and 1 DAL project = total 7 projects) so why should i be rebuilding and deplying all 7 projects , when the change
is meant for only 1?
If there is no other way, is there any way i can copy only the new Dlls, and point Projet1 to the new Dll??? rather than taken all 7 projects to production and redeplying everything again???
ALSO IMP: if there is really no other way of doing this, then what is the use of layered architecture???