Calling Andrus : LINQ-to-SQL id queries

[Marc Gravell]

A long time ago we discussed an issue with id-based queries in
LINQ-to-SQL; as an update, it is now suggested that this is fixed in 3.5
SP1.

Full info:
http://blogs.msdn.com/dinesh.kulkarn...nq-to-sql.aspx

Marc

[Marc Gravell]

Well, part fixed ;-p

Single(pred) is fixed, but Where(pred).Single() still round-trips; for
example via Northwind see below.

Marc

using (NorthwindDataContext ctx = new NorthwindDataContext())
{
ctx.Log = Console.Out;
Console.WriteLine("Find first employee...");
var emp1 = ctx.Employees.First();
int id = emp1.EmployeeID;
Console.WriteLine("Where(pred)=>Single");
for (int i = 0; i < 10; i++)
{
var emp2 = ctx.Employees.Where(x =x.EmployeeID ==
id).Single();
}
Console.WriteLine("Single(pred)");
for (int i = 0; i < 10; i++)
{
var emp3 = ctx.Employees.Single(x =x.EmployeeID
== id);
}
Console.WriteLine("Exit");
}

[Andrus]

Marc,

Well, part fixed ;-p

Single(pred) is fixed, but Where(pred).Single() still round-trips; for
example via Northwind see below.

Thank you.
I created code generator which creates code to implement cache using static
Dictionary<entityId,value properties for every property.
Every entity every property contains static getter method which performs
cache lookup first.
So I do'nt rely on DLinq cache.
The only way to use DLinq cache in winforms appl would be to use application
wide global DataContext class for retrieve and cache only.
However this is probably not reasonable since it does not allow to clear
cache partially.

Btw. Where find information about winforms changes ?
I have only found that there are number of new controls added, no more.

Andrus.

[Marc Gravell]

Btw. Where find information about winforms changes ?

I have only found that there are number of new controls added, no more.

Really? Which ones? I honestly don't expect any ground-breaking
winform developments - much of the thrust seems to be towards WPF and
Silverlight. I really must give them a good look at some point!

Marc

[Andrus]

Really? Which ones? I honestly don't expect any ground-breaking

winform developments - much of the thrust seems to be towards WPF and
Silverlight. I really must give them a good look at some point!

Only info I have found is one sentence and picture from

http://weblogs.asp.net/scottgu/archi...ck-1-beta.aspx
SP1 adds several new Windows Forms controls - including new vector shape,
Printing, and DataRepeater controls:
Andrus.

[Marc Gravell]

Cheers - those had slipped past me; a shame about the namespace and the
non-core references it adds, but I assume that was chosen to retain
compatibility with where-ever it came from. I rather suspect the repeater is
the most useful...

Thanks,

Marc

[Andrus]

Cheers - those had slipped past me; a shame about the namespace and the

non-core references it adds, but I assume that was chosen to retain
compatibility with where-ever it came from. I rather suspect the repeater
is the most useful...

I havent seen any new control in C# Express 2008 SP1 Toolbox.
There is no "Visual Basic PowerPacks" group in Toolbox.

How to use those control in C# Express ?

Andrus.

[Marc Gravell]

I would guess that you can simply reference it directly; for me that is in:

C:\Program Files\Common Files\Microsoft Shared\Visual Basic Power
Packs\1.1\Microsoft.VisualBasic.PowerPacks.Vs.dll

You would probably need to deploy this file to clients, too...

Marc

[Andrus]

>I would guess that you can simply reference it directly; for me that is in:

>
C:\Program Files\Common Files\Microsoft Shared\Visual Basic Power
Packs\1.1\Microsoft.VisualBasic.PowerPacks.Vs.dll

You would probably need to deploy this file to clients, too...

I do'nt have "Visual Basic Power Packs" folder in "Microsoft Shared".
searching "Microsoft.VisualBasic.PowerPacks.Vs.dll" file in computer did not
return any results.
Andrus.

[Marc Gravell]

I do'nt have *"Visual Basic Power Packs" folder in "Microsoft Shared".

searching "Microsoft.VisualBasic.PowerPacks.Vs.dll" file in computer did not
return any results.

Are you using express? In which case I would have to conclude (without
any firm eveidence) that the dll is in VS2008 SP1, not .NET 3.5 SP1;
which probably also means you're not licenced for it without VS2008.

Marc

[Marc Gravell]

btw, MS have confirmed that they can reproduce the same LINQ issue as
above... we'll see whether it ever gets fixed ;-p
Marc

[Marc Gravell]

btw - have you installed express SP1?

Marc

[Andrus]

Marc,

btw - have you installed express SP1?

I have installed C# Express 2008 SP1 and MSDN SP1 full library.

Maybe this assembly is part of VB 2008 Express SP1, havent tried.

Andrus.