Click here to Skip to main content
15,848,415 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
Our company has an application, let's call it MainApp, that gets deployed containing a number of "library" dlls. The library dlls are used by MainApp and "plug-ins" for MainApp. That is to say, the plug-ins also reference and use the library dlls.

Due to changes made in the library dlls, the version numbers had to be updated. The new installer of MainApp, version 1.0.15, includes these dlls with the new version numbers. However, the plug-in (let's call it plug-in1) installer was compiled with MainApp v1.0.14 (which contained previous versions of Library dlls). The code in Library dlls is compatible with plug-in1. I've tested this by "installing" plug-in1 by hand.

Currently, I'm having an issue with version numbers of the library dlls breaking backward compatibility for the plug-in1 installer. It gives an error saying it couldn't find v1.0.0 of Library dlls.

Is there anyway to provide a "redirect" as you can in the MainApp.exe.config xml file?
Posted
Comments
Richard Andrew x64 25-Mar-12 20:44pm    
You've probably not gotten any responses because your explanation is too complicated to follow. Please restate what you're looking for in a more straightforward manner, and you might get some responses.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900