The process of solution packaging and deployment is often time-consuming and fraught with configuration issues. Having a strong understanding of your usage scenarios and being able to correctly categorize your applications (connected versus integrated) allows you to overcome these issues with relative ease.

Comprehensive testing of a solution deployment is another area where you might make dangerous assumptions. The testing section in this chapter offered guidance on how to approach your deployment test strategy. If you are unable to test for a particular scenario (or decide to explicitly disallow it), it’s important that you make this known to your end customer.

Finally, it’s important that your solution interacts well with other solutions. Customers of Microsoft Dynamics CRM often want to use solutions from multiple providers. If you follow the guidance in this chapter, your solution shouldn’t interfere with others. If, for some reason, you need to make unsupported changes to Microsoft Dynamics CRM (for example, modifying Microsoft Dynamics CRM’s Web.config), it’s important to notify your customers.