For info, much of the core of LINQ is available in . NET 2.0 (with C# 3.0) via (for example) LINQBridge This gives you most of LINQ-to-Objects (allowing query syntax against in-memory collections/iterators), but it doesn't provide the new assemblies required for LINQ-to-XML or LINQ-to-SQL etc So no; you can't use XDocument without the new assemblies from . NET 3.5; but you can do many LINQ things.
For info, much of the core of LINQ is available in . NET 2.0 (with C# 3.0) via (for example) LINQBridge. This gives you most of LINQ-to-Objects (allowing query syntax against in-memory collections/iterators), but it doesn't provide the new assemblies required for LINQ-to-XML or LINQ-to-SQL etc.So no; you can't use XDocument without the new assemblies from .
NET 3.5; but you can do many LINQ things.
LINQ is a set of extension methods defined in the System. Core assembly which is part of . NET Framework 3.5.So in order to use LINQ and LINQ to XML you will need to have .
NET Framework 3.5 installed on the target machine because your application will have a static dependency on this assembly. There's a nice diagram showing what's included in different versions of the framework.
Yes @miguel it is syntactic sugar, but it is really helpful and tasty. The Linq came to scene with C# 3 so per se you cannot use LINQ things in 2.0 version.
Can I use these constructs while still targeting . NET 2.0 runtimes?
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.