As Dino mentions, nothing prevents you from calling the static extensions
directly: they exist in the System.Linq namespace of System.Core.dll. The
problem, of course, is that you end up with a lot of
Queryable.Select(Queryable.Where(someInputSequence, somePredicate),
someFuncThatReturnsTheSequenceElement)
instead of the more pleasant
someInputSequence.Where(somePredicate).Select(someFuncThatReturnsTheSequenceElement)
or even
from x in someInputSequence
where somePredicate(x)
select someFuncThatReturnsTheSequenceElement(x)
And that's without getting deeply into the type naming, or expression building
with parameters. However, it's still entirely doable -- it's just *MUCH*
easier when the language is helping out with extension methods, expressions
trees from lambdas, and sophisticated type inference capabilities.
As for ASP.NET itself, Scott Guthrie (in his blog) has already mentioned the
impending LinqDataSource control, which will do some of the more interesting
stuff for you. You'll probably be able to have a working solution off of that
alone, I think (I haven't had the opportunity to play around with it, though I
took a stab at writing one, which exists in the May CTP samples). Then, when
IronPython gets additional features enabled I imagine you'll have some more
flexibility available.
________________________________
From: [EMAIL PROTECTED] on behalf of Kevin Chu
Sent: Thu 4/26/2007 7:13 PM
To: Discussion of IronPython
Subject: Re: [IronPython] About IronPython and LINQ again
If I plan to create Web Framework base of IronPython for ASP.NET like Django.
First thing,I have to solve is a ORMapper.
So do you any adivces about ORMapper used in IronPython for ASP.NET?
On 4/27/07, Keith J. Farmer <[EMAIL PROTECTED]> wrote:
Well, get to it! ;)
-- Keith [MSFT: LINQ to SQL]
________________________________
From: [EMAIL PROTECTED] on behalf of Dino Viehland
Sent: Thu 4/26/2007 11:10 AM
To: Discussion of IronPython
Subject: Re: [IronPython] About IronPython and LINQ again
There's still no direct LINQ support. We believe we're getting the
correct architecture in place to support extension methods in v2.0 (note though
we still haven't done the actual work to enable the extension methods and when
we ship the first 2.0 builds there will be no dependencies on Orcas). This
will enable much of the LINQ abilities in a convenient to use syntax. Until
then you can clr.AddReference to the LINQ libraries and call the static
extension methods directly but it'll be ugly.
Other than that we still haven't gotten to figuring out how to support
LINQ in a more direct form.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Chu
Sent: Thursday, April 26, 2007 5:02 AM
To: Discussion of IronPython
Subject: [IronPython] About IronPython and LINQ again
Hi, IronPythoners
In May 10, 2006 ,I post a discussion about IronPython and LINQ,
complete discussion url is :
http://lists.ironpython.com/pipermail/users-ironpython.com/2006-May/002300.html
<http://lists.ironpython.com/pipermail/users-ironpython.com/2006-May/002300.html>
And now Orcas Beta 1 is released, I again inquire about can I use LINQ
in IronPython.
Because ,IronPython now only use ado.net to access database, if we can
use LINQtoSQL to access SQL Server. It's cool!
--
Once in a Redmoon
_______________________________________________
users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
Once in a Redmoon
_______________________________________________
users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
