Comments

Thanks for watching and for the feedback. We're open to all sorts of discussions on the Rx forums, including the naming ones. This said, we tend to try getting the semantics right first, since alpha conversion is a widely understood technique. Not trying to downplay the importance of API design in the large, Wadler's Law seems to capture exactly what we're talking about .

I'm not sure "reduced me to tears" is a compliment or not . Either way, I forgot to add a link to yet another post on the topic, that achieves very similar effects by without using C# 4.0 dynamic. Here it is: Type-Free Lambda Calculus in C#, Pre-4.0 – Defining the Lambda Language Runtime (LLR). Don't hesitate to contact me if something is unclear.

Since there seems to be quite some interest in the untyped lambda calculus and the way Erik wrote the domain equation in C# syntax, people may be interested in this post of mine on the subject, seen from an angle of .NET 4 technologies. It's titled (Mis)using C# 4.0 Dynamic – Type-Free Lambda Calculus, Church Numerals, and more and goes into quite some detail on untyped lambda calculus, Church Numerals, etc.

 

 

Have fun!

-Bart

Hi folks,

 

Thanks for watching. For more context, have a look at my recent (and upcoming) posts on my blog, covering Rx and System.Interactive. Let us know if you have further questions and have a good 2010!

 

Hope this helps,

-Bart

Concerning the Zip homework, a couple of things to keep in mind:

• Do proper argument validation: both input IEnumerable objects and the zipper function should not be null. This is a bit tricky. (Tip: when does the exception get thrown by the iterator?)
• IEnumerator objects implement IDisposable. Make sure the enumerator objects get disposed correctly under all circumstances. (Tip: don't overcomplicate it; the language can do lots of work for you)

Additional brain gymnastics can be triggered by trying to define Zip in terms of other LINQ Standard Query Operators. Enjoy!

Hi staceyw,

In theory any IQueryable provider should be addressable with LINQ through PowerShell. I haven't tested with the entity framework specifically though. It might be a totally unrelated problem like missing a configuration file that contains the connection string or so. Feel free to send me mail on "bartde at microsoft dot com" with a small project illustrating the failure condition, so I can step through it to see what's going on.

Thanks,
-Bart

Hi folks,

For those of you interested in the LINQ to SharePoint project mentioned by Scott in this video (thanks Scott!), take a look at www.codeplex.com/LINQtoSharePoint. Although we're still in the alpha stage, it's already worth to check out if you're targeting SharePoint list data in your .NET apps. Next week, we'll sync up with Orcas Beta 2, followed by a new alpha release mid August.

Have fun with Beta 2,

-Bart

People who'd like to build building custom query providers for LINQ using the IQueryable interface might be interested to check out my blog series on LINQ to LDAP. Another interesting project might be LINQ to SharePoint on CodePlex. If you want to get some insight in the standard query operators from LINQ to Objects, check out the LINQ-SQO project.

Just my 3.14 cents.

-Bart

Hi Tom,

If you're referring to Server Core concerning the exclusion of .NET Framework and PowerShell in that release, the answer is the following. Because .NET Framework today has bindings with the Windows UI APIs (e.g. System.Windows.Forms) it isn't possible to include it with Server Core. I'm sure there are some other bindings too that make it impossible to include .NET Framework 2.0 with Server Core today but over time we might see refactoring and modularization of the .NET Framework itself, eliminating these kind of issues for a subsequent release of Server Core.

Hope this helps,
-Bart

Great video indeed! I thought some of you might be interested in the managed code story around TxF and TxR, so I've written a few blog posts on this topic that you might want to check out:

http://community.bartdesmet.net/blogs/bart/search.aspx?q=txf&p=1

Have fun! KTM/TxF/TxR are worth your time