> That still tells me that it tries to solve the same problem
> Fluent
> NH tries to solve too: a typed way to map classes to tables for the
> NHibernate framework.
>
>
> Perhaps...
> as MsTest, xUnit, MbUnit tries to solve the same problem of NUnit as C#,
> Vb.Net, Delphi... tries to sole the same problem of Java as Ninject, Funq,
> Castle, StructureMap, Autofact tries to solve the same problem of Spring
as
> EntityFrame4, LLBLGen, and others tries to solve the same problem of
> Hibernate as MacOS, Windows, Unix, Umbutu, Suse and others tries to solve
> the same problem.
> and this is only a very partial and minimal representation of the
situation
> we are living
Ok, let me try it one more time, differently this time: is ConfORM
an option used by a lot of people using nhibernate or is this the plan of
the NH team, over FluentNH/XML?
It's about what the NH framework is 'recommending' as the
'preferred' approach. I don't care what your personal preferences are in
this, I just want to know what's the preferred way and what it will be in
the future (e.g. NH3). If they solve different problems, then it's not a way
of 'you have to choose between A and B'. As they look like they solve the
same problem, it is a matter of 'you have to choose between A and B', and
thus every A and B is relevant, unless it's either someone's pet/hobby
project or a project which is dead for a long time.
FB
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en.
