I have two legacy assemblies and can individually load them up on SoapBox Core by creating a new plugin that references the large assembly and loading the UI elements I need from them. However when I try to put both plugins together, they do not load because they depend on the same libraries but different versions (example log4net). Changing the assemblies themselves is undesirable, is there a way I can get them to work together? Currently I am copying the assemblies and their dependencies into the common plugin directory where the wrapper plugin lives.

asked 19 Apr '11, 16:35

timothypratley's gravatar image

accept rate: 0%

One option is to install your legacy assemblies in the GAC. They can happily co-exist there due to side-by-side versioning. If it's the dependencies of those that are the problem, they can be put in the GAC as well. Then you only need to put your plugins in the SoapBox Core folder. They should be able to find their legacy assembly dependencies from the GAC.

If you don't want to use the GAC, you still have a lot of control over loading dependent assemblies by using the app.config file. I suggest you read this, particularly the part at the end. It looks like you could put your conflicting dependencies in separate subfolders and use the app.config to control which file is loaded for each dependency.


answered 19 Apr '11, 20:18

Scott%20Whitlock's gravatar image

Scott Whitlock ♦♦
accept rate: 50%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 19 Apr '11, 16:35

Seen: 2,311 times

Last updated: 19 Apr '11, 20:18

Related questions

powered by OSQA