This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
just an idea; working with named aggregates. i see you specify an aggregate via a string for querying - to match up to the generated aggregate in the LS model. Is there a particular reason you haven't set aggregate names to be generated as either static or const so we can get away from magic strings? The generated code could have something like: Snippet [EagerLoad(AggregateName=MyModelAggregates.MyEntityDetails)] Where the generated code also builds a static class MyModelAggregates. And then for querying I could have: using (var unitOfWork = _context.CreateUnitOfWork()) Strong typing, intellisense, all good... Thoughts? Snippet
|
|
|
Good idea - I vote for this :)
(my 2c) |
|