Why LINQ?

[Paulo]

Why LINQ should be used on my asp.net applications? I use C# 2.0, will I
have to move to 3.0/3.5 just because LINQ?

Tell me how to convert 2.0 code to LINQ, please. I just want to stay up to
date!

Many thanks

[Mark Rae [MVP]]

"Paulo" <er********@terra.com.brwrote in message
news:eg**************@TK2MSFTNGP06.phx.gbl...

Why LINQ should be used on my ASP.NET applications?

LINQ is functionality built into v3.5 of the .NET Framework, not just
ASP.NET.

I use C# 2.0, will I have to move to 3.0/3.5 just because LINQ?

There is no law which say that you *MUST* use new technology just because
it's available - if you don't need to use LINQ, don't use it...

Tell me how to convert 2.0 code to LINQ, please. I just want to stay up to
date!

Firstly, upgrade to Visual Studio.NET 2008...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

[Patrice]

You'll find the LINQ doc here :

http://msdn.microsoft.com/en-us/library/bb397926.aspx

As for anything else we can't choose and decide for you so the usual path
applies :

1) check out by yourself what is LINQ. Basically it adds query capabilities
against various sources to your language (that is including compile time
checking such as type safety)

2) decide by yourself you consider this a valuable feature for YOUR own
scenario

3) if yes, start using it perhaps not by rewriting something that already
works (this is significantly different from what previous coding) but
perhaps first by taking advantage of it in new projects

Good luck.

--
Patrice

"Paulo" <er********@terra.com.bra écrit dans le message de groupe de
discussion : eg**************@TK2MSFTNGP06.phx.gbl...

Why LINQ should be used on my asp.net applications? I use C# 2.0, will I
have to move to 3.0/3.5 just because LINQ?

Tell me how to convert 2.0 code to LINQ, please. I just want to stay up to
date!

Many thanks

[HillBilly]

Why? Well, why is because we now have a single way to query all of the
various data types and objects using the same skillset with very little
impact on performance or other considerations.

"Paulo" <er********@terra.com.brwrote in message
news:eg**************@TK2MSFTNGP06.phx.gbl...

Why LINQ should be used on my asp.net applications? I use C# 2.0, will I
have to move to 3.0/3.5 just because LINQ?

Tell me how to convert 2.0 code to LINQ, please. I just want to stay up to
date!

Many thanks

[HillBilly]

Why? Well, why is because we now have a single way to query all of the
various data types and objects using the same skillset with very little
impact on performance or other considerations:

* LINQ to SQL
* LINQ to XML
* LINQ to Pizza etc.

"Paulo" <er********@terra.com.brwrote in message
news:eg**************@TK2MSFTNGP06.phx.gbl...

Why LINQ should be used on my asp.net applications? I use C# 2.0, will I
have to move to 3.0/3.5 just because LINQ?

Tell me how to convert 2.0 code to LINQ, please. I just want to stay up to
date!

Many thanks

[Marc Scheuner]

>Why LINQ should be used on my asp.net applications?

One word : type-safety.

With LINQ, your database model is turned into C# classes and types and
allows you to write your queries against a full type-checked model -->
no more mistakes because of mal-formed SQL !

Also, it gives you Intellisense support for actually writing those
queries - you won't have to know your DB schema by heart anymore,
Intellisense can help you figure out the field names etc.

And lastly, with LINQ, it's a lot easier and clearer when writing
queries what your intent is - let LINQ handle all the nitty-gritty
details of turning that into valid SQL and concentrate instead on your
business app instead.

I'd definitely rate LINQ as a HUGE plus in .NET 3.5 - that alone
warrants upgrading.

Marc

[Fabio Mastria]

Marc Scheuner wrote:

>Why LINQ should be used on my asp.net applications?

One word : type-safety.

Just a question... what about the architecture 3 tier??

I think the best thing is to have sql in a stored procedure, called by a web
service... called by a business class which manage data.

LINQ is better to have SQL in code... but is always like a code in a
presentation layer... no?