It would help if you posted the link, so I don't have to go search through 252,458 posts to go find it ;-)
That said, the answer is: it depends. ADO.NET is a useful thing to learn as you'll probably need it someday, one way or the other.
But there are alternatives. For example, Microsoft's Entity framework enables you to do something like this:
Code:
Accomodation myAccomodation = new Accomodation();
myAccomodation.Facilities.Add(new Facility(){ Name = "SomeName"});
myAccomodation.Facilities.Add(new Facility(){ Name = "SomeOtherName"});
// Save changes here
In other words, it's designed to interact with the database through an object model that shields you from some of the underlying database design decisions as foreign keys and many to many relations. Linq to SQL does not support this well, but EF does.
There are also other ORM frameworks available that help you with this. And, with a bit awkward code, you can even do it with Linq to SQL.
So, the answer is: it depends. Pure ADO.NET would work well but requires some knowledge. Other frameworks exist, but you need to learn how they work as well.
Not a concrete answer, but it all depends in the direction you want to go to and the knowledge you already have.
To give you an idea of what ADO.NET and SQL code looks like, you may want to check out my article series on N-Layered design with ASP.NET 3.5:
http://imar.spaanjaars.com/QuickDocId.aspx?quickdoc=476
Cheers.
Imar
inserting checkboxlist items into the database
button below this post to show your appreciation!
