This is meant to be an umbrella issue to discuss how we should approach and manage dependencies on external libraries that Orleans has internally and that applications use. One example is Azure SDK, which is a painful dependency to upgrade to a new version (#68).

The baseline we starting from is that Orleans itself should depend on Azure SDK current-1 version, in order to give users time to migrate their code when a new version comes out. #197 will bring us to that point. It is still not 100% clear if application will be able to use current version of Azure SDK, which is the intent. Looks like #174 is currently blocking that.

AssemblyLoader not respecting assembly binding redirects is the most immediate problem (#174).

Another, less immediate, layer of the problem is that in CoreCLR some of the Reflection APIs that AssemblyLoader is using are going away, and we need to think of how the whole process of discovering and loading of application assemblies should evolve, including dependency resolution.

We need to capture the versioning rules and approach in the documentation.