Closed Piedone closed 10 years ago
I'm not sure on the best way to implement this without a major refactor. The project takes a hard dependency on Azure Storage, and that's the project's purpose.
Perhaps the first step is to upgrade to the latest version.
Now upgraded to 3.03
I didn't mean to remove the hard dependency. Just set the assembly reference for Storage (and probably the other Azure assemblies) not to require that concrete version that you use for development - thought I before I check the project and have seen that it actually does this already. It seems that this also can't be solved from AzureDirectory but only when using it, see: http://stackoverflow.com/a/3337358/220230
Thanks for updating the lib.
I have set the specific version to false on the reference, I don't think there's much else we can do here.
If you add AzureDirectory to a project already using Azure libs (like WindowsAzure.Storage) then you can't use the AzureDirectory package but have to compile it yourself as there will be an error because of mismatching DLLs. Even a few days ago there came out a new WindowsAzure.Storage version (3.0.3) but AzureDirectory uses the previous version.