It is unclear what the relationship of the projects is or when this error occurs, but here's a hunch.
You have 3 facebook project projects (version 4.0.0.0), a twitter project (version 4.0.3.0), and a main project that references both of these projects. You may be able to build this solution, but at startup, assembly binding will fail. What for? because the default behavior is to copy assemblies locally before running. It happens that the first project is to create copies in bin (say twitter), and then the second project (facebook), and then the main one. However, at the end of this, version 4.0.0.0 is in the seat folder. When you start, as soon as you call something from Twitter trying to use the assembly of problems, the communication failure is due to the fact that it has longer access to the build version 4.0.3.0.
There are several ways around this. One of them registers both assemblies in the GAC. If this cannot be done, go to redirect the assembly binding to your configuration file. Another is to register for the AssemblyResolve event and programmatically download the assembly.
mike z
source share