2 Replies Latest reply on Nov 26, 2007 5:53 PM by Cf_Bob

    Using multiple versions of same .NET assembly

      Hi all- I'd like to use different versions of the same .dll assembly via the ColdFusion .NET integration in Scorpio. The idea here is that I might have different versions of the .dll in different branches of my code that all run on the same server. Unfortunately it looks like even if I try to reference two different versions of the same .dll files (i.e. I feed CF different absolute paths to the assemblies), the .NET integration service will only generate proxies for the first one and use those going forward rather than seeing that there are two separate assemblies. This seems linked to the way the .NET integration service works and the fact that there is only one .NET service running for the entire CF server, even in multi server configurations. Is there some way around this issue? At first glance, it looks like I have to (a) sign the assembly differently and (b) change the namespace to get the .NET integration service to see both versions of the code properly. Any ideas?

        • 1. Re: Using multiple versions of same .NET assembly
          SafariTECH Level 1
          On the web, the .NET structure that is allowed to run is defined on the IIS server itself, and you can only run one version per site.

          I'm not really sure why you would need to run multiple infrastructures, since the newest one always (unless deprecated) contains the functionality of previous versions.

          • 2. Re: Using multiple versions of same .NET assembly
            Cf_Bob Level 1
            Thanks SafariTECH - the issue here is that I might have a version of a .dll that is not guaranteed to be backwards compatible. In the .NET world, I could have two separate applications access different versions of an assembly by specifying application level assembly binding information. Is there a way to do the same using two separate CF applications and the .NET integration service? I haven't found a way, even using a CF multiserver configuration, as there's still only one .NET integration service in that case. With only one .NET integration service, it seems like only one version of an assembly can be accessed.