wcf-ria-services

We send bitmaps from our Silverlight client to the server to be saved, using a WCF-RIA defined service operation. Our DomainService class looks a little like this: [EnableClientAccess()] public class CBitmapSavingService : DomainService { public void SaveBitmap(string bitmapGuid, byte[] pngBytes) { // Save PNG on server file system } } Works fine, until we get a large bitmap. Then we get a 'DomainOperationException' exception. I suspect that we are surpassing a size limit for either the parameter or the message. Can I reconfigure my service such that larger bitmaps can be sent from the client

I'm using XmlSerializer. I've had no problems with it until now. I updated Silverlight from 4 to 5 and at the same time also updated the WCF RIA Services from v1 SP1 to v1 SP2. Now the following line gives me an error. XmlSerializer s = new XmlSerializer(typeof(MyCustomObject)); The error is: System.InvalidOperationException: System.ServiceModel.DomainServices.Client.EntityConflict cannot be serialized because it does not have a parameterless constructor. The object I'm using (MyCustomObject in the sample) has not changed in any way so I'm starting to think it's either SL5 or the new RIA

The .NET RIA Services are described as an n-tier framework for Silverlight. I have been wondering what the relation is between this framework and the Model-View-ViewModel pattern. Are they in conflict or can you see the potential for synergic combination? .NET RIA Services and MVVM are synergistic, and aren't in conflict. For example, if I write a Catalog domain service that exposes Products and Categories on the server, and correspondingly have a Catalog domain context on the client... then the following are options to use depending on the scenario: Write a view model that wraps the Catalog

Say you create an RIA DomainService and you include a Person (shown below) entity in it, can you access aggregate entities on that object? For instance, if I have entities like so (keep in mind that this is a naive representation, they are modeled via the EF4 designer): public class Person { string FirstName { get; set; } PhoneNumber { get; set; } } public class PhoneNumber { public string AreaCode { get; set; } public string Trunk { get; set; } public string Number { get; set; } } If I include Person when creating the PeopleDomainService, can the client access the PhoneNumber on it (and

I have a query on the server side that returns a list of distinct cities from a zipcode table. I'm using WCF RIA Service. The following query successfully returns 228 cities when provincename == "" public IQueryable<CityPM> GetCities(string provinceName) { return this.ObjectContext.ZipCodes.Where(z => z.Province.Contains(provinceName)) .GroupBy(z => z.City) .Select(g => g.FirstOrDefault()) .Select(zc => new CityPM() { ID = zc.ID, Name = zc.City }); } but if I use ToLower() method as below, the query returns 0 cities when provincename == "" . public IQueryable<CityPM> GetCities(string

I have a Silverlight 4 application for a simple 'TODO' list. The problem I'm having is that databinding is hooking up relationships on my TODO object, which causes the RIA data context to add it to the DataContext.TODOs list before I want it there. I want to treat the object as new and detached until I'm explicitly ready to add it to the datacontext. Here's how it works : I've got my TODO entity which is associated with a Status (RIA services entity relationship). I create a new TODO() entity which is passed to a ChildWindow popup. Notice that I don't add this new entity to my datacontext. new

How can I use the FaultContract attribute with RIA Services so that I'll be able to pass additional information as part of an exception to Silverlight? So I went hunting though the decompiled RIA Services code. It doesn't seem like it's possible to significantly alter the error info that is sent to the client. You are able to override the OnError() method in your DomainService, but this doesn't allow you to pass arbitrary information back, even if it's a custom exception type. The reason is buried inside the exception handling of the DomainServices.Hosting.QueryProcessor class. If an unhandled