Ok, it is definitely Entity Framework related.
Ok, it is definitely Entity Framework related. The CacheData is pululated with LINQtoEF. Like: using (var myDatabase = new MyDatabase(entityBuilder.ToString())) { result.
A = (from a in myDatabase. ATable select new CacheLoadItem { ID = a. ID, Name = a.Name, Value = a.
Number }).ToList(); result. B = (from be in myDatabase. BTable select new CacheLoadItem { ID = b.
ID, Name = b. Name, Value = b. Code }).ToList(); result.
C = (from c in myDatabase. CTable select new CacheLoadItem { ID = c.ID, Name = c. Name, Value = c.
ID }).ToList(); result. D = (from d in myDatabase. DTable select new CacheLoadItem { ID = d.
ID, Name = d.Name, Value = d. Number }).ToList(); result. E = (from e in myDatabaseETable select new CacheLoadItem { ID = e.ID, Name = e.
Name, Value = e. Number }).ToList(); result. F = (from f in myDatabase.
FTable select new CacheLoadItem { ID = f. ID, Name = f.Name, Value = f. Number }).ToList(); result.
G = (from g in myDatabaseGTable select new CacheLoadItem { ID = g.ID, Name = g. Name, Value = g. Code }).ToList(); result.
H = (from h in myDatabaseHTable select new CacheLoadItem { ID = h. ID, Name = h. Name, Value = h.
Number }).ToList(); result. I = (from I in myDatabaseITable select new CacheLoadItem { ID = i. ID, Name = i.Name, Value = i.
Number }).ToList(); } Does not work, but the following works. Using (var myDatabase = new MyDatabase(entityBuilder.ToString())) { result. A = (from a in myDatabase.
ATable select a).ToList(). Select(b => new CacheLoadItem { ID = a.ID, Name = a. Name, Value = a.
Number }).ToList(); result. B = (from be in myDatabase. BTable select b).ToList().
Select(b=>new CacheLoadItem { ID = b.ID, Name = b. Name, Value = b. Code }).ToList(); result.
C = (from c in myDatabase. CTable select c).ToList(). Select(c=> new CacheLoadItem { ID = c.ID, Name = c.
Name, Value = c. ID }).ToList(); result. D = (from d in myDatabase.
DTable select d).ToList(). Select(d=> new CacheLoadItem { ID = a. Name1, Name = d.
Name, Value = d. Number }).ToList(); result. E = (from e in myDatabaseETable select e).ToList().
Select(e=> new CacheLoadItem { ID = e. ID, Name = a. Name1, Value = e.
Number }).ToList(); result. F = (from f in myDatabase. FTable select f).ToList().
Select(f => new CacheLoadItem { ID = f. ID, Name = f.Name, Value = f. Number }).ToList(); result.
G = (from g in myDatabaseGTable select g).ToList(). Select(g=> new CacheLoadItem { ID = g. ID, Name = g.
Name, Value = g. Code }).ToList(); result. H = (from h in myDatabaseHTable select h).ToList().
Select(h=> new CacheLoadItem { ID = h.ID, Name = h. Name, Value = h. Number }).ToList(); result.
I = (from I in myDatabaseITable select i).ToList(). Select(i=> new CacheLoadItem { ID = i. ID, Name = i.Name, Value = i.
Number }).ToList(); } The difference is that I don't do the transformation in LinqToEF but in LINQtoObjects. So I guess that EF is broken?
Result is of type CacheData – Morten Lyhr Jun 21 '10 at 12:53 In the first sample with pure LinqToEF. The data is there before the serialization with ProtoBuf, but not after. In the second with LintToObjects the data is there before and after serialization with ProtoBuf.
– Morten Lyhr Jun 21 '10 at 12:55 Well, I'll happily take a look, but an interesting thought : I've seen LINQ-to-SQL drop lazy data during serialization - it only knows about serialization due to the callback API. I can probably come up with a way (especially in "v2") to simply skip the callback API? But if you have found a workaround it might not be worth it?
– Marc Gravell? Jun 21 '10 at 20:53.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.