My colleague sent me a link to a great F# overview from Chris Smith, who presented at DevLink and is a member on the F# team at Microsoft. Everything you want to know about F# on a high level is covered in his post, in a very objective approach.
I was performing a CRM deployment to a TEST environment today, and we use the CRM SDK to do that. You use the ImportCompressedAllXmlRequest which takes in a compressed XML Customization file (if you have a .xml file, you can use code to compress it), and uploads it to the CRM Server.
However I was getting Timeout Error from the MSCRMAsyncService. Quite peculiar, and from looking at the Trace logs, it was timing out of a update statement to the AsyncOperationBase table. I quickly did a query, and found more than a million rows in there. AAahhhh….that explains why.
Apparently it’s not uncommon for this table to grow to a humongous state, and it’s not optimal. There’s lot of unnecessary data in there, and causing problems for my deployment. Turns out you need to clean that table up using some SQL scripts, and after that regularly maintain it using batch jobs. Here’s the SOLUTION. By the way, the delete script takes hours to execute, so leave it running overnight!
Here’s a more detailed article explain why this happened in the first place. Hope it helps.
|Share this post:|
In my first job and project, I was fortunate enough to learn from some of the best. We tried to adhere to most of the best software development practices, like unit testing, daily builds, automated deployment to multiple environments, code reviews, test coverage, source control for code and database, refactoring and countless application design sessions. It was a very fun time in my career…..good times.
I’ve been dwelling in the world of MS CRM 4.0 for more than a month now, it’s a pretty decent product. In terms of development on CRM, it’s not exactly a pleasant experience. Because it’s such a closed and inflexible ecosystem, there’s only ever 1-2 ways to do something. After doing stuff for a while, it gets pretty repetitive and monotonous. However there was one piece of work that I had to complete which proved to be a little tricky, and I’m going to share with you in this post.
Essentially, I had to implement a behavior that is close to the “Convert Lead” feature in CRM. It was not as straightforward as I though it would be, and here’s the breakdown of things you need to do in order to implement the entire feature.
Let’s use a fictitious entity for this example, called new_entity. So here goes.
Some of the best JQuery tutorials I’ve seen so far. Enuff said.
Read about Best jQuery Tutorials for June 2009. Enjoy.
If you develop on the Microsoft Platform, no doubt you would have encountered challenges with authentication using Kerberos. Colleague of mine recommended a great article of how Kerberos authentication works step by step, with scenarios of delegation from multiple servers. Also explains how to configure Kerberos for Sharepoint.
Few days agoo, I watched Seth Godin‘s talk at the Business of Software conference and he’s truly a thought-leader in our field, and a very entertaining and inspiring speaker. It’s about an hour and I promise you that you will be totally drawn and captivated by this.
In this conference, he talks about “Why marketing is too important to be left to the marketing department“. Enjoy.
In the past 2 weeks, I’ve had to install quite a number of software tools and products ( namely MS CRM 4.0, TFS 2008, VS 2008 ) on servers and workstations for my project. On 2 ocassions due to minor glitches I had to uninstall a CRM tool (via an MSI File) as well as VS 2008 due to something weird happening with Team Explorer and VS 2008 SP1. I encountered the most annoying “Cannot uninstall application due to some error, setup will now end” type of errors. A possible cause may be some screw-up in the registry and the uninstaller is unable to proceed….so what do you do now??? Here are some tips.
I came across a very nice post to have a “check all” functionality using JQuery. Great stuff and I’m sure will come in useful for many developers.
Code review is a necessity, never just a nice to have. Why do I say that? Because it has helped me grow a lot as a programmer. When I started as a junior programmer, I’ve had my code reviewed by many senior colleagues, and I have learnt so much from them. As my experience grew, I took on the role of reviewing the junior programmers, and imparted my knowledge and good practices unto them. There are many benefits to be gained from code reviews, such as:
Having been through my fair share of reviewing and being reviewed, I thought I would share some of the common pitfalls I have encountered and also been guilty of.