Potash Valley

I would answer that question by a maybe more appropriate one ... 'Why would anyone want to use Euss when NHibernate / Castle ActiveRecord exists ?
Especialy, if you further extend NHibernate / ActiveRecord with tools such as Rhino Commons (Repositories / Unit Of Work) or ActiveWriter ...

It would be nice to have a side-by-side comparison of Euss with NHibernate (and related tools) .. and maybe DLinq also.
Euss really seems great ... on the paper, unfortunately, one of the first things users will notice is the relatively low number of posts in the forum (a lively community is an important criteria in the choice of an open source tool).

One point could be to see the few number of posts as a relatively stable tool ;)

One can also find a tool useful, even if there are far better other ones out there.

lol :) Don't get wrong, I'm interested in EUSS ... I checked the first demos that appeared on your website at a time I was developing an abstract persistence layer ... I wanted to see how you were approaching things ;o)

So in your opinion, what would be the real advantages, the key selling points of EUSS compared to using more classical ORM tools ?

Some questions:
- Why does my service layer have to reference EUSS ?
- Is there an interface for ObjectContext so that it can easily mocked in unit tests ?

I know that you know that euss is not just an orm but a persistence framework which can do orm. An I know that you understand clearly the difference (google told me).

This is one of the main interests of euss. Then I could also cite some specificities like he synchronization framework, the web administration tool, and it's technical providers (cache, prevalence, hub, ...).

I think the main drawback is - as you said- it's "popularity". My next goals are to provide some little videos demonstrating those aspects, which for some are not even decribed in the documentation, and I know it's a shame.

To answer your questions:
- you service layer doesn't have to reference euss, not at all (maybe it's in the documentation for simplicity)
- I'm open to such suggestions. Actually we use the Memory engine internally in order to not need any database during our tests

I think you could ask those questions on the forum, if ou see what I mean ;)

Yes ! You know well that I know that EUSS is not just an ORM .;o) but I think that, at first, most developers will compare it to other ORMs, and will probably not see the immediate benefits.

I guess some nice videos could help increase the popularity. :)