Note that there are some explanatory texts on larger screens.

plurals
  1. POIdeal .NET Architecture?
    text
    copied!<p>I'm writing this question from the standpoint of an ASP.NET application. However I realize it may be suited to other contexts as well.</p> <p>There are so many approaches to developing the common elements of an ASP.NET website. Here are a few I have come across:</p> <ul> <li>LLBLGen</li> <li>SubSonic</li> <li>LINQ to SQL</li> <li>Entity Framework</li> <li>CodeSmith + .netTiers</li> <li>NHibernate</li> <li>Hand coding DAL/BLL/Presentation</li> </ul> <p>I don't consider myself an expert developer by any means, however I do understand common OOP techniques well, and can get through all my projects just fine. I do however struggle with knowing how to 'architect' a site. By that, I mean, should I use <a href="http://en.wikipedia.org/wiki/Multitier_architecture" rel="nofollow noreferrer">n-tier architecture</a>? Is that still the gold standard and the above tools just utilize that concept? I'm pretty sure I want to hold off on MVC until a future (or final) release. </p> <p>*****Edit: I have removed the portion of the question which deals with patterns (singleton, factory) after having more fully understood the separation of the question. Thank you for all who have answered this part so far, however, my main focus is on the architecture portion.*****</p> <p><em>Edit #2: I changed the title to be more of an agnostic question upon realizing this would apply to more than web-specific architecture.</em></p> <hr> <p><strong>Question:</strong> What steps do I take as a first step, when I have sat down in front of a blank canvas (solution file) with all my pre-written documentation and system requirements in hand ? Where do I go from there?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload