By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,918 Members | 1,852 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,918 IT Pros & Developers. It's quick & easy.

Is it ok to still use datasets instead of linq?

P: n/a
I have been told that I should start using linq. I am used to datasets and
how they work. Should I really change since I don't know anything about
linq?

Nov 7 '08 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Andy B wrote:
I have been told that I should start using linq. I am used to datasets and
how they work. Should I really change since I don't know anything about
linq?
You should definitely take a look at LINQ to see what you can do with
it. However, it's not at all certain that it's better for whatever you
are doing. Just because there is a new alternative doesn't mean that
everything that came before is suddenly totally useless.

--
Göran Andersson
_____
http://www.guffa.com
Nov 8 '08 #2

P: n/a
"Göran Andersson" <gu***@guffa.comwrote in message
news:eK**************@TK2MSFTNGP02.phx.gbl...
>I have been told that I should start using linq. I am used to datasets
and how they work. Should I really change since I don't know anything
about linq?

You should definitely take a look at LINQ to see what you can do with it.
However, it's not at all certain that it's better for whatever you are
doing. Just because there is a new alternative doesn't mean that
everything that came before is suddenly totally useless.
Agreed, though there are people who claim that DataSets are now completely
obsolete, not just because of LINQ but also because of the Entity
framework - LOL!
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Nov 8 '08 #3

P: n/a
Andy B wrote:
I have been told that I should start using linq. I am used to datasets
and how they work. Should I really change since I don't know anything
about linq?
There's chatter recently that Linq to Sql is already being phased out in
favor of the Entity Framework:

Is LINQ to SQL Truly Dead?
http://www.infoq.com/news/2008/11/DLINQ-Future

--
Ben
http://allben.net/

Nov 8 '08 #4

P: n/a
"Ben Amada" <be********************@gmail.comwrote in message
news:FE**********************************@microsof t.com...
Andy B wrote:
>I have been told that I should start using linq. I am used to datasets
and how they work. Should I really change since I don't know anything
about linq?

There's chatter recently that Linq to Sql is already being phased out in
favor of the Entity Framework:

Is LINQ to SQL Truly Dead?
http://www.infoq.com/news/2008/11/DLINQ-Future

--
Ben
http://allben.net/
How hard is it to use the entity framework? The main thing I use datasets
for is data access and binding to controls on a page. I would use entity
framework, but it seems a little complicated for one and it looks like you
have to jump through tons of hoops just to bind to a repeater control. Any
ideas on this?

Nov 8 '08 #5

P: n/a
Andy B wrote:
How hard is it to use the entity framework? The main thing I use
datasets for is data access and binding to controls on a page. I would
use entity framework, but it seems a little complicated for one and it
looks like you have to jump through tons of hoops just to bind to a
repeater control. Any ideas on this?
I honestly haven't yet looked into EF. I'm a little cautious these days to
jump into the gust of technology that just happens to be blowing through
Redmond this month. I very much doubt the classic dataset / datatable
classes in ADO.NET are going anywhere while .NET is around. Entity
Framework was released in .NET 3.5 SP1. You can see how EF works, with
samples, etc. at the link below:

ADO.NET Entity Framework
http://msdn.microsoft.com/en-us/library/bb399572.aspx

--
Ben
http://allben.net/

Nov 8 '08 #6

This discussion thread is closed

Replies have been disabled for this discussion.