Today I experienced a somewhat frustrating issue with performing asynchronous queries to MSCRM 2011 through Silverlight. I had a collection of records, which I wanted to delete. All I had to do was iterate through the list, call BeginDelete and handle the asynchronous callback. This should be easy but an unhelpful exception was being raised intermittently with an unhelpful error message.
While working on a Silverlight product for MSCRM 2011 I experienced a very bizarre problem today. We have all been there… where you have a working product, go home, come back to work and the thing is broken, and you think BUT I HAVEN’T TOUCHED ANYTHING!!! Well that was me today.
One of my first choices while starting my Silverlight development in Microsoft Dynamics CRM 2011 was to used SOAP or REST. What surprised me was the lack of a clear answer in the Microsoft SDK. All I could see was a fuzzy answer, something along the lines of “Well REST is potentially OK for this… but SOAP can do that as well…”, and “SOAP is good for this…, but REST can actually achieve that as well…”. AHHHHHHHHH!!!!!!!! So I’ve given both a go and finally came to a conclusion.
While developing Silverlight applications for Microsoft Dynamics CRM 2011 I’ve been hit with the same decision most developers have. REST or SOAP? Initially I decided on REST as I wanted to use LINQ to keep my codebase nice and tidy. However, it was clear from an early stage that I needed more control than the typical CRUD operations. So I switched to SOAP. How on earth do I send and receive the async requests!?