Home ›
All Tags » architecture » classes (RSS)

Browse by Tags

Related Posts

  • Lazy Load Pattern and Circular Reference Problem

    I have my project set up as above (please ignore the BusinessFacade library). I have these business objects/entities: Customer Delivery Address Card Details Email Preferences Now a Customer has 1 or more Delivery Addresses . Customer Class: Public Class Customer Private _DeliveryAddresses As List( Of...
    Posted to Architecture (Forum) by scott@elbandit.co.uk on 08-24-2007, 12:00 AM
    Filed under: N-Tier, Profile, 3tier, 3-Tier Architecture, 3-tier programming, architecture, assembly, Basic Architecture Design, Best Practices, bll, business, business logic layer, Class Design, classes, dal, design, design pattern, layered architecture, Lazy Load Pattern, ASP.NET Architecture

  • Good Design? - Pro ASP.NET 2.0 E-Commerce in C# 2005 by Paul Sarknas

    has any body read this book? If so could you answer a few questions. What is the advantage of using the LittleItalyVineyard.DataAccess.StoredProcedure class to hold the names of the SP's? In the DAL the author uses a class for each data acess call (example LittleItalyVineyard.DataAccess.Select.AddressSelectData...
    Posted to Architecture (Forum) by scott@elbandit.co.uk on 06-06-2007, 12:00 AM
    Filed under: ntier, N-Tier, OOP, .NET, .net 2.0, 3tier, 3-Tier Architecture, 3-tier programming, architecture, Basic Architecture Design, Best Practices, bll, business logic layer, C#, Class Design, classes, datalogic layer, design, design pattern, design pattern interface usercontrol, entity, Patterns & Practices, ASP.NET Architecture

  • Is this the Factory Pattern? Abstract Class, Class libraries

    hello I would like some help, I am designing a system and would like to know if I have the basics before I get to far into the project. Could you have a look at my project solution below and let me know what you think. Many thanks Scott. I have a simple test project set up like so: the class listing...
    Posted to Architecture (Forum) by scott@elbandit.co.uk on 05-16-2007, 12:00 AM
    Filed under: architecture, Basic Architecture Design, bll, business, business logic layer, Class Design, classes, dal, design, design pattern, interface, inheritance, Patterns & Practices, ASP.NET Architecture

  • Entity based O/R mappers vs. Domain based O/R mappers and other Entity/Domain Model comparisons

    I came accross an article on Frans Bouma's Blog ( http://weblogs.asp.net/fbouma/archive/2004/10/09/240225.aspx ) that explained how the "type" of design model an O/R mapper follows can greatly influence the way your application is written. Now, initially the statement that the foundation of an application...
    Posted to Architecture (Forum) by meppum on 01-31-2007, 12:00 AM
    Filed under: N-Tier, O/R Mapper, O/R Mapping, architecture, bll, classes, dal, Data modeling, design pattern, database object, entity, ORM, reporting comparison

  • Re: Domain Model Example Critique

    Here is my opinion about all of this: The root namespace contains a classes that implement Fowler's DomainModel domain logic pattern (not just data transfer objects - also may contain validation methods and domain-specific functions). but the DomainObjectBase is this layer's supertype and can't belong...
    Posted to Architecture (Forum) by kejroot on 12-15-2006, 12:00 AM
    Filed under: MVC, O/R Mapping, architecture, bll, Class Design, classes, dal, design pattern, entity, OOP, ORM

  • Domain Model Example Critique

    Please critique the (fictious and incomplete) code below. I would like advice on how to make the code into more of a standard architecture or pattern. The example is a registration system where a person is registering for an event. I've been programming for a couple of years now and I've been learning...
    Posted to Architecture (Forum) by pseudozero on 12-11-2006, 12:00 AM
    Filed under: architecture, classes, dal, entity, OOP
Page 1 of 1 (6 items)

Contact | Advertise | Issue Management by Axosoft's OnTime | Running IIS7
All Rights Reserved. | Terms of Use | Trademarks | Privacy Statement
© 2010 Microsoft Corporation.