Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>We made a really in-deep analysis two years ago (2010) betweeen NHibernate, EF and Llblgen and chose the last one. We definitely think we made the right decision.</p> <p>Llblgen Pro is a gorgeous &amp; mature ORM (Entity FW needs to evolve yet: direct m:n, enum, inheritance...). Easy to use both model and database first without XML to see, just a good graphical designer. </p> <ul> <li>Highly efficient: get only the columns you need ... or use TypedList to get commonly used joined/grouped columns ... or map your views with TypedViews, or map your retrieve Store Procedures ...or use ad-hoc queries. You could even create some templates mapping your own POCO (TypeValue) and call SQL directly!!! (we haven't needed to go so far)</li> <li>From the designer, use its own framework, or NHibernate or Entity Framework, or LINQ to SQL</li> <li>Quite a lot of functionality you'd miss once you've decided to go into production (prefetch, transactions, databinding helpers, paging, (de)serialization, customization (properties, dependency injection, authorization, auditing, ...)</li> </ul> <p>...but it is much more: a great model designer &amp; template system. </p> <p>From the ORM on:</p> <ul> <li>A good use of custom templates (ex. ASP.Net, MVC, REST or WCF) provides a scaffolding system/common architecture -> allows the less experienced coders to catchup and be more productive. Common solutions are reused (its cost drops down: it's not "code vs. understand &amp; integrate" but "code vs. plug"). Although it's old-fashioned ASP.Net webforms have a look at <a href="http://northwind.angte-demo.com/" rel="nofollow">http://northwind.angte-demo.com/</a> for a feeling of what you can get with the templates. </li> <li>Code for your particular application in VS as usual. If the code is reusable add the code to the template (it usually means changing in a ASP-like file things like "Product" with "&lt;%=Entity.Name%>", not hard staff).</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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