Multiple version of DLLs loaded into memory

  • Thread starter Thread starter Srikanth Tammana
  • Start date Start date
S

Srikanth Tammana

Hi,
We have an application which runs as Excel add-in and recently we have
released newer version with higher assembly version.
So, they work fine if either of them are registered at a given point of
time. But I want to have both of them registered to support any issues
related to them. When I have both versions registered, I am getting Type
conflicts as both version of DLLs loaded into default domain when we start
excel process (As my application is an excel-addin with two different prog
ids for each version they are getting loaded into memory)
Is there any solution to solve this problem? I tried to create config file
with binding redirect and it still does not work.

<dependentAssembly>
<assemblyIdentity name="My Assembly" publicKeyToken="eb52b3e8c479af58"
culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-9.9.9.9" newVersion="3.5.2.0"/>
</dependentAssembly>

I think it worked once when I created the config file for Excel.Exe with
above information. But it will give problem when I run older version of
application as the config file always routes to newer version. So only way
is to update the config file appropriately which I am not interested in.
Can anyone suggest me a solutin for this problem?
Thanks in advance.
 
No. This is not posible. We want to install on the same machine and use the
corresponding excel adding program id to switch between the addins.

Is there any solution?

Bob Phillips said:
Run them in separate virtual machines.

HTH

Bob
Click to expand...
 
Back
Top