Dynamics CRM ISV folder after disabling Solutions

      Microsoft is well known that after 12 patch CRM2011 canceled ISV support for folders, since some web application that we developed definitions or want to deploy a service how to do, and some have chosen to open another site publishing. We serve as an example of such publishing open another site visit will lead to a problem of cross-domain, here are another way some people may also be used, but I did not find on the Internet has a similar share, so in this share for everyone.

     I want to share is in the default publishing site CRM to "Add Application" a way to increase application, someone will say that I have been released in this way but being given ah ah, yes, but this error is being given It can be solved. Many commonly used way is the bin inside the DLL in the root directory of all CRM copy to the bin directory publishing folder, but recently a colleague tried in 2013 so bad, but this time to share in 2013 the method is still easy to use (this method from 4.0 to 2011 to 2013 have now used), of course, itself not officially supported in this way, if you want to exaggeration friends do not look. He said so much nonsense Closer to home, the only thing that you want to modify publisher profile webconfig, code is as follows:

<span style="font-size:14px;"><compilation debug="true" targetFramework="4.0">
    <assemblies>
      <remove assembly="Microsoft.Crm, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      <remove assembly="Microsoft.Crm.Sdk, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      <remove assembly="Microsoft.Crm.Platform.Sdk, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      <remove assembly="Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
      <remove assembly="Microsoft.IdentityModel, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
    </assemblies>
</compilation>
<httpModules>
	<remove name="MapOrg"/>
        <remove name="CrmFederatedAuthenticationModule" />
      	<remove name="CrmSessionAuthenticationManager"/>
      	<remove name="CrmAuthentication"  />	
</httpModules>
<httpRuntime executionTimeout="300" maxRequestLength="32768" requestValidationMode="4.0" encoderType="System.Web.Util.HttpEncoder"/></span>

In the above code is added system.web node (if the above code is used for in 2011 and even 4.0 CRM modifications of the Version 2013).

Then add the following code in the configuration node, and then refresh the page found OK normal visit.

<span style="font-size:14px;"><system.diagnostics>
	<sources>
      <source name="System.ServiceModel" switchValue="Error" propagateActivity="true">
        <listeners>
          <remove name="ServiceModelRedirect" />
        </listeners>
      </source>
      <source name="System.ServiceModel.Activation" switchValue="Error" propagateActivity="true">
        <listeners>
          <remove name="ServiceModelRedirect" />
        </listeners>
      </source>
      <source name="System.IdentityModel" switchValue="Error">
        <listeners>
          <remove name="ServiceModelRedirect" />
        </listeners>
      </source>
      <source name="Microsoft.IdentityModel" switchValue="Error">
        <listeners>
          <remove name="ServiceModelRedirect" />
        </listeners>
      </source>
    </sources>
</system.diagnostics></span>

Reproduced in: https: //www.cnblogs.com/VicTang/p/3808998.html