The MaxItemsInObjectGraph error message comes up fairly often in the WCF RIA Services forums and I just ran into it on a personal project so I thought I’d write a quick blog on how to fix this error.
The exact error message from WCF Trace is:
2015年3月12日星期四
WCF RIA Services - “Not Found” Error Message
The dreaded “The remote server returned an error: NotFound” error message in RIA Services can be frustrating if you are not aware of what it really means, and more importantly how to diagnose it.
This generic error message is due to network stack limitation in your browser, basically the browser is intercepting the error and not giving it all to Silverlight. That does not mean there isn’t good information to be found. Your friend here is Fiddler and/or WCF Service Tracing.
2013年12月24日星期二
Should you return IQueryable from Your Repositories
Should
you return IQueryable<T> from Your Repositories
DomainContext and Operations
[WCF RIA Services Version 1 Service Pack 2 is compatible with either .NET framework 4 or .NET Framework 4.5, and with either Silverlight 4 or Silverlight 5.]
Comparing WCF Data Services and WCF RIA Services
Windows Communication Foundation (WCF) provides all the support
you need to build distributed
使用Entity Framework和WCF Ria Services开发SilverLight
使用Entity Framework和WCF Ria Services开发SilverLight之1：简单模型
本文目的是通过Silverlight ria service完成一次数据的读取过程，并且在此基础上建立测试项目。
Ria service借助于WCF和ADO.NET Entity Framework构建分布式开发框架。使用它可以快速构建自己的开发模式。
2013年12月23日星期一
使用MEF+MVVM light+WCF RIA Service实现的Sellthrough系统
在csdn上承诺要分享一个使用Silverlight+MVVM+MEF实现一个项目，都过去一个月了，我还没开始。。。
WCF序列化65536大小限制的问题
在Silverlight+WCF RIA Service或者WCF Service的架构中，经常会遇到WCF序列化65536大小限制的问题。由于WCF RIA Service没有提供明确的异常信息和错误信息，所以往往构成误导。
Silverlight WCF RIA Services: Strategies for handling your Domain Context
This is the first in a two-part article series on the WCF RIA Services Domain Context.
This article series is accompanied by source code, which can be downloaded here.
This article series is accompanied by source code, which can be downloaded here.
Async Validation with RIA Services
Almost a year ago, I posted a lengthy article on how to implement Async Validation with RIA Services and DataForm. It was hard; much harder than it should have been, and we all knew it. Since then, things have changed, and async validation is a lot simpler. Let’s take a look at why it’s easier and how you can easily perform async validation in your application.
RIA Services Validation: ViewModel Validation with Entity Rules
For those of you familiar with the ViewModel (or MVVM) pattern, you are likely also familiar with a typical pain point regarding validation: you often need to duplicate your entity validation metadata onto your ViewModel classes. This can lead to burdensome dual maintenance of your validation rules, and it can seem very frustrating that with the server to client metadata propagation that RIA Services offers, your ViewModel classes are left dangling out there for you to manage yourself. In this post, I’ll illustrate a utility I created that allows a ViewModel to assume validation metadata from model classes or properties, eliminating the dual maintenance.
RIA Services Validation: Using ValidationContext (Cross-Entity Validation)
In our last post, we learned how ValidationContext can be used to provide and consume state and services for validation methods to use. Now, let’s take a quick look at how validation methods can actually use this information. I’m going to include a bunch of code in this post, and I will rely on the code to be rather self-explanatory.
RIA Services Validation: Providing ValidationContext
Throughout this series on RIA Services Validation, I’ve mentioned and shown ValidationContext several times. In this post, we’ll learn about the purpose of ValidationContext, what types of context it can provide, and how it integrates with RIA Services. This will allow us to explore further topics such as cross-entity validation and open the door for other advanced validation scenarios.
RIA Services Validation: Entity-Level Validation
In my last post, I went over some cross-field validation scenarios and provided some sample code, including a CompareValidatorAttribute. We’ve now covered single-field validation and cross-field validation, but there’s yet another level of validation supported by RIA Services—Entity-Level validation. As you’ll see in this post, entity-level validation is very similar to what we’ve already seen.
RIA Services Validation: Cross-Field Validation
I frequently hear questions about how to perform cross-field validation in RIA Services. Before thoroughly covering this topic*, I wanted to be sure to go through some simple scenarios, show how to use CustomValidationAttribute, how to derive from ValidationAttribute, explain how validation rules are propagated to the client, and what triggers the validation. Hopefully by now, you’re getting pretty comfortable with the validation framework and you’re ready to explore some more examples.
RIA Services Validation: Validation Triggers
My goal with this blog post series is to provide an end-to-end tour of how RIA Services validation works and how you can leverage its capabilities to build rich, responsive applications. A key factor for making the most of validation is fully understanding when and how RIA Services invokes your validation rules. Awareness of the various validation triggers will help you implement your validators so they are fired as you expect, when you expect. In this post will dig into the RIA Services codebase and identify every place where entity validation is invoked.
RIA Services Validation: Custom Reusable Validators
We just covered Custom Validation Methods, where we learned how to use CustomValidationAttribute to invoke a static (VB: Shared) method to perform validation. Let’s talk about an alternate approach to custom validation though: creating custom, reusable validators by deriving fromValidationAttribute. While it’s true that the custom validation methods used by [CustomValidation] could certainly be reusable, I tend to think of that approach as a light-weight way to call specific business logic routines for validation. The approach we’re about to see is what I use when I’m creating an inventory of validators to be reused throughout my project(s).
订阅：
博文
(
Atom
)