Quantcast
Channel: Common Language Runtime Internals and Architecture forum
Viewing all articles
Browse latest Browse all 1710

problems after use useLegacyV2RuntimeActivationPolicy setting

$
0
0

Please see below the architecture of my application:

Application A -> Assembly B -> Assembly C (Third party dll file could not be modified) -> Third Party A and Third Party B.

1. The original Runtime versions:

     Application A: Runtime Version: v2.0.50727

     Assembly B: Runtime Version: v2.0.50727

     Assembly C: Runtime Version: v1.1.4322 

2. Now only upgrade/recompile Application A from Runtime v2.0.50727 to v4.0, the configuration file of Application:

      <startup>
         <supportedRuntimeversion="v4.0"sku=".NETFramework,Version=v4.0"/>

   </startup>

 The third party A does not work again under Application A. Third Party B still works fine.

So Modify above config file to :

   <startupuseLegacyV2RuntimeActivationPolicy="true">
         <supportedRuntimeversion="v4.0"sku=".NETFramework,Version=v4.0"/>

   </startup>

Now, Third party A works again. However, third party B does not work.

I try below configuration files, the third party B still does not work:

  <startup useLegacyV2RuntimeActivationPolicy="true">
        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
        <supportedRuntimeversion="v2.0.50727"/>
        <supportedRuntime version="v1.1.4322"/>
        <supportedRuntime version="v1.0.3705"/>
  </startup>   

 

Both third party A and third party B are important customers.

Are there any suggestions to support both Third Party A and B?

Thanks Very Much!

Scott 





Viewing all articles
Browse latest Browse all 1710

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>