Home ›
All Tags » architecture » entity (RSS)

Browse by Tags

Related Posts

  • Your opinion to the domaindriven architecture

    Hello, i want to ask you to post your opinion to the code below. I try to use the MCV-Architecture and seperate the different layers. It is a complex Webapplication, where Customers can make Reservations for different Places and organize Events. I will have about 50 Entityclasses in the end. The application...
    Posted to Architecture (Forum) by cptOneEye on 09-22-2008, 12:00 AM
    Filed under: MVC, O/R Mapper, architecture, domain, entity

  • Populating an entity using DataColumnMapping

    Hello, Currently when I need to populate my business entites I write code similar to: Public Class Person Private _name As String Public Sub New ( ByVal name As String ) _name = name End Sub Public Sub New () End Sub Public Property name() As String Get Return _name End Get Set ( ByVal value As String...
    Posted to Architecture (Forum) by scott@elbandit.co.uk on 02-09-2008, 12:00 AM
    Filed under: architecture, arcitecture, Best Practices, Buisness layer, business, business logic layer, business model, Data modeling, datalogic layer, dataobjects, design pattern, entity

  • Assess .Net Intranet Application

    I am assessing whether a .net intranet application system is of acceptable, reasonable quality. My criteria so far for this is on several fronts: - Architecture (e.g., is the architecture n-tier?) - Is the code easy to maintain? - Has the code been written with reuse in mind, or refactored? - Are there...
    Posted to Free For All (Forum) by dbrook007 on 01-04-2008, 12:00 AM
    Filed under: ntier, partial classes, persist changes, Report Viewer, solution project, system analysis", System Design, Technical Specification, UI Architecture, UI Framework, UI Process Components, VB, VB Class, VB Classes, vb.net, Web Forms, .NET, 3tier, 3-Tier Architecture, 3-tier programming, approach, architecture, Asp.Net 2.0 : java script, ASP.NET 2.0 NET SQL Server 2005 database connection error, asp.net tuning, assembly, authentication, Basic Architecture Design, Best Practices, bug, business logic layer, caching, Class Design, concurrentcy, Consistency in UI, css, CustomErrorPage, DAL exceptions, data access layer, data access object relational mapping, Data modeling, datagrid, datalogic layer, dataobjects, design pattern, Events, Generics, Globalization, database object, xml, entity, IIS, application state management, performance, Exception Handling, Exception Handling Application Block, Exception Handling Application Block Tutorial, ASP.NET Architecture, sql server, OOP, "system Design", arcitecture, business model, data serialization, GridView, Patterns & Practices, N-Tier, optimization, Reflection, web service, ADO.NET, Asp.Net 2.0, assemblies, Data Concurrency, database, http, methods, Website Problem

  • Re: Should i separate my properties and methods within my business entity classes

    I have seen classes implemented with this pattern and in fact the WCF and WebService Software Factory creates these classes into two different projects - your "BusinessEntities" and then your "DataFactory". In my opinion, the way you were doing it is a better pattern with this extra...
    Posted to Architecture (Forum) by david@davidlwalker.com on 07-19-2007, 12:00 AM
    Filed under: web service, .NET, architecture, bll, business, business logic layer, dal, data access layer, web services, webservices, entity, ASP.NET Architecture, OOP, Web, WCF, Patterns & Practices

  • 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

  • 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 (8 items)

Contact | Advertise | Ads by BanManPro | Running IIS7
All Rights Reserved. | Terms of Use | Trademarks | Privacy Statement
© 2009 Microsoft Corporation.