Is .NET v3.0 (aka WinFX) going to be Synced with C# 3.0 (aka LINQ) ?

I think it makes great sense to rename WinFX to .NET v3.0, but I haven't seen any mention as to whether or not this implies any type of sync with C# 3.0 and LINQ, let alone DLINQ and ADO.NET v3.0 Entity stuff -- anyone have anything they can share?  It seems like it would be really weird to have .NET v3.0 come out a lot sooner than C# 3.0 and ADO.NET v3.0, and I don't think those are going to be released earlier, so does this mean that part of this renaming entails a delay in WinFX, or should we expect the other things to later be renamed to 3.x or even 4.0?  Sorry if it seems I'm ignoring VB, but since its not labelled 3.0 to begin with its not really a problem with this other renaming if it ships later or not.
Published Saturday, June 10, 2006 1:35 PM by PaulWilson
Filed under: , ,

Comments

# re: Is .NET v3.0 (aka WinFX) going to be Synced with C# 3.0 (aka LINQ) ?

See Jason Zander's blog: http://blogs.msdn.com/jasonz/

LINQ (and most likely ADO.NET 3.0) will not be part of .NET Framework 3.0, but will be released together with Orcas.

Saturday, June 10, 2006 2:24 PM by Martin Ennemoser

# On Second Thought...

Earlier today, I was working on my article on the timeline for .NET releases over the next 18 months....

Saturday, June 10, 2006 4:31 PM by Robert McLaws: FunWithCoding.NET - Windows Vista Edition

# re: Is .NET v3.0 (aka WinFX) going to be Synced with C# 3.0 (aka LINQ) ?

My understanding is that only the original WinFX content will be in .Net 3.0; i.e. WCF, WF and WPF.

LINQ, ADO.NET vx etc will probably be a part of v3.5 / v4.0 er whatever they decide to name it :)

Saturday, June 10, 2006 5:25 PM by Morten Abrahamsen

# re: Is .NET v3.0 (aka WinFX) going to be Synced with C# 3.0 (aka LINQ) ?

I don't like the merging of WinFX with .Net 3.0.  To me, .Net is a platform-independent framework, akin to Java the Framework, with WinFX being a product-specific (Windows) layer of code built upon that, much like GDI would sit on top of the C++ runtime (and possibly STL), with .Net being a richer runtime.  The confusion as each component of what is now the ".Net Framework" is only going to get worse as the increasingly numerous pieces of the puzzle progress at differing rates.
But that's marketing people for ya.

Saturday, June 10, 2006 9:53 PM by Keith Patrick

# re: Is .NET v3.0 (aka WinFX) going to be Synced with C# 3.0 (aka LINQ) ?

Paul, your question alone shows it DOESN'T make sense to name it _3.0_. I agree it does make sense to rename those silly acronyms, but it should have been 2.1

Sunday, June 11, 2006 6:10 AM by FransBouma

# re: Is .NET v3.0 (aka WinFX) going to be Synced with C# 3.0 (aka LINQ) ?

www.netfx3.com ....  there's no tab for LinQ (at least not yet).

Dan

Monday, June 12, 2006 1:19 PM by Dan Bartel

# re: Keith Patrick

".Net is a platform-independent framework, akin to Java the Framework"
What did you smoke for lunch?  .NET is platform-DEPENDENT... i.e.: Microsoft.  Mono and the others are completely independent attempts to mimic the framework so that it runs elsewhere.  Lay of the pipe will ya?

Wednesday, June 14, 2006 6:58 PM by Concerned CitiZEN

# re: Is .NET v3.0 (aka WinFX) going to be Synced with C# 3.0 (aka LINQ) ?

Indeed, it is the CLS that is platform neutral not the Framework with is an implementation just as Mono is.

Wednesday, June 21, 2006 11:41 AM by Lex

# re: Is .NET v3.0 (aka WinFX) going to be Synced with C# 3.0 (aka LINQ) ?

It's a short-sighted misnomer. It won't be just Mono that's going to suffer; I mean what are they supposed to call .NET 3.5 on Compact Framework? Where's the "3" when WinFX isn't even going to be there? http://www.petitiononline.com/winfx/petition.html

Thursday, August 10, 2006 3:26 AM by rei

# re: Is .NET v3.0 (aka WinFX) going to be Synced with C# 3.0 (aka LINQ) ?

.Net 3.0 will use c# 2.0. It will not use c# 3.0 I think they should've named .Net 3.0 something more like .Net 2.5

Friday, August 25, 2006 1:55 PM by Curelom

# re: Is .NET v3.0 (aka WinFX) going to be Synced with C# 3.0 (aka LINQ) ?

It's very stupid idea to name WinFx as .NETFW3.0. THen .NETFW3 = .NETFW2 + WinFx1 = mess. How about some updates? Downloads? Will be there different versions for download? Like only .NETFW? And what then will be a .NETFW? Or will be users pushed to download .NETFW + WinFx? It's very smart to download both especially when not using WinFX at all ;) And how about updates? What will happen when there will be an update to WPF? Do we have to then download a new .NETFW3.x version? Or will be there differente updates? It's very bad idea, going against basic versioning and project priciples. Then we could rename .NETFW and every product as MSSQL, Biztalk as Windows and it would be the simplest solution :) .NETFW IS NOT WINFX! It's something different!

Tuesday, September 19, 2006 3:41 AM by Jan

Leave a Comment

(required) 
(required) 
(optional)
(required)