DAL Layer
-
Hi All, We are using SOA for our windows Application.However we are confused with DAl layer. First we started with Entity Framework,and it was dropped for some reason. Second we decide to use the Linq , but microsoft stop the support. third we are planning to use the Enterprise Library. May I get some suggestion regarding Enterprise Library? or suggest best technology for DAL Layer. Thanks in advance.
Ramkumar ("When you build bridges you can keep crossing them. ") http://ramkumarishere.blogspot.com
-
Hi All, We are using SOA for our windows Application.However we are confused with DAl layer. First we started with Entity Framework,and it was dropped for some reason. Second we decide to use the Linq , but microsoft stop the support. third we are planning to use the Enterprise Library. May I get some suggestion regarding Enterprise Library? or suggest best technology for DAL Layer. Thanks in advance.
Ramkumar ("When you build bridges you can keep crossing them. ") http://ramkumarishere.blogspot.com
Ramkumar_S wrote:
Second we decide to use the Linq , but microsoft stop the support
Microsoft scored a big own goal here - they haven't stopped support for LINQ, but they haven't been very effective in communicating this fact to people. I suspect your team dropped Enterprise Library because it is very complex and still a bit erratic in its behaviour. Now, if you want to go with something other than Enterprise Library, then I think you need to take a look into something like nhybernate - it's possibly the most popular .NET ORM out there right now.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
Ramkumar_S wrote:
Second we decide to use the Linq , but microsoft stop the support
Microsoft scored a big own goal here - they haven't stopped support for LINQ, but they haven't been very effective in communicating this fact to people. I suspect your team dropped Enterprise Library because it is very complex and still a bit erratic in its behaviour. Now, if you want to go with something other than Enterprise Library, then I think you need to take a look into something like nhybernate - it's possibly the most popular .NET ORM out there right now.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Pete O'Hanlon wrote:
I suspect your team dropped Enterprise Library because it is very complex and still a bit erratic in its behaviour
They didn't drop the Enterprise Library. They dropped the Entity Framework. The Enterprise Library is what they are considering next. I've never used NHibernate, but I have used its Java big brother, Hibernate. It's good for small projects, or if your team isn't strong on SQL skills. But we found that once the application began to get more complex and the database grew in size it became harder to manage through Hibernate and some of the many-to-many relationships in particular were hard to model correctly. Overall, I would say I'm positive about Hibernate but it's not the panacea that some people think.
-
Pete O'Hanlon wrote:
I suspect your team dropped Enterprise Library because it is very complex and still a bit erratic in its behaviour
They didn't drop the Enterprise Library. They dropped the Entity Framework. The Enterprise Library is what they are considering next. I've never used NHibernate, but I have used its Java big brother, Hibernate. It's good for small projects, or if your team isn't strong on SQL skills. But we found that once the application began to get more complex and the database grew in size it became harder to manage through Hibernate and some of the many-to-many relationships in particular were hard to model correctly. Overall, I would say I'm positive about Hibernate but it's not the panacea that some people think.
David Skelly wrote:
They didn't drop the Enterprise Library. They dropped the Entity Framework. The Enterprise Library is what they are considering next.
I actually meant to put Entity Framework - the brain was thinking EF, the fingers were typing EL. I've used nhibernate on larger scale projects, and it's very flexible. It seems to be significantly diverging from hibernate.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
Hi All, We are using SOA for our windows Application.However we are confused with DAl layer. First we started with Entity Framework,and it was dropped for some reason. Second we decide to use the Linq , but microsoft stop the support. third we are planning to use the Enterprise Library. May I get some suggestion regarding Enterprise Library? or suggest best technology for DAL Layer. Thanks in advance.
Ramkumar ("When you build bridges you can keep crossing them. ") http://ramkumarishere.blogspot.com
I'm a great believer in roll your own, mainly because I'm an old fart who has all the tools/framework already built. However one of our teams recently did some work in both EL and nHibernate. Its was concluded that the only reason for a framework was to maintain database agnostic code. There was approx a 50% speed penalty when moving from stored procedure to framework (we do batch processing rather than transactional systems). As we have strong SQL skills (you don't get a job if you can code TSQL) we have retained the procedures and a fairly simple framework where each table is represented by a generated class (our own classbuilder app).
Never underestimate the power of human stupidity RAH