We want your LINQ Feedback!
Do you have questions, comments or thoughts on how we could improve the LINQ Project? Please let us know! One of the key reasons to announce LINQ so early in the development cycle is to get feedback on how we can improve the product. With that goal in mind, we have dedicated LINQ on MSDN:
In addition to the forums, on 9/22, the C# team is going to be having a live chat on C# 3.0. This is a great chance to ask questions and get answers real-time from the team.
Chat with the C# team on C# 3.0 - September 22nd 1pm PST
Can’t attend PDC but still want to talk to the C# team? This chat is your chance! Join the C# team to discuss the newly announced C# 3.0 features like extension methods, lambda expressions, type inference, anonymous types and the .NET Language Integrated Query Framework. You've been hearing rumblings about this for a while, now we finally talk in depth about the future of the C# language.
Comments
- Anonymous
September 16, 2005
Where's the best place to ask, "Why does C# put the select clause last?" It's more of a C# question than a Linq question.
I understand that it makes IntelliSense a little smarter in some cases and that the projection operation is logically done last, but overall it seems very awkward to me after a couple of decades of using SQL Select statements.
I guess there will finally be one feature that I like better in VB, since they put the select clause first. :-) - Anonymous
September 19, 2005
Hi Bill,
That was my question as well. The answer I got was that it was for the IDE's (well, and the user of that IDE) benefit. If you're merrily typing "SELECT" and hit the spacebar, there's no way to pull up Intellisense if the SELECT is at the beginning. However, if you put it at the end, the FROM & WHERE are already in place, so you can pop the appropriate choices for the SELECT statement. Only time will tell if the more natural VB form can actually be coded, or if they will need a designer to build those SELECT-first statements.