What to expect to find in next release 4.0?

Posts   
 
    
gregkuha60
User
Posts: 47
Joined: 23-Jan-2012
# Posted on: 15-Feb-2013 17:26:55   

Hello

I'm trying to find a "roadmap" for llbenpro but can't find. What can we expect to see in the next version 4.0? What are the plans?

Best regards Greger Sander

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 16-Feb-2013 06:44:25   

There are a lot of new features and improvements. Many can be found individually at some threads. However there is not an official list yet about that. Usually each major version has a beta period when all the new functionality is revealed so you can take a closer look. We have to wait a little bit more wink

David Elizondo | LLBLGen Support Team
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39590
Joined: 17-Aug-2003
# Posted on: 16-Feb-2013 11:32:42   

From the top of my head:

  • Full VS.NET integration of designer (2010/2012)
  • Table valued functions, onto which you can map an entity/typedview (designer, runtime) and which allows you to use the function in linq/queryspec as a source of a query (e.g. from c in metadata.Function(a, b) where ... )
  • 50% faster fetches of entities (runtime), also less memory consumption.
  • Query result cache (runtime), which allows you to cache the resultset of a linq/queryspec query (including typedview/list) for a period of time.
  • Data scopes (runtime), which allow you to define a couple of queries and relationships and all data manipulation/refetching of the data inside the scope is managed for you, including cascading deletes.
  • Action hint pane inside the designer what to do next (designer), which lists all the actions related to your last action and the state of the project, helping a lot of users who wonder what to do next or where to find a specific feature
  • Type shortcut aliasing, so you can define e.g. 'EmailAddress' which is a string (150), and you can use 'EmailAddress' as type on a field, which then gets '150' as default length (designer)
  • Row skipping for fetches (runtime), so you can now page with e.g. .Skip(14).Take(3)
  • Inlining valuetypes (designer) for LLBLGen Pro Runtime. This means you can model with valuetypes, e.g. Address with City, Street, Housenr, and at code generation time these valuetypes' fields are inlined so you get e.g. VisitingAddressCity, VisitingAddressStreet... this allows for easier modeling with value types with our runtime.
  • Fetching typedlists with queryspec
  • Full XML serializabillity of all query api elements, including the unit of work. So you can send a UoW to a service using xml serialization.
  • many small enhancements.

Many of these might look small, but they're really not. simple_smile E.g. the query cache + the much faster fetches alone will help a lot. Example: fetching 31,000 entities in v3.5 takes 1200ms, in v4 with caching takes 250ms. VS.NET integration is also huge: you design everything inside vs.net, you have separate tool windows for the designer panes, and when you generate code, the projects are auto-added to your solution. The datascopes will solve a lot of problems for people who create LoB apps with our runtime, as it takes away a lot of work with respect to binding, managing whether an entity has changed, handling save actions, cascading deletes etc. as it simply creates a UoW for you which you can commit and that's it simple_smile

And we're not done developing yet, so more is added before beta starts simple_smile

Frans Bouma | Lead developer LLBLGen Pro
arschr
User
Posts: 893
Joined: 14-Dec-2003
# Posted on: 16-Feb-2013 14:22:30   

Do you expect sql hints to make it?

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39590
Joined: 17-Aug-2003
# Posted on: 18-Feb-2013 09:46:09   

arschr wrote:

Do you expect sql hints to make it?

I tried to add it, but I couldn't make it work. There are a lot of problems, mostly because every DB specifies its hints differently and uses different hints. I first thought I append the list of <table>, <hint> pairs to a list and pass that along to the query engine, but that's not going to work for a lot of hints (only for global query ones). The global ones are already doable (override CreateSelectDQ in adapter, append the hints to the sql statement), it's the other hints that are interesting, e.g. the join hints. It was always awkward to specify, and more awkward to get the hint into the SQL statement, so then there's just 1 thing to do: not do it.

Frans Bouma | Lead developer LLBLGen Pro
Posts: 256
Joined: 05-Jul-2010
# Posted on: 22-Feb-2013 14:12:32   

Any dates yet... I'm curious

thanks

A

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39590
Joined: 17-Aug-2003
# Posted on: 22-Feb-2013 22:13:52   

Initial target was end of february. I still have some workitems to clear so I think it's first week of march. Or thereabout. Close simple_smile

Frans Bouma | Lead developer LLBLGen Pro