LLBLGen Prof Testimonials

[Ayende Rahien]

Hi guys,

I am looking for stories about how you are using LLBLGen Prof.

How it helped you, solved problems, etc...

Thanks in advance,

~Ayende

[Maciej Aniserowicz]

Hi Ayende,
This is not a testimonial per se, but a 'true story'. You can stop
reading now if you are only interested in "why I love llblgen"
replies.
I am implementing a callcenter system that is much more than CRUD and
LLBLGen caused me some memory-related problems. In short: entity
collection that is loaded together stays in memory until ALL of it's
elements are dereferenced, even if I use the "EntityCollection" just
to load them.
Frans helped me resolve this issue (and some other issues, also
related to memory leaks) but the solution is rather ugly. Note that I
am using v2.6, but AFAIK the this behavior has not changed in further
releases. You can see the whole story and the context @ LLBLGen
forums, my problems and Frans's answers will tell you more than I can
do here: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=19232
.

Br/
Maciej Aniserowicz

[Frans Bouma]

> I am implementing a callcenter system that is much more than CRUD and
> LLBLGen caused me some memory-related problems. In short: entity
collection
> that is loaded together stays in memory until ALL of it's elements are
> dereferenced, even if I use the "EntityCollection" just to load them.
> Frans helped me resolve this issue (and some other issues, also related to
> memory leaks) but the solution is rather ugly. Note that I am using v2.6,
> but AFAIK the this behavior has not changed in further releases. You can
see
> the whole story and the context @ LLBLGen forums, my problems and Frans's
> answers will tell you more than I can do here:
> http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=19232
> .

It was indeed a problematic situation, primarily caused by
references inside an entity graph in memory which had to be bi-directional,
but sometimes they didn't.

It's one of the downsides of using object graphs: they have the
aspect to keep things in-memory, and require tht they're treated as a whole.
That's of course not really working out when you want to keep one part but
get rid of the other.

FB