BindingRedirects uses an older version when FSharp.Azure.StorageTypeProvider is referenced

[TWith2Sugars]

No description provided.

[isaacabraham]

I suspect that this is actually an issue with the Azure Storage Type Provider. The Storage TP doesn't reference the Azure Storage SDK via Nuget, it bundles specific versions of the Azure SDK directly in its own package.

What do the binding redirects look like in your config file?

[TWith2Sugars]

I already have a reference to Microsoft.WindowsAzure.Storage via Microsoft.Azure.WenJobs

They used to be
<bindingRedirect oldVersion="0.0.0.0-4.3.0.0" newVersion="4.3.0.0" />

but are now
<bindingRedirect oldVersion="0.0.0.0-3.0.2.0" newVersion="3.0.2.0" />

[TWith2Sugars]

BTW the binding redirects affect the files that are listed in the Storage TP nuspec

[isaacabraham]

I assume WebJobs has a dependency on 4.3.0.0... so you have now pulled in the Storage TP and it's gone back to 3.0.2.0.

What do you mean by "affects the files that are listed..."?

[TWith2Sugars]

Yeah WebJobs has a dependency on 4.3.0.0.

The binding redirect problem happens to all files listed in the Storage TP nuspec: https://github.com/isaacabraham/AzureStorageTypeProvider/blob/master/build.fsx#L92-L95

It picks up their version rather than the paket.lock version.

[isaacabraham]

Mmmmm. As far as Nuget is concerned those files are just files, there's no dependency in the nuspec file as far as I remember. So I'm not sure why paket is pulling up those dlls as versioned dependencies. @forki?

[forki]

no really sure I understand the question

[TWith2Sugars]

When the binding redirect happens as part of the install it picks the version listed in the Storage TP nuspec rather than the version form the paket.lock/packages

[forki]

is there a way to reproduce this?

[TWith2Sugars]

Want me to throw up a quick git repo to show this?

[isaacabraham]

Is there actually a version in the Storage TP nuspec? I'm surprised - there probably shouldn't be, as it doesn't even use nuget for the dependencies.

[isaacabraham]

@TWith2Sugars yes that would be helpful.

[TWith2Sugars]

The files in the StorageTP nupkg are offending versions :)

[TWith2Sugars]

I'm unable to recreate this in a clean project and now it's behaving nicely after cleaning up bin/obj folders in my existing project.

I'm putting this down as a one off weird occurrence.

[isaacabraham]

This might have occurred if you had an old version of the Azure Storage Type Provider as it used to work with nuget dependencies but I removed them when I got to v1.0.

[TWith2Sugars]

Possibly