Design decision on class library projects?
It's been mentioned several times in this forum that some of the class library projects that the book refers to are rather implemented as classes in the main project -- for example, the downloaded code does not have a PhilePageBase class library project or a Controls class library project as the book describes.
Instead PhilePage.cs and Navigator.cs are part of ThePhile project (Asp .Net Web Application). And it works fine to do that.
My question is why this difference? Clearly it was a design decision to not have these class library projects (assuming that the downloaded code is more recent). Why that decision? Core is a class library project.
As I rebuild this web site I'm following the downloaded version rather than the book's version.
-Ted
__________________
-Ted
|
Similar Threads
