There are several add-ins (usually from the same supplier) which cannot work together. SOLIDWORKS may crash or misbehave. Add-ins are working correctly if loaded independently.
When same library (even of different versions) are used by different projects within the same application domain (e.g. add-in in SOLIDWORKS) .NET framework will use the cached library. The cached library will be the one which is accessed first. For example the library can be accessed when add-in button is clicked.
This results in the issues when library is not backward and forward compatible (i.e. version is supported by both newer and older applications). This is usually not the case for the libraries as behaviour may be changed, bugs fixed or regression issues introduced in the newer versions of library.
This introduces the possible conflicts when resolving the assembly references.
Use Binding Redirect element to redirect different versions of the shared library:
Add the following snippet to app.config file:
<?xml version="1.0" encoding="utf-8" ?> <configuration> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="[Assembly Name]" publicKeyToken="[Public Key Token]" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-9999.9999.9999.9999" newVersion="[Current Version]" /> </dependentAssembly> </assemblyBinding> </runtime> </configuration>
You can use the following snippet to find the required identity information (i.e. assembly name, version, public key token and culture) from the shared library.
System.Diagnostics.Debug.Print(typeof([Any type from the shared assembly]).Assembly.FullName);
This will be printed as
[Assembly Name], Version=[Version], Culture=[Culture], PublicKeyToken=[Public Key Token]