Pre-Validation Events for Delete Plugins

When you are creating a plugin that must perform certain actions on the Delete message, you might at times try to make changes to the associated records of the records that is being deleted. When you call the Delete message using either the Pre-Operation or Post-Operation events, the associations to the underlying related records are deleted before the actual records is deleted. 

Open Entity Form with the new Xrm.Utility object

Update Rollup 8 for Microsoft Dynamics CRM 2011 was released in May 2011, but an updated SDK was not provided with the rollup.
The Xrm.Utility objet provides a container for a couple of useful functions, that are available in every page that supports scripting. These functions can be used from form scripts or ribbon commands.

CRM Exchange Sync Trial Version now available

On Friday, September 14, we have released our latest version of the CRM to Exchange Synchronization application. The latest release, now also available for a 30-day trial, includes additional new features as well as easier configuration, multi-culture support logging capabilities and more. 

Recurring CRM Plugin Execution using Workflows

Many times we are required to have a process or task that will automatically execute at a predefined interval (such as every first of the month), but Microsoft Dynamics CRM does not have a built-in engine to have such a process. An example of this would be updating the Month-To-Date totals of a particular entity.

Deploy a Report Builder 3.0/VS 2010 Report on SSRS 2008

Visual Studio 2010 and Report Builder 3.0 RDL reports use a new schema that is not supported by SQL Server 2008 Reporting Services. They are designed to work only with SSRS 2008 R2. Currently there is no way to publish a VS2010 Report on SQL Server 2008 without some modifications to the RDL code.

Executing Powershell Commands against Exchange 2007 and Exchange 2010

The System.Management.Automation assembly allows the exeuction of Powershell commands against Exchange server.
Although, it would seem that the same code would be able to run for both of the versions of Exchange Server, two different codebases are required. The reason for this is that Exchange 2007 (SP1) supports only local Powershell, and Exchange 2010 uses remote Powershell.