Ability to use Linq2db in Onion architecture

[linq2db]

Ability to use Linq2db in Onion architecture

[igor-tkachev]

Is this issue still relevant?

[gkathire]

I think this is still an issue, currently i'm adding linq2db assembly in non-dal layer projects which has the poco associated with the db. It would be nice if you can put the annotation classes in a separate assembly or provide a mechanism to dynamically create the table<->poco relationship (like Entity Framework's OnModelCreating hook).

[igor-tkachev]

Well, what namespaces you want to see in this assembly. Or what namespaces you do not want to see. And the most difficult question is what is the assembly name :)

[gkathire]

How about something like Linq2DB.Common or Linq2DB.Shared as the assembly name and the namespace ?. The annotations can reside in Linq2DB.Common(/Shared).Annotations and other generic utilities can be in Linq2DB.Common(/Shared).Utilities and so forth.

[jogibear9988]

I think for Problems like this, we have the fluent mapping?

[ili]

It is the way... But if we do have 100 POCOs i think fluent mapping would be heavy thing, also using T4 templates is a pretty feature :)

[jogibear9988]

What would be the advantage of having two assemblies?

[gkathire]

Most of the time in big projects, we tend to put the interfaces and pocos associated with the tables in a separate project, in that case we dont want the database access code to be included in that project.

[jogibear9988]

yes, but youonly don't need to use it.
i don't see any advantage in splitting up linq2db

[MaceWindu]

We don't have any plans to split linq2db into several assemblies, at least in this way.
You can easily achieve something like that with custom annotation classes (or whatever metadata source you like) and your IMetadataReader implementation to work with them. Btw I already use this approach for enums sharing with non-db assemblies in our project. Just two halfpage-size classes: for attribute and reader.

I will close it for now.