Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a small application in C#, and so far I have implemented it using data persistence classes that are running SQL directly, I understand there are better alternatives as Hibernate.NET and possibly Spring.NET.
There are some other I forget? pros and cons?
thanks!
Here are a few of the more common ones:
Spring.NET isn’t really a dedicated data persistence framework. It’s more of a IoC (Inversion of Control) framework, which gives you dependency injection, and a bunch of other stuff, including the ability to plug in a data persistence framework.
LINQ to SQL and SubSonic are probably the easiest to use and learn out of all of these. NHibernate and Entity Framework are more complex, but probably also more powerful and flexible than plain LINQ to SQL.