May 25, 2012 at 10:02 AM
Edited May 28, 2012 at 11:19 AM
*An Update - I had thought that by using the extern alias that I had things working properly. It turned out that it doesn't help
I've posted something similar a while back, but now I'm running into a pretty serious roadblock as a result of this issue
I've got a module which we've written that uses the latest Facebook Dlls (6.0.16)
However, another team member has been implementing our authentication services which uses the NGM.OpenAuthentication project. The NGM.OpenAuthentication uses Facebook.dll (184.108.40.206)
Now that's this code has been combined with our facebook module, we're running in a situation where the NGM.OpenAuthentication is always loaded before our module so the facebook dll in the Orchard.Web\App_Data\Dependencies folder is always the
(220.127.116.11) version which breaks our module.
Now I know I could probably update the NGM module to use new facebook library, but I'd like to avoid modifying 3rd part components whenever possible.
Also note that I rean into a very similar problem 3 weeks ago where the NGM module uses an older version of Newtonsoft.Json. Were able to work around this one by lowering our requirement and using the old version of the dll as well, but in the case of facebook,
we need to use the new dll.
Is there some other way to "force" Orchard to use or load a particular version of the same dll?
Given that I've ran into this twice in the last month, I imagine others will run into something similar.
Any Suggestions or Workarounds aside from renaming my module or modifying the NGM code?
Any updates on the status of the open work item?