Peace Be Upon You,
For any component that we will develop on CRM it has two essential things that will be deployed on CRM; customizations and configuration data, I found these two VERY useful tools:
The Customization Comparison Utility lets you compare the customization files between two Microsoft Dynamics CRM systems
The Configuration Data Utility lets you transfer custom configuration data from one Microsoft Dynamics CRM system to another.
More details about these 2 tools and downloading them from here:
The first one can help much in detecting any customization conflicts and the second one lets you export custom configuration data from a source Microsoft Dynamics CRM system and import it to a target Microsoft Dynamics CRM system.
Really i think these tools are important for any CRM development team.
Peace be upon you,
I was developing on windows server 2008 and when i tried to attach a debugger to the CrmAsynchronous service so I can debug custom activities, Igot an “Access Denied” error.
The resolution for this is to change the log on account of the CrmAsynchronous service to be the account you are logged in with instead of being network service.
Peace be upon you,
I thought of sharing these useful & free .Net utilities:
.NET Productivity Suite
DevForce Express is a full featured framework that accelerates building complex, data intensive, .NET applications. Key features include VS2005 integration, RAD tools, advanced databinding, caching, security, and more.
ILMerge is a utility for merging multiple .NET assemblies into a single .NET assembly. It works on executables and dlls alike. It comes with several options for controlling the processing and format of the output, see the accompanying documentation for details.
LibCheck allows you to compare two versions of an assembly, and determine the differences. The tool reports the differences as a combination of ‘removed’ and ‘added’ APIs. The tool is limited to looking only at APIs (i.e, it can’t check for behavioral changes), and only compares public differences, or changes which are deemed to be ‘breaking’. The tool can be used to quickly determine what has changed between one version of your assembly and another, and can help ensure that you won’t introduce any breaking changes to clients of your assembly. Instructions and intended use of the tool are described in the ‘libcheck tool specification’ document with the zip file.
The CLR Profiler is a tool that you can use to analyze and improve the behavior of your managed applications.