0

Just wanted to know if anyone has run into this problem or knows why this is happening.

I am doing a really simple mvvm test application. Everything works.

The only problem is that I have a DB with 4588 records and when i try to pull them all, my loadoperation craps out.

If I narrow it down to .take(4095), this works. So my Computer Science Spidy Sense started buzzing. I know this number. It then dawned on me that 4095 ( 4096 records actually since the collection is 0 based) is 8^4 or in other terms 32bits. Is this a built in limitation in RIA? 32 bits? ..or just a good CS round number that was used to cap the calls?

So then I decided to try it another way using a custom domain service and a presentation model.

The wierd thing is that I was able to get all 4588 records.

That also had issues, for instance I was only able to hang 12 properties off of my presentation model. Once I added another property, it broke. But the original problem of 4096 record limit wasn't showing up with the PM.

Any ideas?

Thanks in advance!!!

aloisdg
  • 22,270
  • 6
  • 85
  • 105
  • I'd bet its configurable. WCF has limitations like this on the size of object graphs it will serialize and transmit. Its there to prevent DoS attacks. Never used RIA so I can't tell you offhand where to look or how to configure this. –  May 27 '11 at 12:59
  • Thanks for replying Will. I am going to try to see if i can research that route. – FlackAttack May 28 '11 at 09:18

1 Answers1

1

It's possible you are running into the default limit for MaxItemsInObjectGraph, I've used the approach given here to resolve in the past:

http://blogs.objectsharp.com/CS/blogs/dan/archive/2010/04/13/maxitemsinobjectgraph-wcf-ria-services-exception.aspx

Joel Tipke
  • 497
  • 5
  • 13
  • Thanks Joel. I looked into that, but I don't think that was my problem. I ended up redoing my Database and project all together and got it working. I have a sneaking suspicion that it had to do with the way I had my relationships set up on my DB, but I can't confirm this. Thanks again for responding! – FlackAttack Jun 05 '11 at 07:26