Welcome to the forty-first Community Convergence. The big news this week is that we have moved Future

Just got this link from the MSDN and this is a big milestone for Microsoft. Amazzzzing stuff you guys have made and I seriously appreciate it.
I like the way you have covered the various features and explanation in your thick Italian accent.
This will go a long way and may change design to a big extent. Kudos to the entire team.
Cheers,
Rohit
rohits79 - gmail.com

Thanks for the kind words.
Which accent are you referring to? :)

I sent the video link to a good friend of mine just to provoke him. He is italian, but his italian accent is terrible (we moved to spain when 12, then to england at 20, to brazil at 28 and to the usa at 30. He knows 5-6 languages, but none that he can claim his own :-)
I've watched your presentation and it was very clear and lucid. If I was reluctant about LINQ, now I'm starting to adopt it. But there are a few missing points in my mind, and by reading several blogs these last days, these questions also exist on the mind of many. For example, how LINQ fits the n-tier development model?
I see that there are two schools of thought nowadays, one that says to hell with DAL, LINQ to SQL "is" your DAL, and the other that says that LINQ is only useful as a RAD tool in small projects (or bounded within a traditional DAL).
Right now I'm experimenting with the first approach, creating encapsulated wcf services that makes LINQ queries directly to the datacontext obtained by the O/R designer, but I can surely see what problems may come up in a big system.
It would be very nice to hear something from an authority of the subject. Don't you want to blog about it?
Saluti di uno Italiano-Brasiliano

oops... replace "we moved" to "he moved"

Luca, the Microsoft Lead Program Manager, he is one of my favorite presenters. The way he demonstrate

Padu Merlotti,
Great comment! We are faced with those questions.  Technology is moving quickly, which makes those question you pose difficult to answer.  
For example if you decide to use LINQ to SQL as you data access layer and your business layer what do you unit test?  Do you unit test?
Bryan

Bryan,
I use NUnit for more traditional architected systems. This is going to be the first SOA system that I design. Haven't thought yet if NUnit will fit the new model or if I'll have to use (or come up) with something else.

Hi Padu,
I normally think of L2S as my DAL. If you need a DAL with more capabilities (i.e. more complex object relational mappings), then L2E is your best choice.
If you don't like how the L2S API works (i.e. maybe your customers need a company specific way to access data), then it make sense to encapsulate L2S in your own DAL.
In summary, it depends :-)

Luca,
I'm in the first week of development... that's exactly what I'm doing.
My wcf services encapsulate my L2S "EL" (Entity Layer, term that I stole from a blog I read this week).
So far so good...
I usually don't like paper thin DALs.

Really nice Vid, finally I'm on the way to understand LINQ ;)

Another rubish from Microsoft.
Do they know what multiple layers mean...
Man what a completely rubish.