To help you prepare for your upgrade to Microsoft Dynamics CRM 2013, we have created the Custom Code Validation Tool for Microsoft Dynamics CRM 2013. When using JavaScript code in Microsoft Dynamics CRM, it is possible that some code will stop working or cause an error when you upgrade. The Microsoft Dynamics CRM Custom Code Validation Tool helps identify potential problems so that a developer can fix them. Please run this tool on your CRM instance to help identify potential issues with custom JavaScript in JavaScript libraries and HTML web resources. It will detect issues in the custom web resources that will no longer work after the upgrade is completed. The most common issues that this tool targets are:
CRM v4 client SDK calls
CRM 2007 end points
Common DOM manipulations
Running this tool before upgrade will enable you to identify issues and fix them prior to your scheduled upgrade so that your upgrade process can run smoothly.
A single Microsoft Dynamics CRM installation can host multiple
organizations on multiple servers. Therefore, it is important to specify which
organization you want to access. The IDiscoveryService Web service
returns a list of organizations that the specified user belongs to and the URL
endpoint address for each organization. For more information about the IDiscoveryService
Web service, see Discover the URL for Your Organization with
IDiscoveryService Web Service and IDiscoveryService.
Add the Microsoft
Dynamics CRM 2011 Assemblies to Your Project
Most of the time you will choose to use the SDK assemblies in your
development projects. Using the assemblies is the recommended developer
scenario for Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online.
These assemblies are in the SDK\Bin folder, along with the corresponding Visual Studio IntelliSense XML
files. For more information about the assemblies, their contents and usage, see
Assemblies Included in the Microsoft Dynamics CRM SDK.