Note that there are some explanatory texts on larger screens.

plurals
  1. PO2.0/3.5 assemblies side-by-side
    primarykey
    data
    text
    <p>I have a web application that I expect to intergrate features in assemblies from two separate providers. One set (Set1) of assemblies is build on .NET 2.0 while the other set (Set2) of assemblies <strong><em>ABSOLUTELY</em></strong> requires .NET 3.5. For Set2 assemblies to work, I have to add a (<strong>system.codedom</strong>) section to web.config and specify the v3.5 compiler. However, that seems to break code referencing Set1 assemblies (the JIT compiler takes forever and request times out). When I remove the <strong>system.codedom</strong> section, some features of the application referencing Set2 fail.</p> <p>We started this project with the knowledge that .NET 2.0 and 3.5 can coexist without any problems. Is there any way of making these two sets of assemblies play nicely?</p> <p><strong>EDIT:</strong> Here is what the system.codedom section looks like;</p> <pre><code> &lt;system.codedom&gt; &lt;compilers&gt; &lt;compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CSharp.CSharpCodeProvider,System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" warningLevel="4"&gt; &lt;providerOption name="CompilerVersion" value="v3.5"/&gt; &lt;providerOption name="WarnAsError" value="false"/&gt; &lt;/compiler&gt; &lt;compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" warningLevel="4"&gt; &lt;providerOption name="CompilerVersion" value="v3.5"/&gt; &lt;providerOption name="OptionInfer" value="true"/&gt; &lt;providerOption name="WarnAsError" value="false"/&gt; &lt;/compiler&gt; &lt;/compilers&gt; </code></pre> <p></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload