Editing the ISV.Config

To edit the isv.config, do the following:

1.Export the isv.config using the Export Customizations tool.

2.Create a backup copy of the exported XML file. Use this file to recover from errors.

3.Make your changes to the exported XML file.

4.Import the updated XML file using the Import Customization tool.

This file contains examples of the various customizations you can perform. You should rename this file and then create your own configuration file. By doing this you will not confuse the sample UI changes with the UI changes you need for your customization.

For the schema and sample files, see Configuration Files and Schemas.

Enabling your customizations

To enable your customizations, modify the ISVIntegration setting in the web.config file, which is located at:

<installation drive and folder>\wwwroot\web.config

This setting appears as follows:

<add key="ISVIntegration" value="All"/>

The ISVIntegration setting is used as a performance optimization. When there are no customizations to be rendered, the value for this setting should be None. Multiple values can be used as long as they are separated by a comma and do not contain spaces, as shown in the following examples: 

<add key="ISVIntegration" value="None"/>
<add key="ISVIntegration" value="Outlook,Web"/>

The following table shows the possible values for the ISVIntegration setting.

ISV Extensions Privileges

After you have enabled your customizations, you need to set the ISV Extensions privilege for security roles that need to use the customizations. By default, the security roles that do not represent a management position do not have ISV Extensions Privilege.

Disabling your customizations

To disable your customizations for either client you must use the appropriate setting in the web.config file.

Security Issues

Any integration into the application or the Outlook client must participate in security. That is, any server or client application calling into the Microsoft CRM 3.0 application programming interface (API) must have user context in the same domain.