Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
P

Philip Brockmeyer

@Philip Brockmeyer
About
Posts
1
Topics
0
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Is it time for EF or maybe...
    P Philip Brockmeyer

    My preference is to use NHibernate + Fluent NHibernate. There is a pretty steep learning curve, but the functionality, maturity, and community support is second to none. The important thing to keep in mind when using an ORM is that to get value out of it you should really be using a presentation pattern that separates business objects from presentation/view logic (Model-View-Controller, Model-View-Presenter, Supervising Controller, etc...). Given a separation of concerns using an ORM in a web application shouldn't give you any more grief than using an ORM in a desktop application. For NHibernate you'll have to keep the session factory in ASP session state, but there are articles on the internet available to help you out with this.

    The Lounge asp-net csharp visual-studio wpf com
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups