When it comes to developing custom ASP.NET pages that need to integrate with Microsoft Dynamics CRM 2011, Microsoft recommends hosting them as a separate web application outside of the CRM web application, instead of inside the ISV folder or a virtual directory.
Unfortunately, the problem doesn’t stop there. You will notice that when you do this, it breaks some of the Ribbon functionalities (e.g. can’t add child records), the calendar date picker, etc.
Hence, I believe that the best practice would be for the website to be hosted as a separate web application under the CRM web application. It is still a separate web application, and both CRM and the custom website now share the same base URL – http://crm.company.com.
A few extra steps to get the custom pages working in the web application inside the CRM:
- Copy the following DLL files to the bin folder of the website:
- Add the section marked in red below to the website’s web.config.
<!--?xml version="1.0" encoding="UTF-8"?> <configuration> <configSections> <remove name="crm.authentication" /> </configSections> <appSettings> <clear /> ...