And another LINQ 101 bug...

[Mike P]

Here is another one I hope somebody can help me with, this is the
AnyGrouped example and does not recognise the 'Group' as being valid :

List<Productpro ducts = GetProductList( );

var productGroups =
from p in products
group p by p.Category into g
where g.Group.Any(p =p.UnitsInStock == 0)
select new { Category = g.Key, Products = g.Group };

foreach (var a in productGroups)
{
lbl.Text += a.Category + ":<br/>";

foreach (var b in a.Products)
{
lbl.Text += b + "<br/>";
}
}

*** Sent via Developersdex http://www.developersdex.com ***

[raylopez99]

On Aug 22, 8:47*am, Mike P <mike.p...@gmai l.comwrote:

Here is another one I hope somebody can help me with, this is the

These LINQ query errors remind me of SQL query errors--being off by a
parens or one small token is fatal. Good luck. It's a real dinosaur
construct (LINQ and SQL) IMO.

RL

[Peter Duniho]

On Fri, 22 Aug 2008 08:47:18 -0700, Mike P <mi*******@gmai l.comwrote:

Here is another one I hope somebody can help me with, this is the
AnyGrouped example and does not recognise the 'Group' as being valid :

Again, hard to say without seeing the actual sample. But what happens if
you replace "g.Group" with simply "g"?

Pete

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

raylopez99 wrote:

On Aug 22, 8:47 am, Mike P <mike.p...@gmai l.comwrote:

>Here is another one I hope somebody can help me with, this is the

These LINQ query errors remind me of SQL query errors--being off by a
parens or one small token is fatal. Good luck. It's a real dinosaur
construct (LINQ and SQL) IMO.

What do you code in where being off by one parenthesis does not matter ?

Arne

[raylopez99]

On Aug 22, 6:41*pm, Arne Vajhøj <a...@vajhoej.d kwrote:

These LINQ query errors remind me of SQL query errors--being off by a
parens or one small token is fatal. *Good luck. *It's a real dinosaur
construct (LINQ and SQL) IMO.

What do you code in where being off by one parenthesis does not matter ?

Yes, I thought of this after I posted. What I'm trying to say is that
some languages are more forgiving than SQL, which tries to pack too
much into one line. Kind of like if / else statements that are
nested--sometimes it's better to have a case statement. But it's just
my newbie opinion.

RL

[Mike P]

Here is the link to the example :

http://msdn.microsoft.com/en-us/vcsh...spx#anyGrouped

*** Sent via Developersdex http://www.developersdex.com ***