Home/ Questions/Q 3665166
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T01:43:44+00:00

I’m evaluating some ORMs for my future project. I don’t like EF approach for

  • 0

I’m evaluating some ORMs for my future project. I don’t like EF approach for my particular goal, because I already have business objects which I want to make persistent and I want to target at least 1 DBMS except SQL Server. I did some research on telerik’s OpenAccess ORM. it looks very powerful, but also very complex to learn, and there documentation is somewhat outdated as their examples doesn’t work for the latest version. Now I’m thinking to try NHibernate. It looks great, but as far as I know, it doesn’t have a production ready LINQ provider, which is a huge drawback for me. But I think I can live without it.

Now about the question. I have multiple assemblies in my project, each of them containing different business objects. I want to make another DAL like assembly which will handle all CRUD operation for all of the business objects which are split in different assemblies. I know that NHibernate needs xml mappings, but in my situation, in which assembly(ies) should I embed the mapping xml files, in DAL assembly or in every assembly containing business object?

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    NHibernate 3.0 has a new query-API which is called ‘Query Over’, and it is very LINQ-isch.

    The mapping files should be placed in the assembly that contains the business logic.

    • 0