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.
In Java, Hibernate is king in terms of automating code/DB synchronization. And I’m aware NHibernate is a .NET equivalent, and that LINQ has some cool SQL functions (despite not being developed further IIRC).
But, is there any advantage from pairing .Net development with a SQLServer database? Magic automatic persistence of objects perhaps? Or these days does your language/DB pairing make little difference?
A simple pairing of .NET with SQL will afford you nothing over a good ORM.
The only possible reason to use the two together is that both come from the same vendor and will certainly inter-operate well.
That’s why Linq2Sql came about, not after NHibernate (Hibernate for .NET) has been around for years.