ORM for .net Without Linq [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.

Closed 7 years ago.

开发者_运维技巧 Improve this question

I'm looking for ORMs that dosent support linq, i have a huge database more than (150 tables) I can't use linq To Sql or Entity framework cuz the database is not very well structured. i'm in the a process of refactoring so i'm looking for an ORM that uses old fashion SPs and entity mapping any suggestions ?

---

Subsonic might work pretty well for you. You can edit its T4 templates all you want to highly customize what's available on your entities and repositories, and the stored procedure support is pretty good (for what I needed on my project, anyway). Besides stored procedures there's also a decent fluent syntax for constructing additional queries in the code, but if you're concerned that those won't work well you can simply not used them (or potentially even disable them).

As for "not supporting LINQ" you could simply not use that feature, surely?

---

You could just use Entity Framework 4. You almost can do everything with the model and use T4 templates to refactor code in your needs. Generate POCO classes or what suits your needs. Self tracking entities or let the model generate the code by default. Supports 1 on 1 table - entity mapping and inheritance, supports complex properties that you can create for your domain. I think these should be enough to get you work.

You could also use eSQL commands instead of Linq 2 Entities, so avoids linq queries, though i can't see any reason doing that??? LINQ it's just great..

---

I recommend you the following steps:

1) Download Entity Developer for SQL Server tool

2) Create LinqConnect model using the Database First wizard

3) Generate classes for your application using T4-like templates. Modify these templates if you need some code generation customization

4) Go to model classes and implement extensible methods that override your CRUD operations. At this step you can provide support of stored procedures in the persistence layer.