Archive for April, 2011

I had to go through the rain dance of adding the Administrator account back to SQL Server after there were no admin accounts that could log in. This can happen if the SQL server box has been removed from a domain and SQL Server was installed using domain accounts. If mixed mode authentication is disabled […]


I recently had to build a simple UI for listing out a set of Microsoft CRM entities to choose from. The natural way of presenting this to the user was to give them a list of items with some associated checkboxes for selection. I wanted to associate a CRM entity ID with each checkbox so […]


How many times have you been in a client demo when your application throws an ugly stack trace up on the screen? Double points if it is up on the projector at about eight feet wide. Now, I don’t like to go overboard with excessive exception handling just to avoid the appearance of errors, but […]


I came across some code recently that gave me pause, so I thought I’d explore it a little bit here. We’ve recently converted a lot of code from CRM 4.0 to CRM 2011, and one of those pieces of code involved kicking off a Windows workflow. The following code snippet is right out of the […]


Early on in my experiences with CRM programming I learned to do whatever I can to get meaningful error responses from the server. Nothing is more difficult than having a Web service call fail and not being able to tell what happened by looking at the stack trace. Since the CRM API is delivered using […]


I was improving the design of some Silverlight code recently where the application was designed to be controlled externally from another Silverlight application. I’ll cover how to do this in two parts. The first part is exposing some API to the browser via the Html bridge. In order to make a type scriptable in Silverlight […]


I’m going to share with you a technique for re-using simple Microsoft ASP.NET Web Parts in content management systems other than SharePoint. I’ll be using Sitecore for this article but the technique should apply to DotNetNuke and others. This is useful for keeping a consistent library of Web components that can share the same code […]