I wrote a post a few weeks ago about an issue that I ran into while programming my first WCF application. If you would like to read it that post first (it might be a good idea)Since it was posted, I have noticed that a few people visit the post every day and they are probably annoyed since I identified the problem, identified the solution and then gave no explanation as to how the solution should actually be implemented. So, as promised, I am going to go over the path that we followed the solve the problem step by step.
You are here
I have a confession to make: I've been working on the perfect application. How do I know it's the perfect application? I know because it's never done and there's always "just one more thing" to refactor. And that, my friends, is a problem.
One of our older web applications in VB.NET has a page with several dependent dropdownlists that are designed to allow the user to choose various health benefits combinations. The rules for the dependencies vary and can be quite involved. To minimize database calls and to improve performance a caching layer was added. The process worked nicely, but included a lot of repetitive code to check the cache. For example, a check similar to the one in the method below had to be used each time an item was needed from the cache.
Expanding upon Jeff Ballard's recent post, Microsoft CRM 2011 oData Examples, the following is an example of how to use OData to update a record. Let's say that we want to let the user not only see who the Account's latest Contact is, but also allow them to update the Contact's Job Title, E-mail, and Phone Number without needing to open up the Contact, itself.
I enjoyed reading this article entitled the “Seven Personality Traits of Top Salespeople.” The author Steve Martin identifies what to some may sound counter-intuitive: (1) That most successful sales professionals scored high on the “Modesty and Achievement Orientation” portion of the referenced personality test, and (2) That most successful sales professionals show 30% less gregariousness. Those findings sure correct two oft-repeated salesperson