I'm working on a small project for a Swedish company. They need their application be available via web, so it's time to put that Silverlight knowledge at work. I decided to use Silverlight for UI technology and have a REST service layer to provide the required data. 

I was working on an application which transfered a large amount of data in a DataSet object to a client. Everything worked fine for small amounts of data, but as soon as the DataSet got bigger than 100 rows, client didn't get the message sent by the server anymore!It took some time to figure out what the problem was. If you're transferring a large amount of data and having the same problem you may need to do two things :You should set the MaxReceivedMessageSize on your binding to a larger value. If the message sent by the client/server exceeds this 

I've been busy for last months, working on not-much-new-anymore, .NET 3.0 foundations, with more focus on WPF and WCF.Here are some drawbacks and shortcomings I encountered when testing the WCF :I tried getting a DataSet containing 100 data rows from a service, using TCP binding with reliable session. When the data was bigger than a few KiloBytes, client didn't recieve the message from the service, and because of Reliable Session, service kept sending the results again and again in specific time intervals!It turned out that there's a setting to specify the maximum message size client can recieve. Client will NOT