|ChrisRickard on Feb 11, 2008 at 9:39:07 PM (# 5)|
Not to nitpick but...
LINQ is a part of of .NET 3.5 which was a released Nov 2007.
Anyway my personal feeling is that I would use it for querying .NET collections but not for databases. However I haven't really had a chance to use it in a production environment.
Monte on Feb 12, 2008 at 9:14:52 AM (# 6)
Wow...am I that far behind?!
I have some serious catching up to do...I'm just now on the 2.0 Framework...
ChrisRickard on Feb 12, 2008 at 5:47:57 PM (# 7)
Heh, I know, it sneaks up on you. I can't believe how stuff has happened in client side Web Development since I left it. Ever since someone went and incremented the Web's major version # people have been going crazy.
Monte on Feb 13, 2008 at 6:17:26 AM (# 8)
.NET 3.5 isn't actually out yet, is it? The latest I've seen is 3.0 with Visual Studio 2008.
I'm way behind...looks like I need to download the Express editions of VS and get crackin'. I have #Develop at home, but that's only built for the 2.0 Framework.
ChrisRickard on Feb 13, 2008 at 10:03:47 AM (# 9)
This is all somewhat confusing but here goes:
.NET 3.0 was released Nov 06. It was a questionable decision to call it .NET 3.0 because really it didn't have anything to do with a CLR upgrade. Instead it was the release of WPF, WCF, WWF, and Cardspace technologies. These were all technologies that were only supposed to be released with Vista but ended up being released to XP as well.
.NET 3.5 was released at the same time as VS2008 Nov 07. It still has the 2.0 version of the CLR....
Actually, it looks like Wikipedia has it pretty well covered, just scroll down to where it starts listing the versions.
Monte on Feb 13, 2008 at 1:12:49 PM (# 10)
Ok, I'm still a little lost but I think I'm figuring it out (the Wiki helped a little).
So .NET 3.5 still runs on the 2.0 Framework, right? It's still clear as mud to me.