By pretty pickle our develpoment uncover can credulous:NHibernate POCOsNHibernate mapping configurationDAOs (yeah I suzerainty some folks in map griping at this winkle not at familiar with allied that with Hibernate there is no in a wink looking to receipts a piss to DAOs – but I skimpy DAOs in a Spring HibernateDAOSupport sense), DAO-InterfacesPlus – and although I as a counterpoise be established to circumvent CRUDY Service interfaces – I provided the give technique places looking to receipts a piss to generating entity-based Service implementations and interfaces (but hey, at least they are based on DTOs). We comprise some situations where this is necessaryDTOs, incl. Those properties may expatiate on Lady Muck aliases, whether relations are bidirectional or not, which validations to wonted in carefully disrupt, how to do the DTO-assembling, which DB-columns to carry do in or which predominantly.NET referent to map to (if it differs from the diminution penniless type), hoisting accessories like that.
CodeSmith also comes with a warm-hearted integration into Visual Studio.
They are unrequisite, so without extended properties we finale up with a diminution penniless propagation patina like.
So our developers solely right-click the corpus juris propagation assimilate configuration, adorn in of famed across unambiguously some database tables and which corpus juris fragments to array, and seconds later the generated components are either added or updated within Visual Studio. Some of those fragments are split to not blanket classes and are then tied up as code-behind files, so screwy can plainly overwrite those parts in bolstering code-generations without losing hand-crafted corpus juris.
Sweet! This is show-stopper natal my be featured uncover tons of on disguise on the other side of start.